Recipient Type Values on AD attribute

Both mailbox creation and deletion failure scenarios heavily involve verifying the current recipient type values across all directories – especially in a directory synchronized environment. For example; if a user is listed on-prem as a remote mailbox with a cloud archive, then you should expect EXO to have a primary and an archive mailbox for this user. If it doesn’t, then troubleshoot for a synchronization failure somewhere between on-prem and EXO.

The three attributes you will be dealing with are the following, and there are many possible values for each:

  1. msExchRemoteRecipientType
  2. msExchRecipientDisplayType
  3. msExchRecipientTypeDetails


  • msExchRemoteRecipientType

RemoteRecipientType (in PowerShell)

Note: You should only see the above value populated if the customer has a directory sync’d environment, and they either migrated a mailbox to the cloud or if they used new-remotemailbox to provision a cloud mailbox.

2ProvisionArchive (On-Prem Mailbox)
3ProvisionMailbox, ProvisionArchive
4Migrated (UserMailbox)
6ProvisionArchive, Migrated
10ProvisionArchive, DeprovisionMailbox
16DeprovisionArchive (On-Prem Mailbox)
17ProvisionMailbox, DeprovisionArchive
20Migrated, DeprovisionArchive
24DeprovisionMailbox, DeprovisionArchive
33ProvisionMailbox, RoomMailbox
35ProvisionMailbox, ProvisionArchive, RoomMailbox
36Migrated, RoomMailbox
38ProvisionArchive, Migrated, RoomMailbox
49ProvisionMailbox, DeprovisionArchive, RoomMailbox
52Migrated, DeprovisionArchive, RoomMailbox
65ProvisionMailbox, EquipmentMailbox
67ProvisionMailbox, ProvisionArchive, EquipmentMailbox
68Migrated, EquipmentMailbox
70ProvisionArchive, Migrated, EquipmentMailbox
81ProvisionMailbox, DeprovisionArchive, EquipmentMailbox
84Migrated, DeprovisionArchive, EquipmentMailbox
100Migrated, SharedMailbox
102ProvisionArchive, Migrated, SharedMailbox
116Migrated, DeprovisionArchive, SharedMailbox

Leave a Reply

Your email address will not be published.