'%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 Microsoft 365 Migration from Exchange 2016 Failing Issue
Question details
Users are experiencing recurring failures when attempting to migrate mailboxes from an on-premises Exchange 2016 environment to Microsoft 365.
- Product
- Microsoft Exchange 2016 and Microsoft 365
- Device & OS
- not provided
- Scenario
- Migrating on-premises Exchange 2016 mailboxes to the Microsoft 365 cloud infrastructure.
- Observed behavior
- The email migration process fails repeatedly, often due to underlying issues with administrative permissions, Autodiscover, Outlook Anywhere endpoints, or Azure AD synchronization dependencies.
Ensure you have Global Administrator privileges in your Microsoft 365 tenant and Organization Management permissions in your on-premises Exchange 2016 environment before making any configuration changes.
Validate Migration Endpoints and Permissions
Verify that your migration endpoints, MRS Proxy, and administrative permissions are correctly configured to establish a secure connection between on-premises and cloud servers.
A successful mailbox move requires a flawless connection between Microsoft 365 and your local Exchange server. If the Mailbox Replication Service (MRS) Proxy is disabled or your endpoint certificates are invalid, the migration batches will fail immediately.
Open the Exchange Admin Center (EAC) on your Exchange 2016 server. Navigate to Servers > Virtual Directories, select the EWS (Default Web Site) directory, click the Edit icon, and ensure the 'Enable MRS Proxy endpoint' checkbox is selected.
Use the Microsoft Remote Connectivity Analyzer tool online. Run tests for Outlook Anywhere and Autodiscover to ensure external Microsoft 365 services can securely discover and connect to your local server.
Ensure the administrator account used for the migration has the 'ApplicationImpersonation' role assigned and possesses 'Receive As' permissions on the targeted Exchange mailbox databases.
Log into the Microsoft 365 Admin Center, navigate to Show All > Exchange, select Migration, and click on Endpoints. Test the existing Exchange 2016 endpoint to confirm a successful connection.
Resolve Azure AD Synchronization Dependencies
Address conflicts caused by existing Microsoft 365 mailboxes or lingering Active Directory synchronization issues that block the migration process.
Seek Specialized Help from Microsoft FastTrack
Utilize Microsoft's official enterprise assistance resources for deeply complex endpoint or hybrid configuration errors.
Discover WPS Office - The Best Free Alternative to Microsoft Office
While migrating complex Exchange servers requires specialized IT workflows, managing your daily documents shouldn't be complicated. WPS Office is a powerful, lightweight, and completely free office suite that serves as a seamless alternative to Microsoft 365 for your productivity needs.
- 1. Download the Installer: Visit the official WPS Office website and click the Free Download button.
- 2. Install the Suite: Run the downloaded executable file and follow the simple on-screen instructions to install the software.
- 3. Open Your Documents: Launch WPS Office and instantly open, edit, or save your existing Microsoft Office files without formatting loss.
Frequently Asked Questions
Why does a cutover migration fail when Active Directory synchronization is enabled?
Cutover migrations are designed for environments where directory synchronization is not used. If Azure AD Connect is already synchronizing accounts and Microsoft 365 mailboxes exist, the cutover batch will fail due to duplicate object conflicts. A hybrid migration should be used instead.
What is the MRS Proxy, and why is it needed for Exchange 2016 migration?
The Mailbox Replication Service (MRS) Proxy is an Exchange server component that facilitates cross-forest mailbox moves. It must be enabled on the Exchange 2016 EWS virtual directory to allow Microsoft 365 to securely pull mailbox data from your on-premises servers.
How do I view detailed error messages for my failed migration batches?
You can view detailed logs in the Microsoft 365 Admin Center. Navigate to the Exchange Admin Center, select Migration, click on the failed migration batch, and select 'View details' on the right pane to see specific error codes and failure reasons for individual mailboxes.
Do I need to reconfigure Outlook Anywhere for a Microsoft 365 migration?
Yes, your migration endpoints rely heavily on Outlook Anywhere (RPC over HTTP) or MAPI over HTTP to connect securely. If your SSL certificates are invalid or external URLs are configured incorrectly, the connection to Microsoft 365 will fail.
