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

Details

• 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.

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