On-Premises vs Remote Mailboxes: Understanding Mailbox Types in Exchange Hybrid
In an Exchange Hybrid environment, “what type of mailbox is this” has a more layered answer than in a pure on-premises or pure cloud setup, since the same user can be represented differently depending on which side of the hybrid boundary a mailbox actually lives on. Getting these types straight matters for migration planning and for troubleshooting mail flow issues that only show up in hybrid.
The core distinction: where does the mailbox actually live
In hybrid, every user is represented in on-premises Active Directory, but their actual mailbox is either still on-premises or already migrated to Exchange Online. The on-premises object type reflects which of these is true:
- Mailbox (on-premises): a standard mailbox still hosted on an on-premises Exchange server, not yet migrated.
- Remote Mailbox: the on-premises AD object representing a user whose actual mailbox has already been migrated to Exchange Online. This is not a real mailbox itself, it’s a mail-enabled user object with a
TargetAddresspointing to the Exchange Online mailbox, kept on-premises specifically so the on-premises Exchange organization retains management visibility and directory sync continues to work correctly.
Checking which type a specific user is
# On-premises Exchange Management Shell:
Get-Mailbox -Identity "[email protected]" # still on-premises
Get-RemoteMailbox -Identity "[email protected]" # already migrated to Exchange OnlineA given user will only return a result from one of these two cmdlets, never both, which is itself a useful diagnostic: if neither returns a result, the object likely isn’t mail-enabled at all, or exists only in Exchange Online with no on-premises AD counterpart.
The standard mailbox types you’ll see on either side
- User Mailbox: a standard, licensed mailbox for an individual.
- Shared Mailbox: no dedicated license required (within Microsoft’s size/feature limits), accessed via delegated permissions from other mailboxes rather than its own login.
- Room Mailbox / Equipment Mailbox: resource mailboxes for meeting rooms or bookable equipment, with their own calendar and booking policies.
- Discovery Mailbox: used internally by Exchange for eDiscovery search result storage, not meant for direct end-user access.
These types apply identically whether the mailbox is on-premises or in Exchange Online, the Remote Mailbox distinction above is specifically about hybrid migration state, layered on top of these standard types.
Why this distinction actually matters during a migration wave
A common hybrid migration mistake is running a script that filters on Get-Mailbox alone to build a report or apply a policy change, and silently missing every user who has already migrated, since those users now only appear under Get-RemoteMailbox on-premises. Any organization-wide script during an active migration project needs to check both cmdlets, or better, query Exchange Online directly for the authoritative current state.
Frequently asked questions
Why does a migrated user still show up in on-premises Active Directory at all?
This is intentional and required for hybrid to function correctly. The on-premises AD object (now a Remote Mailbox / mail user) continues to sync to Entra ID via Entra Connect, preserving a single, consistent identity and allowing on-premises tools and Group Policy to keep managing the user account even after their mailbox has moved to the cloud.
Can a Remote Mailbox be converted back to an on-premises mailbox?
Yes, via an offboarding migration batch in the Exchange Hybrid environment, which is the reverse of the normal onboarding migration. This is uncommon but sometimes necessary for compliance or specific technical requirements that require a mailbox to move back on-premises.
