'%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 Cross-Tenant Exchange Online Mailbox Migration Failures
Question details
Administrators experience failures when attempting cross-tenant mailbox migrations between two Microsoft 365 tenants due to using incorrect on-premises configurations.
- Product
- Exchange Online
- Device & OS
- not provided
- Scenario
- Migrating mailboxes directly between two Exchange Online tenants without an on-premises Exchange server.
- Observed behavior
- Migration PowerShell scripts and commands like Set-WebServicesVirtualDirectory fail because they are designed exclusively for on-premises Exchange environments.
Ensure you have global administrator or Exchange administrator privileges for both the source and target Microsoft 365 tenants before initiating the migration process.
Implement the Microsoft 365 Cross-Tenant Mailbox Migration Process
Apply the official tenant-to-tenant migration process instead of legacy on-premises Exchange commands.
When migrating between two Exchange Online environments without an on-premises Exchange server, standard IMAP and MRS Proxy configurations (like Set-WebServicesVirtualDirectory) will not work. You must establish a proper tenant-to-tenant organizational relationship.
Navigate to the Microsoft 365 admin center and verify that both the source and target tenants are strictly Exchange Online environments.
Stop using the 'Set-WebServicesVirtualDirectory' PowerShell command, as it is only applicable to on-premises servers and will trigger connectivity failures in Exchange Online.
Establish the required Azure AD applications and cross-tenant access settings between the source and target tenants following Microsoft's official cross-tenant migration guide.
Create MailUser objects in the target tenant and assign the appropriate Exchange Online PowerShell execution rights to the migration administrator accounts.
Run the authorized cross-tenant migration PowerShell scripts to initiate and finalize the mailbox transfers.
Boost Your Team's Productivity with WPS Office
While managing complex Microsoft 365 migrations, consider providing your users with a lightweight, cost-effective alternative for their daily document needs. WPS Office offers seamless compatibility, a familiar interface, and cross-platform support to keep your business running smoothly during tenant transitions.
- 1. Download the software: Visit the official WPS Office website to download the free installation package for your operating system.
- 2. Install and deploy: Run the lightweight installer and follow the on-screen instructions to deploy the software across your users' devices.
- 3. Open existing files: Launch WPS Office and directly open existing Microsoft Office documents with zero formatting loss.
Frequently Asked Questions
Why does the Set-WebServicesVirtualDirectory command fail in Exchange Online?
This command is specifically designed for on-premises Exchange Server configurations. Exchange Online manages web services automatically in the cloud, so this command is neither applicable nor available for tenant administrators.
Can I use IMAP migration for a Microsoft 365 cross-tenant transfer?
While it is technically possible for basic email transfer, IMAP migration is highly discouraged for Exchange Online tenant-to-tenant migrations because it fails to migrate calendar events, tasks, contacts, and complex folder rules.
What permissions are required for a cross-tenant mailbox migration?
Administrators must configure Azure AD applications, assign specific Migration Administrator roles, and establish formal organizational relationships and security permissions between the source and target Microsoft 365 tenants.
