How to Convert an On-Premises Exchange Mailbox to a Remote Mailbox
Question details
The user needs to verify and repair remote mailbox associations after migrating from Exchange 2010 to Microsoft 365 using directory synchronization.
- Product
- Microsoft Exchange / Microsoft 365
- Device & OS
- not provided
- Scenario
- Post-migration from Exchange 2010 to Microsoft 365 with directory synchronization active, ensuring the on-premises Exchange server correctly recognizes the remote mailbox.
- Observed behavior
- Running Get-RemoteMailbox in the on-premises Exchange Management Shell returns no result, indicating the remote mailbox association is missing or misconfigured.
Ensure you have administrative privileges for both your on-premises Exchange Management Shell and your Microsoft 365 tenant, and verify that Azure AD Connect (directory synchronization) is actively running.
Repair the Remote Mailbox Association using Exchange Management Shell
Use Exchange Management Shell commands to manually enable the remote mailbox on-premises and synchronize its Exchange GUID with Microsoft 365.
When an on-premises mailbox is migrated but fails to automatically convert, you must manually bridge the attributes. This ensures that on-premises mail routing recognizes the mailbox is now hosted in Microsoft 365.
Open the on-premises Exchange Management Shell and run 'Get-RemoteMailbox -Identity <User>'. If no remote mailbox is returned, proceed to the next step.
Connect to Exchange Online PowerShell using your Microsoft 365 admin credentials and run 'Get-Mailbox -Identity <User> | Format-List ExchangeGuid'. Note the GUID value returned.
Back in your on-premises Exchange Management Shell, run 'Enable-RemoteMailbox -Identity <User> -RemoteRoutingAddress <User@yourtenant.mail.onmicrosoft.com>' to convert the local account.
In the on-premises shell, run 'Set-RemoteMailbox -Identity <User> -ExchangeGuid <Online_GUID>' using the GUID you copied earlier. This ensures attributes synchronize correctly during the next directory sync cycle.
Enhance Your IT Workflow with WPS Office
While managing complex Microsoft 365 and Exchange migrations, you can equip your team with WPS Office—a highly compatible, lightweight, and cost-effective office suite that serves as a perfect alternative to Microsoft Office for drafting IT documentation and reviewing migration logs.
- 1. Download the installer: Visit the official WPS Office website and download the free installer for your operating system.
- 2. Install the suite: Run the setup file and follow the quick installation prompts to install the lightweight suite.
- 3. Open and edit seamlessly: Launch WPS Office to instantly open, edit, and save your existing Microsoft Office documents without formatting loss.
Frequently Asked Questions
Why doesn't Get-RemoteMailbox return any results in my on-premises shell?
This usually happens if the on-premises mailbox was disabled or migrated without properly being enabled as a remote mailbox, causing the local Exchange server to miss the remote routing attributes necessary to identify it.
Where exactly should I run the Get-RemoteMailbox command?
The Get-RemoteMailbox cmdlet should always be run in the on-premises Exchange Management Shell. This checks if your local environment correctly recognizes that the mailbox has been moved to Microsoft 365.
Is it normal for a migrated remote mailbox to appear as a Mail User?
Yes, once an on-premises mailbox is successfully converted or enabled as a remote mailbox, it will appear as a Mail User in your on-premises Exchange environment. This is expected behavior.
What happens if I don't set the Exchange GUID on the remote mailbox?
If the Exchange GUID is not manually set on the on-premises remote mailbox to match the Exchange Online mailbox, directory synchronization may fail to match the accounts correctly. This can lead to mail routing failures or access issues for the user.
