When dealing with attributes synced to O365 via FIM \ DirSync \ AAD Sync, you will frequently encounter the msExchRemoteRecipient type attribute, previously empty in on-prem Exchange (only msExchRecipientTypeDetails and msExchRecipientDisplayType had values) the msExchRemoteRecipientType will have the following values depending on the object type and how the mailbox and archive were enabled \ moved to O365….


1       Provisioned User Mailbox

3       Provisioned User Mailbox, Provisioned Archive

4       Migrated User Mailbox

6       Migrated User Mailbox, Archive created in cloud

20     Migrated User Mailbox, deprovisioned Archive

33     Provisioned Room Mailbox

36     Migrated Room Mailbox

65     Provisioned Equipment Mailbox

68     Migrated Equipment Mailbox

100   Shared Mailbox in EXO


* A big THANKS to Lou Mandich ( for helping me round up the missing #6 …

Reader Comments

  1. Also…

    Provisioned Room Mailbox: 33
    Migrated Room Mailbox: 36
    Provisioned Equipment Mailbox: 65
    Migrated Equipment Mailbox: 68

    ….but for some reason, no option to provision a shared mailbox directly.

  2. How do i manually set the attribute to 3 using PowerShell? I’m having to do that to enable Archive mailboxes for mailboxes migrated to Exchange Online..

    1. Andrew,
      This the command I am using to make the changes to this attribute.
      get-aduser -server “myDC” “userid” -Properties msExchRemoteRecipientType | set-aduser -replace @{msExchRemoteRecipientType=3}

  3. Set-RemoteMailbox testuser -RemoteRecipientType "ProvisionMailbox, ProvisionArchive"

  4. sorry… i read and those are NOT the values for "msExchRemoteRecipientType" but for "msExchangeRecipientTypeDetails" instead

  5. What about a 102? I think this might be a shared mailbox too, not sure what the difference to 100 is though

  6. Does anyone know what type *8* designates? I’m having trouble finding codes anywhere else for this attribute.

    1. We’re running a hybrid O365 environment. Every user that has a correct mailbox configuration in our environment has a msexchRemoteRecipientType of ‘4’ (migrated from on-prem). We have some users with a value of ‘8’ that have an 0365 mailbox, but no remotemailbox, which is a faulty config. However, upon running enable-remotemailbox on the users that meet this criteria, which would provide the desired configuration in theory, their msexchRemoteRecipientType gets changed to a value of ‘1’. I also cannot find what this value indicates…but I am guessing that it’s something along the lines of a provisioned local mailbox that had been previously migrated. Does anyone have further information on this value?

Comments are closed.