msExchangeRecipientTypeDetails Active Directory Values
Integrating an on-premises 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:
-
msExchRecipientDisplayType
-
msExchRecipientTypeDetails
-
msExchRemoteRecipientType
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:
| Object Type | RecipientTypeDetails | Value Name |
| User Mailbox | 1 | UserMailbox |
| Linked Mailbox | 2 | LinkedMailbox |
| Shared Mailbox | 4 | SharedMailbox |
| Legacy Mailbox | 8 | LegacyMailbox |
| Room Mailbox | 16 | RoomMailbox |
| Equipment Mailbox | 32 | EquipmentMailbox |
| Mail Contact | 64 | MailContact |
| Mail User | 128 | MailUser |
| Mail-Enabled Universal Distribution Group | 256 | MailUniversalDistributionGroup |
| Mail-Enabled Non-Universal Distribution Group | 512 | MailNonUniversalGroup |
| Mail-Enabled Universal Security Group | 1024 | MailUniversalSecurityGroup |
| Dynamic Distribution Group | 2048 | DynamicDistributionGroup |
| Public Folder | 4096 | Public Folder |
| System Attendant Mailbox | 8192 | SystemAttendantMailbox |
| System Mailbox | 16384 | SystemMailbox |
| Cross-Forest Mail Contact | 32768 | MailForestContact |
| User | 65536 | User |
| Contact | 131072 | Contact |
| Universal Distribution Group | 262144 | UniversalDistributionGroup |
| Universal Security Group | 524288 | UniversalSecurityGroup |
| Non-Universal Group | 1048576 | NonUniversalGroup |
| Disabled User | 2097152 | DisabledUser |
| Microsoft Exchange | 4194304 | MicrosoftExchange |
| Arbitration Mailbox | 8388608 | ArbitrationMailbox |
| Mailbox Plan | 16777216 | MailboxPlan |
| Linked User | 33554432 | LinkedUser |
| Room List | 268435456 | RoomList |
| Discovery Mailbox | 536870912 | DiscoveryMailbox |
| Role Group | 1073741824 | RoleGroup |
| Remote Mailbox | 2147483648 | RemoteMailbox |
| Team Mailbox | 137438953472 | TeamMailbox |
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.
So, that’s all in this blog. I will meet you soon with next stuff. Have a nice day.
Guys please don’t forget to like and share the post. Also join our WindowsTechno Community and where you can post your queries/doubts and our experts will address them.
You can also share the feedback on below windows techno email id.
If you have any questions, feel free to contact us on admin@windowstechno.com also follow us on facebook@windowstechno to get updates about new blog posts.
