'%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 Resolve Cross-Tenant Migration RecipientTypeDetails MailUser Error
Question details
The user needs to resolve an error during a cross-tenant mailbox migration where the migration user in the target tenant lacks the required RecipientTypeDetails value.
- Product
- Microsoft Exchange Online
- Device & OS
- not provided
- Scenario
- Performing a cross-tenant mailbox migration in Microsoft 365.
- Observed behavior
- The migration fails and displays an error stating that the target object must be configured as a MailUser before the migration can proceed.
Ensure you have global administrator or Exchange administrator privileges in both the source and target Microsoft 365 tenants before attempting to modify identity configurations.
Verify and Configure Target Object as MailUser
Update the target user object's identity mapping in Exchange Online to ensure it is recognized as a MailUser, which is required for receiving the migrated mailbox.
In cross-tenant mailbox migrations, the destination tenant must have a valid object to receive the mailbox data. If this object is not correctly mapped with the 'MailUser' recipient type, Exchange Online blocks the process.
You cannot directly edit the RecipientTypeDetails attribute; instead, you must ensure the required mail attributes (such as TargetAddress and Mail) are properly synchronized or configured.
Open PowerShell as an administrator and connect to the Exchange Online environment of the target tenant using your admin credentials.
Run the command 'Get-Recipient -Identity <UserIdentity>' to check the current RecipientTypeDetails value of the target user object.
If the user is not listed as a MailUser, configure their Exchange attributes properly in the on-premises Active Directory (like setting a valid TargetAddress routing to the source tenant) and let Azure AD Connect sync the changes to the cloud.
Wait for directory synchronization to complete across the Microsoft 365 tenant. Once the object displays 'MailUser' in Exchange Online, resume your cross-tenant mailbox migration batch.
Looking for a reliable and lightweight Office alternative?
While you are dealing with complex Microsoft 365 administration and tenant migrations, your end-users still need a reliable daily productivity suite. WPS Office provides a free, lightweight, and highly compatible alternative to standard Microsoft Office installations.
- 1. Download the Installer: Go to the official WPS website and download the free WPS Office installer to your device.
- 2. Install WPS Office: Run the downloaded installation file and follow the straightforward on-screen prompts.
- 3. Start Creating: Open WPS Office and instantly access your existing Word, Excel, and PowerPoint documents without formatting issues.
Frequently Asked Questions
What does the RecipientTypeDetails MailUser mean in Exchange Online?
A MailUser (or mail-enabled user) is an object in Exchange Online that has an email address and an external routing address (TargetAddress), but does not have a fully licensed mailbox yet in that specific tenant. This state is required in the target tenant during cross-tenant migrations.
How long does it take for directory changes to synchronize during migration?
After correcting the recipient configuration on-premises, Azure AD Connect sync cycles typically take up to 30 minutes. Once synced to Azure AD, Exchange Online directory propagation can take an additional 5 to 60 minutes.
Can I manually change RecipientTypeDetails in the Exchange admin center?
No. RecipientTypeDetails is a calculated property based on underlying Exchange attributes such as ExchangeGUID, Mail, and TargetAddress. You must correct those foundational attributes so that Exchange automatically calculates the object as a MailUser.
Where can I find more help for cross-tenant identity mapping errors?
You can refer to the official Microsoft Learn documentation on cross-tenant identity mapping. For complex scenarios, post your query with error details in the Microsoft Q&A Exchange Online community.
