Forum Discussion
Exchange 2016 Hybrid, move mailbox failed
We have configured the exchange hybrid config a while ago and tested the migration and succesfully moved a mailbox from on prem to Exchange Online.
Yesterday was planned to start the migration for all the users, but as we know there were problems.
Today they should be fixed, but when the migration status shows below
11/14/2026 11:11:29 [AMZPR05MB943814] The Microsoft Exchange Mailbox Replication service 'AMZPR05MB943814.eurprd05.prod.outlook.com' (15.21.592.10 ServerCaps:1FFFFFFFFF, ProxyCaps:37FFFFFFFFFFFFFFFFC7DD2DFDBF5FFFFFCB07EFFF, MailboxCaps:, legacyCaps:1FFFFFFFFF) is examining the request.
11/14/2026 11:11:29 [AMZPR05MB943814] Resource information was found with reservation.
11/14/2026 11:11:29 [AMZPR05MB943814] Content from the Shard mailbox (Mailbox Guid: ef34477b-0084-487b-a27f-e89da129956e, Database: eurprd05.prod.outlook.com/f670e037-4a2a-4fbe-aa9a-2132c89edaf6) will be merged into the target mailbox.
11/14/2026 11:11:29 [AMZPR05MB943814] Connected to target mailbox 'customer.onmicrosoft.com\0a4112f9-5389-4200-85c9-765bf37cb330 (Primary)', database 'EURPR05DG745-db166', Mailbox server 'AMZPR05MB943814.eurprd05.prod.outlook.com' Version 15.21 (Build 592.0).
11/14/2026 11:11:30 [AMZPR05MB943814] Transient error CommunicationErrorTransientException has occurred. The system will retry (5/60, 5/605).
I created a new migration point successfully , but the errors above are the same.
inbound/outbound firewall settings were not changed between the first successfull migration and today.
Is this still something left over from the mayor outage Yesterday , or can someone point me in the right direction ?
Kind regards
Jacco Dominicus
6 Replies
- SelinaKnowIron Contributor
Since the endpoint and MRS Proxy tests are succeeding, I would leave one move request in place and let its transient retries continue instead of recreating endpoints again. Check the tenant service-health entry for the same timestamps and attach the full move report to the existing Microsoft support case. Repeatedly restarting the batch can make the timeline harder to diagnose.
- Jacco_DominicusCopper Contributor
The move reaches the Exchange Online target but then retries with CommunicationErrorTransientException; a successful endpoint creation and unchanged firewall rules do not identify the failing side. The excerpt alone also cannot establish whether the outage caused it. While the support case is being opened, capture the detailed report for one affected mailbox from Exchange Online PowerShell with Get-MoveRequestStatistics -Identity <mailbox> -IncludeReport, and give it to support privately. Check the report’s failure side, nested error and timestamps rather than assuming the transient label is the root cause. For the existing endpoint, run Test-MigrationServerAvailability -Endpoint <endpoint name>; interpret an OAuth endpoint result carefully, since Microsoft says that test can validate token retrieval without connecting to the remote host. On the on-premises Exchange servers, verify the EWS virtual directory has MRS Proxy enabled. Compare findings with the earlier successful move and the tenant’s service-health advisory before changing configuration.
- Jacco_DominicusCopper Contributor
Hello Jamony
Did the test and all were status succes.
have to wait on MS to respond, if that is not quick enough we will goging to use a third party tool to do the migration
regards
Jacco Dominicus
- Jacco_DominicusCopper Contributor
That was also in my mind before i mqde this post.
Migration was planned this weekend, anf if someone had a quick fix that would be nice.
I wil make a support ticket in the clients o365 tenant regarding this
Thanks
Jacco dominicus
You might want to open a support ticket and ask about this, there might be indeed some impact due to the outage (i.e. Microsoft might have decided to deprioritize migration scenarios as "non-essential"). Though they haven't mentioned anything publicly about it, so you'll have to go through support.