In addition, you may see an error message in the Exchange Management Console that resembles the following after the failed remote mailbox move:
Therefore, even though the user's on-premises mailbox is marked as being moved in Exchange Server, it's not converted to a remote user mailbox as expected. The user's on-premises mailbox continues to include a usual mailbox-enabled user.
- Identify all user properties on the mailbox, and then save this information to a text file. To do this, open the Exchange Management Shell, and then run the following command:
Get-Mailbox <UserMailbox> | fl | Out-File C:\UserMailbox.txt
- Disable the user's on-premises mailbox. To do this, use one of the following methods:
- Use the Exchange Management Console to disable the user's on-premises mailbox.
- Use Exchange Management Shell to disable the user's on-premises mailbox. To do this, run the following Exchange Management Shell command:For more information about this cmdlet, go to the following Microsoft TechNet website:
- Convert the user's on-premises mailbox to a remote user mailbox. To do this, run the following Exchange Management Shell cmdlet:
Enable-RemoteMailbox -Identity <UserName> -RemoteRoutingAddress <UserName@domain.mail.onmicrosoft.com>
- After the remote mailbox is provisioned, modify any custom mailbox attributes (for example, the legacyExchangeDN attribute) that you want and that weren't assigned by an email address policy to the user account.
For more information about the cmdlets that are mentioned in this article, go to the following Microsoft TechNet websites:
Article ID: 2745710 - Last Review: Dec 16, 2016 - Revision: 1