When you try to enable or disable an archive mailbox for an existing Exchange Online user, or when you try to move a mailbox from Exchange Online to an on-premises environment, you receive an error message that resembles one of the following:
Error: UserAlreadyBeingMigratedException: The user '<User Email Address>' already has a pending request. Please remove the existing request and resume the current batch or start a new batch for this user.
Mailbox '<User Display Name>' has a completed move request associated with it. Before you create a new move request for the mailbox, run the Remove-MoveRequest cmdlet to clear the completed move request.
Mailbox '<User Display Name>' has move status <move status>. You can't enable or disable an archive while the mailbox is being moved.
When you run the Get-MoveRequest | fl command to examine the move request, you verify that the request is an Office 365 datacenter move request. This is indicated by the IntraOrg flag.
This problem occurs because failed move requests are not yet removed from the system.
To maintain service health, Exchange Online regularly moves mailboxes between different servers. Completed Office 365 datacenter move requests are cleaned up very quickly. Failed Office 365 datacenter move requests may remain somewhat longer but are still cleaned up after some time. These failed move requests do not affect users. The service will retry the move in the future, if it's required.
Generally, if an internal datacenter move doesn't affect your ability to perform administrative tasks, you can safely ignore the error messages.
If management tasks are affected by the move requests, follow these steps: