The administration of a hybrid deployment that connects on-premises Exchange Server with Exchange Online, enabling seamless integration and centralized control.
Anyone running Exchange SE and seeing this issue?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Since ~12 Oct 2026 23:53 UTC, all onboarding moves (Exchange 2019 CU15 -> Exchange Online, Modern Hybrid / Hybrid Agent) fail with TooManyTransientFailureRetriesPermanentException / CommunicationErrorTransientException right after "Connected to target mailbox". Test-MigrationServerAvailability still succeeds.
Workaround that made us succeed with the migration at the end: renaming the local Administrator account on the Exchange server makes the moves work again.
Is anyone else seeing this? Is there a known issue or incident ID from Microsoft?
The administration of a hybrid deployment that connects on-premises Exchange Server with Exchange Online, enabling seamless integration and centralized control.
Anyone running Exchange SE and seeing this issue?
Thank you so much for sharing this workaround! You saved me hours of troubleshooting!
I was experiencing the exact same issue with Exchange 2016 Hybrid, trying to offboard a mailbox from Exchange Online back to our on-premises server.
The migration endpoint connectivity tests were all successful, but the actual mailbox move kept failing with TransientFailureTarget and Negotiate Unauthorized, with 0 bytes transferred.
After reading your post, I checked Event ID 4625 on our Exchange server and found repeated failed NTLM authentication attempts using administrator with a blank Account Domain.
I renamed the local Administrator account on our Exchange server to something else (leaving the domain Administrator account unchanged), resumed the migration, and it immediately started working!
The migration is now progressing and transferring data!
Really appreciate you taking the time to share your findings. Hopefully Microsoft will investigate and address the underlying issue.
Thanks again!
I renamed the local admin and the service user for the migration endpoint. First it works fine but on the next day I get the same error again. Do someone has the same issue or has an idea to solve my problem
I have multiple clients running Exchange SE, and I’m experiencing the same issue with all of them. Thanks a lot for the tip! I’ve been trying to figure out the problem for two days. I had correctly identified it as a credential issue, but even when using a different account instead of the administrator account, I was still encountering the same problem.
Thank you @Dario Steck (dplan AG) , wow most random issue \ bug i've seen in a while. Again thank you for sharing!