Email Migration

Fix Exchange Online Remote Mailbox Migration PowerShell Errors

Kushani NimanthikaKushani Nimanthika Nov 14, 2026 869 views

Question details

A user needs to resolve a permissions error when moving a remote mailbox to Exchange Online with PowerShell.

Fix Exchange Online Remote Mailbox Migration PowerShell Errors
Product
Exchange Online and Exchange Server
Device & OS
not provided
Scenario
A remote mailbox move succeeds in the Exchange Admin Center, but the user also needs to run it through PowerShell.
Observed behavior
The PowerShell attempt fails with a permissions error when connecting to the Mailbox Replication Service Proxy endpoint.
Before you start

Capture the complete PowerShell error and compare the credentials, target server, and migration settings used in PowerShell with those used in the Exchange Admin Center. Confirm that you have access to both Exchange Online and the on-premises Exchange management tools.

Solution 1Recommended

Check migration endpoint credentials and PowerShell permissions

Use this approach when the Exchange Admin Center succeeds but PowerShell reports an authentication or authorization error.

1
Compare the accounts

In the Exchange Admin Center, open Migration and review the migration endpoint used by the successful move. Compare its credentials and server settings with the credentials and parameters supplied in PowerShell.

2
Update the endpoint

In the Exchange Admin Center migration endpoint settings, update the credentials or create a new endpoint with a properly authorized on-premises account. If using New-MoveRequest directly, provide the appropriate remote credentials to that command instead; it does not use a migration endpoint.

3
Review role assignments

In the Exchange Admin Center, review the role assignments for the account running the move and the account used to connect to on-premises Exchange. Verify that they have the required migration and mailbox move permissions.

4
Retry the move

Use New-MigrationBatch with the verified source endpoint, or use New-MoveRequest with the appropriate remote connection parameters. If the request still fails, save the complete error for further diagnosis.

Check migration endpoint credentials and PowerShell permissions
Avoid changing permissions blindly: A permissions error can reflect different causes. Review the exact error and existing role assignments before removing or reassigning permissions.
Free Microsoft Office alternative

Work with Office files while planning your Exchange migration

WPS Office is a free, lightweight alternative for working with documents, spreadsheets, and presentations. Its familiar interface and Microsoft Office format compatibility make it easy to move everyday file work across. WPS Office does not fix Exchange migration errors or replace Exchange Online.

Document migration plans and track mailbox move progress in spreadsheetsOpen and edit Microsoft Office formats, including DOCX, XLSX, and PPTXUse a familiar interface for everyday office tasksWork with a free, lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Why does the move work in the Exchange Admin Center but fail in PowerShell?

The two methods can use different credentials, endpoint settings, or command parameters. Compare the successful migration endpoint in the Exchange Admin Center with the account and connection details used in PowerShell.

How do I check whether MRS Proxy is enabled?

In the on-premises Exchange Management Shell, run Get-WebServicesVirtualDirectory | Format-List Identity,MRSProxyEnabled. Review each EWS virtual directory that can receive migration requests.

Does New-MoveRequest use the migration endpoint configured in the Exchange Admin Center?

No. A direct New-MoveRequest uses the remote connection parameters and credentials supplied to the command. New-MigrationBatch can use a configured migration endpoint.

What should I collect if the migration still fails?

Save the complete PowerShell error, the command parameters with secrets removed, and the results of the migration server availability test. These details help distinguish permission, authentication, and connection problems.