Fix Exchange 2013 to Exchange Online Mailbox Migration Access Errors
Question details
Identify and resolve access errors during an Exchange 2013 hybrid mailbox migration to Exchange Online.

- Product
- Microsoft Exchange Server 2013 and Exchange Online
- Device & OS
- not provided
- Scenario
- An administrator is moving mailboxes from an on-premises Exchange 2013 organization to Exchange Online through a hybrid migration endpoint.
- Observed behavior
- The migration reports MapiExceptionNoAccess or an Unable to open message store error. Full Access permission alone may not resolve the problem.
Identify the affected mailbox, the external migration endpoint hostname, and the Exchange server handling the request. Ensure you have the administrative access needed to inspect the endpoint, migration reports, and firewall logs.
Check the Hybrid Migration Endpoint and Network Path
Use this approach when access errors may be caused by blocked or misdirected traffic rather than mailbox permissions.
In Exchange Online PowerShell, run Get-MigrationEndpoint | Format-List Identity,RemoteServer to identify the endpoint and external server name used for the move.
Run Test-MigrationServerAvailability -ExchangeRemoteMove -RemoteServer mail.example.com -Credentials (Get-Credential), replacing the hostname with your endpoint and supplying the appropriate migration credentials. Review any reported connection or authentication errors.
In the on-premises Exchange Management Shell, run Get-WebServicesVirtualDirectory | Format-List Identity,MRSProxyEnabled,ExternalUrl. Confirm that MRS Proxy is enabled on the relevant EWS virtual directory and that the published hostname and TLS certificate match the endpoint.
Review firewall or Cisco ASA logs and NAT rules for HTTPS traffic on port 443 between the external endpoint and the internal Exchange server. Correct any rules that drop traffic or route it to the wrong server.
Check the reverse proxy or firewall publishing rules for the EWS endpoint. Ensure that pre-authentication does not interfere with the authentication required by the hybrid migration, then retry the migration from the Exchange admin center.

Review Migration Reports and Conflicting Move Requests
Use migration reports and move-request status to determine whether the failure is specific to one mailbox or affects multiple moves.
Document Your Exchange Migration Plan With WPS Office
WPS Office is a free, lightweight, easy-to-use Microsoft Office alternative for preparing migration plans and reports. Its familiar interface and Office-format compatibility make it easy to bring existing documents and spreadsheets into your workflow. It does not repair Exchange or migrate mailboxes.

Frequently Asked Questions
Does MapiExceptionNoAccess always mean the mailbox permissions are wrong?
No. Firewall, NAT, endpoint authentication, or pre-authentication issues can also cause access errors. Check the migration report and test the external endpoint before assuming the mailbox permissions are the cause.
How can I find the server used by the migration endpoint?
In Exchange Online PowerShell, run Get-MigrationEndpoint | Format-List Identity,RemoteServer. Match the endpoint to the migration batch you are investigating.
Where can I check whether MRS Proxy is enabled?
In the on-premises Exchange Management Shell, run Get-WebServicesVirtualDirectory | Format-List Identity,MRSProxyEnabled,ExternalUrl. Check the EWS virtual directory used by the published migration endpoint.
What should I check if only one mailbox fails?
Run Get-MigrationUserStatistics -Identity user@example.com -IncludeReport in Exchange Online PowerShell and inspect the detailed report. Also check for an existing move request and review mailbox-specific permissions or errors.
Can WPS Office fix the Exchange migration error?
No. WPS Office can help you document the migration, but Exchange endpoint, network, and mailbox issues must be investigated in Exchange and the relevant network infrastructure.




