Rules to Better Office 365 - 6 Rules
If you still need help, visit our Office 365 consulting page and book in a consultant.
Using Active Directory Federation Services (ADFS) lets you use one account to log into multiple systems, through Single Sign-On (SSO).
ADFS is built upon SAML 2.0 protocol (Security Assertion Markup Language), allowing secure exchange of authentication data.
With ADFS, you can use only one account (generally created on your on-premises Active Directory (AD) server) to log into multiple systems e.g. Dynamics 365 CRM, Office 365 and many others.
This implementation gives you security over which users are acessing which application with which accounts, and also reduces the surface for attacks on having many accounts with many different passwords:
Figure: Good Example - Using one account on many systems
ADFS also gives you a solution in other corner cases:
- When you want to use Office 365 and not store your password on the cloud; 2. When you want the authentication to take place on-premises; 3. When you want to create a trust between SharePoint on-premises and Azure AD; 4. Amongst many others.
Figure: Good Example - Using SSO to log into CRM with your on-premises account
- When you want to use Office 365 and not store your password on the cloud; 2. When you want the authentication to take place on-premises; 3. When you want to create a trust between SharePoint on-premises and Azure AD; 4. Amongst many others.
Azure Active Directory (AAD) Password Hash Synchronization (PHS) is one of the methods you can use if you want to have your identities synced to the cloud, alongside Pass-through Authentication (PTA) and Federation with AD FS.If you have a hybrid identity in place with AAD, chances are you are already synchronizing password hashes to the cloud with Azure AD Connect Sync.
AAD PHS synchronizes the password in on-premises AD with AAD so you can use your on-premises password to login to cloud services, like Azure or Office 365. It also allows you to implement Seamless Sign-On for domain-joined machines, so users don't need to login twice when opening their emails in a browser, for example.
AAD PHS also allows you to have an absolute lean infrastructure on-premises, as the only needed moving part is Azure AD Connect Sync to be installed in a server or Domain Controller. No agents or internet-facing machines necessary.
The web requests don't even come to your server, they are server by Microsoft's big pool of servers around the globe!
Figure: Good Example – AAD PHS infrastructure workflow You can check out a deep dive of AAD PHS in official Microsoft documentation at What is password hash synchronization with Azure AD?
If you have an on-premises Skype for Business (S4B) server, and you want to upgrade to Microsoft Teams, you need to setup S4B in Hybrid mode with your Office 365 tenant first.
Microsoft Teams is going to replace Skype and Skype for Business in the near future - which means an upgrade will be necessary soon.
- To leverage the full features of Teams, you need to first setup Hybrid on your S4B on-premises server. This is no small task, and you can find the full instructions on how to do that here 2. After setting up a Hybrid environment, you will need to migrate all your users from S4B to Teams. This involves 2 steps (if you have an on-premises S4B): a. Moving from S4B on-premises to S4B online (instructions); b. Moving from S4B online to Teams. (instructions)
- In Teams, add a Dynamics tab
- In Dynamics, add a Teams URL field
Figure: Dynamics 365 tab in MS Teams (also showing the Teams URL field, two birds in one stone) The default message size limit in Exchange Online is 25MB. Even though email attachments are not the best way to share a large file, sometimes it is the only option - and these days, 25MB is quite small. This default limit should be increased; it is easy to do so from the Exchange admin center or Exchange Management Shell.
It is important to remember that the maximum email attachment size will also depend on the person receiving the email - their email service will need to accept the larger size. For example, Gmail's default limit is also 25MB.
Changing the default in Exchange admin center
- Go to Exchange admin center | Recipients | Mailboxes | Set default message size restrictions
- Enter the maximum size you would like to set in KB for both sending and receiving, and click Save. We have it set to 35MB (35,840KB).
Figure: Default message size restrictions in Exchange admin center Note that this will only apply to new mailboxes. To change the restrictions for existing mailboxes, from the same page you can select one, several or all existing mailboxes, and click Message size restrictions. As above, enter the desired maximums and click Save.
Figure: Existing mailbox message size restrictions in Exchange admin center Changing message limits in Exchange Management Shell
Of course, this can also be done with the Exchange Management Shell, for example:
Set-Mailbox -Identity "Adam Cogan" -MaxSendSize 35mb -MaxReceiveSize 35mb
Links
Exchange Online limits - Service Descriptions | Microsoft Docs
Configure message size limits for a mailbox | Microsoft Docs
Microsoft provides a collaboration tool called Microsoft 365 email groups on the cloud, which allows users to send emails to a group of people using a single email address. These groups can be created and managed from any location with an internet connection and can include both internal and external recipients. Microsoft 365 email groups on the cloud offer a wide range of collaboration features, making them an effective tool for streamlining communication and improving productivity.
On-premises groups vs Microsoft 365 groups
It is important to understand the differences between on-premises groups and Microsoft 365 groups.
On-premises groups
These groups are created and managed within an organization's local network, using on-premises infrastructure such as Active Directory. These groups typically have limited collaboration features and are primarily used for email distribution and security management. If we have to manage the groups, users, or laptops on-premises that are domain-joined it is easier to create a security group in AD.
NOTE: AD groups sync to Microsoft 365 (cloud), but Microsoft 365 groups don't sync back to AD
Figure: Choosing a group type in On-Premises Active Directory Microsoft 365 groups
In Microsoft 365, there are 6 different types of groups you can create - so it is important to know how to decide which group to create.
The groups available in Microsoft 365 are:
- Microsoft 365 Groups
- Distribution groups
- Security groups
- Mail-enabled security groups
- Shared mailboxes
- Dynamic distribution groups
Figure: Choosing a group type in Microsoft 365 Microsoft 365 Groups
Microsoft 365 groups are for collaboration between members of the group. When you create a Microsoft 365 group, you get a number of shared resources - including an inbox, a calendar, and a shared workspace for files. You can create a Microsoft 365 Group with or without a Team attached to it - or you can add a Team later.
Microsoft 365 Groups are recommended by Microsoft, and they are often the best choice if you're not sure which group type to choose. Choose these groups if the users wish to choose whether they want to receive the email or not (subscribe).
Distribution groups
Distribution groups are the way to go if you just want to be able to email a number of people at the same time. They lack the collaboration features of a Microsoft 365 group, but sometimes you don't need these extra bits.
It's also worth noting that Distribution groups can be upgraded to Microsoft 365 Groups, so you can change your mind later. Choose these groups if the users need to always receive these emails (important alerts).
Security groups
Security groups do not provide email, or any sort of collaborative tools. They are used to grant access to resources, such as SharePoint or Azure resources. This makes managing access easier, as you don't have to add individual accounts - and when you remove someone from the group, their access is removed from everywhere that group had access.
Naming security groups is particularly important, so that you know what it is and what it is used for. These should be prefixed with SEC_ and should clearly show what the group is used for, for example SEC_VPNUsers.
Mail-enabled security groups
Mail-enabled security groups are - you guessed it - security groups with mail enabled. They are useful if you want to grant access to a resource and email the people with that access.
Shared mailboxes
Shared mailboxes are used when multiple people need to access the same mailbox. They are useful when there is a shared role, e.g. a reception desk. They also include a calendar that can be used by everyone with access to the mailbox.
Shared mailboxes are also useful as they give you a mailbox without taking up one of your Exchange online licences.
Figure: Shared mailboxes are created in their own section under the Teams & groups heading Dynamic distribution groups
Dynamic distribution groups are created in the Exchange admin center.
Unlike regular distribution groups that contain a defined set of members, the membership list for dynamic distribution groups is calculated each time a message is sent to the group, based on the filters and conditions that you define. When an email message is sent to a dynamic distribution group, it's delivered to all recipients in the organization that match the criteria defined for that group.
You can read more about groups in Microsoft 365 in Microsoft's documentation.
