Integrating an on-premise Active Directory and Exchange organization with Microsoft Cloud Services will require attention to new elements and details.
As an example the list of object attributes in the on-premises Active Directory schema differs from the attributes in the Azure and Office 365 services directory platforms.
An example is three critical values that are used by Exchange Server:
Note that the only supported way to change these values are using the Exchange Admin Center (EAC)og using the Exchange Management Shell (EMS).
Making modifications to these attributes using standard PowerShell, the Attribute Editor in Active Directory Users and Computers or using the ADSIEdit snap-in is NOT supported.
Also, I have seen several cases where objects are not been picked up by the Azure AD connector in Azure AD Connect, and after troubleshooting it is revealed that the msExchRecipientTypeDetailsattribute has manually been altered from 1 to 2, thus changing it from a User Mailbox to a Linked Mailbox … where the latter is excluded from export to Azure AD/Office 365.
There is a reference field that specifies what a recipient type is, as far as on-premises AD/Exchange is concerned, Recipient Type Details = msExchRecipientTypeDetails.
As many other AD attributes, these are represented by an Integer value in AD. Here are all the possible values for Recipient Type Details:
|Mail-Enabled Universal Distribution Group|
|Mail-Enabled Non-Universal Distribution Group|
|Mail-Enabled Universal Security Group|
|Dynamic Distribution Group|
|System Attendant Mailbox|
|Cross-Forest Mail Contact|
|Universal Distribution Group|
|Universal Security Group|
As such, all I had to do was locate the Distribution Group in AD, update its msExchRecipientTypeDetailsattribute to 268435456 and wait for DirSync to replicate the change.
If you have any questions feel free to contact me on email@example.com also follow me on facebook @windowstechno to get updates about new blog posts.