msExchRecipientTypeDetails

Object Type

RecipientTypeDetails (Decimal Value)

User Mailbox

1

Linked Mailbox

2

Shared Mailbox

4

Legacy Mailbox

8

Room Mailbox

16

Equipment Mailbox

32

Mail Contact

64

Mail-enabled User

128

Mail-enabled Universal Distribution Group

256

Mail-enabled non-Universal Distribution Group

512

Mail-enabled Universal Security Group

1024

Dynamic Distribution Group

2048

Mail-enabled Public Folder

4096

System Attendant Mailbox

8192

Mailbox Database Mailbox

16384

Across-Forest Mail Contact

32768

User

65536

Contact

131072

Universal Distribution Group

262144

Universal Security Group

524288

Non-Universal Group

1048576

Disabled User

2097152

Microsoft Exchange

4194304

Remote User Mailbox                                                                   2147483648
Remote Room Mailbox                                                                 8589934592
Remote Equipment Mailbox                                                          17179869184
Remote Shared Mailbox                                                               34359738368                 

I constantly find myself needing this table, and I can’t ever remember where on TechNet to find it, so since this is MY blog 🙂 I’m putting a copy here.

Credit where credit is due, the original lives here : http://blogs.technet.com/b/benw/archive/2007/04/05/exchange-2007-and-recipient-type-details.aspx

Reader Comments

  1. I’m not sure if yours is a typo, but I just spent a while troubleshooting with setting these attributes along with msExchRemoteRecipientType in order to have AAD Connect synchronize my user accounts to Azure AD / Office 365 and my equipment mailbox account wouldn’t sync to Azure AD. Eventually I created an equipment mailbox on-premises then migrated it and check its value. It was very close to your value for remote equipment mailbox except the 5th character is 9 instead o 3 – 17179869184. My on-premises Exchange is 2013 CU15. Seems like these long recipient type numbers are different on everyone’s blog, maybe they are ever changing with Microsoft’s updates to Exchange.

Leave a Reply