'%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)
Fix Shared Mailboxes Missing from Exchange Online in Hybrid Migration
Question details
Users need to resolve an issue where shared mailboxes converted to user mailboxes in a hybrid migration are invisible in the admin portal.
- Product
- Microsoft Exchange Online
- Device & OS
- not provided
- Scenario
- Migrating and converting shared mailboxes to user mailboxes during a Microsoft 365 hybrid configuration setup.
- Observed behavior
- The converted mailboxes appear in PowerShell but are completely missing from the Exchange admin center and Microsoft 365 portal. Users cannot view historical messages or receive incoming emails.
Ensure you are logged into your tenant with Global Administrator or Exchange Administrator privileges, and have the necessary Microsoft 365 portal access to manage support requests.
Create a Service Request via Microsoft 365 Admin Center
Since hybrid migration synchronization and mailbox provisioning issues require tenant-level diagnostics, escalating the issue to Microsoft Support is the safest and most effective solution.
A discrepancy where mailboxes are visible via PowerShell but missing from the GUI often points to a backend provisioning delay, a directory synchronization error, or corrupted mailbox attributes in Exchange Online. Microsoft's backend support team can investigate tenant-level logs to force the sync.
Navigate to the Microsoft 365 admin center using your Global Administrator or Exchange Administrator credentials.
Click on 'Support' in the left-hand navigation pane, then select 'Help & support' or 'New service request'.
Provide details that the shared mailboxes were converted during a hybrid migration, are visible in PowerShell, but cannot receive mail or display historical messages.
Consult Microsoft FastTrack or Q&A Communities
Seek expert assistance from specialized Microsoft communities dedicated to handling complex hybrid configuration and Exchange migration scenarios.
Verify Mailbox Type and Synchronization via PowerShell
Double-check the properties of the affected mailboxes using Exchange Online PowerShell to ensure they are correctly flagged as user mailboxes.
Maintain Your Team's Productivity with WPS Office
While resolving complex Exchange hybrid migration issues, make sure your team's document workflows remain uninterrupted. WPS Office provides a reliable, lightweight, and highly compatible alternative to Microsoft Office, letting you create, edit, and share files without skipping a beat.
- 1. Download the Installer: Visit the official WPS Office website and click the free download button for your operating system.
- 2. Install the Software: Run the downloaded installation file and follow the on-screen instructions to complete the setup.
- 3. Open and Edit Files: Launch WPS Office to immediately start opening, editing, and saving your Microsoft Office files seamlessly.
Frequently Asked Questions
Why do migrated mailboxes appear in PowerShell but not in the Exchange admin center?
This usually indicates a backend provisioning delay or a directory synchronization conflict between your on-premises environment and Microsoft 365, meaning the GUI hasn't updated to reflect the database changes visible in PowerShell.
Will I lose historical emails if a mailbox conversion gets stuck during a hybrid migration?
Generally, historical emails are retained safely on the server backend. The issue is typically related to user access and indexing rather than data loss, but contacting Microsoft Support is vital to restore proper access without risk.
What is the best way to get help with a failing Exchange hybrid migration?
Because hybrid setups involve complex routing and tenant-level configurations, creating a support request directly in the Microsoft 365 admin center or posting in the Microsoft FastTrack community are the most effective methods for resolving the issue.
