'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Exchange Mailboxes Showing as On-Premises After Hybrid Migration
Question details
Resolve an issue where mailboxes that have been migrated to Microsoft 365 continue to display as being hosted on-premises within an Exchange hybrid environment.
- Product
- Microsoft Exchange Hybrid
- Device & OS
- not provided
- Scenario
- Administrators are reviewing mailbox statuses after completing a hybrid migration from an on-premises Exchange server to Microsoft 365.
- Observed behavior
- Mailboxes that were successfully moved to Microsoft 365 incorrectly appear as on-premises mailboxes in the Exchange admin center.
Ensure you have administrative access to both your on-premises Exchange Management Shell and your Microsoft 365 tenant, and verify that Azure AD Connect synchronization is running without errors.
Verify Directory Attributes and Consult Exchange Experts
Since this involves complex directory attribute synchronization across hybrid environments, verify the basic sync status before escalating to Microsoft hybrid specialists.
In an Exchange hybrid environment, mailboxes migrated to the cloud are converted to Remote Mailboxes on-premises. If Azure AD Connect fails to synchronize the updated attributes (such as msExchRecipientDisplayType or RemoteRecipientType), the administrative portal will continue to display the mailbox as on-premises. Resolving deep synchronization issues often requires advanced administrative intervention.
Open the on-premises Exchange Management Shell and run 'Get-RemoteMailbox -Identity <user> | fl RemoteRoutingAddress' to ensure the mailbox has the correct target address (usually ending in mail.onmicrosoft.com).
Log into your Azure AD Connect server, open PowerShell as an administrator, and execute 'Start-ADSyncSyncCycle -PolicyType Delta' to force any pending attribute changes to push to Microsoft 365.
If the status does not update after synchronization, gather your migration batch logs and post your issue in the official Microsoft Exchange Hybrid IT Pro forum. Specialists there can help review specific directory attributes and migration status anomalies.
A Lightweight, Free Alternative for Your Daily Office Work
While enterprise Exchange hybrid migrations require specialized Microsoft administrative expertise, your day-to-day document management shouldn't be complicated. WPS Office offers a completely free, highly compatible alternative to Microsoft Office for creating, editing, and managing your essential documents.
- 1. Download the installer: Visit the official WPS Office website and click the free download button to get the lightweight installation package.
- 2. Install the software: Run the downloaded installer and follow the simple on-screen instructions to set up the suite on your computer.
- 3. Open your documents seamlessly: Launch WPS Office to instantly open and edit your existing Word, Excel, and PowerPoint files without any formatting loss.
Frequently Asked Questions
Why does a migrated mailbox still show as on-premises?
This typically occurs due to synchronization delays or failures in Azure AD Connect. After a migration batch completes, on-premises directory attributes like 'msExchRecipientDisplayType' must be updated and synced to Microsoft 365 to reflect the new remote mailbox status.
Will users lose access to their emails while the mailbox shows as on-premises?
Generally, no. As long as the actual migration completed successfully and Outlook Autodiscover is correctly routing the user to the Microsoft 365 endpoint, mail flow and user access will continue normally. The issue is usually restricted to how the administrative portal displays the status.
How can I manually check the recipient type in Exchange Online?
You can connect to Exchange Online PowerShell and run the command 'Get-Recipient -Identity <user email> | Select RecipientType, RecipientTypeDetails'. A properly migrated mailbox should show up as a 'UserMailbox' in the cloud rather than a 'MailUser'.
