Sometimes these groups are created with the option to allow sending only to users with Exchange mailboxes, rather than external users or contacts. Ensure that the on-premises group is able to send to all recipient types Go to recipients > contacts, and create a new contact. Just make sure that you use the same Display Name, alias and email address for the contact as you have already for the on-premises group. Office 365 needs to have a contact object that matches the on-premises dynamic group. Create contact objects in Office 365 that correspond to the groups With the Internal Relay option, if Office 365 doesn’t know what to do with a message, it will forward the message back down to your on-premises server. Switch it from Authoritative to Internal Relay. If not, re-run the Hybrid Configuration Wizard again, and also check the setting for your email domain name in mailflow > accepted domains from the Office 365 EAC. Just make sure you can send mail from an on-premises mailbox and receive it in the cloud, and vice-versa.
#HOW TO SYNC OFFICE 365 GROUPS WITH AD FULL#
If you have a full hybrid environment, this should already be the case. Ensure you have cross-premises mail flow enabled But, if you’re keeping Dynamic Distribution Groups on-premises, how do we get mail delivered to them, once we migrate mailboxes to Office 365? Remember: Azure AD is not aware of these objects, so how can we ensure mail delivery still happens? Like this. Or another alternative is, convert them to normal distribution groups and then synchronize them that way. Your other options are to manually re-create them in the cloud. Therefore, if you want to keep your Dynamic Groups, then you have to keep them on-premises. The problem is, Azure AD is not the same as your on-premises AD, and there may be elements of the Directory that do not correspond 1-1, so some queries wouldn’t really be able to execute in the same way. If you meet the criteria at the time an email is sent to that “group,” then you will get a copy of the message. recipients are located in the “Human Resources” OU). So for example there are some criteria that need to be met (e.g. In other words, members of the group are determined via a query that is run at the time the email is sent to the group. What they are essentially, is a stored query. They don’t sync because they aren’t really the same type of object as a normal distro group. In a hybrid scenario, where you have Azure AD Connect synchronizing your Active Directory objects for single-sign on with Office 365, Dynamic Distro Groups simply will not sync. (Yes, I just made that word up, but now it is a real word–that’s how words are made). Dynamic Distribution Groups are not directly “migratable” to Office 365.