Article ID: 2745710 - View products that this article applies to.
After you move a user's mailbox from an on-premises Microsoft Exchange Server environment to Microsoft Office 365, the user can't access the mailbox by using Microsoft Outlook. However, the user can access the mailbox by using Microsoft Outlook Web App.
In addition, you may see an error message in the Exchange Management Console that resembles the following after the failed remote mailbox move:
7/16/2012 9:46:01 AM  7/16/2012 1:43:08 PM  Failed to convert the source mailbox 'Primary (00000000-0000-0000-0000-000000000000)' to mail-enabled user after the move. Attempt 6/6. Error: UpdateMovedMailboxPermanentException.
This issue may occur if you disable the permission inheritance on the target user in the on-premises Active Directory schema.
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.
To resolve this issue, follow these steps:
Note In Microsoft Exchange 2010, a remote mailbox consists of a mail-enabled user who exists in the on-premises Active Directory and an associated mailbox that exists in the cloud-based service.
For more information about the cmdlets that are mentioned in this article, go to the following Microsoft TechNet websites:
Still need help? Go to the Office 365 Community
Article ID: 2745710 - Last Review: July 9, 2014 - Revision: 7.0