A powerful email and collaboration platform developed by Microsoft, designed to support enterprise-level communication and productivity. Miscellaneous topics that do not fit into specific categories.
Hi @MIS
Thank you for reaching out to Microsoft Learn Q&A!
Based on your description, I understand that you're unable to complete the migration from your on-premises Exchange environment to Microsoft 365 due to a "timeout exceeded" error.
As forum moderators, we don’t have access to a dedicated testing environment to replicate specific user scenarios. However, we’re committed to providing accurate support based on the resources available to us. To better understand your situation, I’d like to clarify some points:
Question 1: When you mentioned that three user mailboxes are failing during migration, does this mean other mailboxes were successfully migrated, or are these the only mailboxes included in the current migration batch?
Question 2: What version of Exchange Server are you currently using?
Additionally, here are some key conditions required for a successful migration:
- TLS 1.2 must be enabled as the minimum required version.
- MRSProxy should be enabled and running.
- Exchange Online requires Negotiate (NTLM) authentication for MRSProxy.
- On-premises migration Admin needs to have the minimum required permissions and valid credentials.
I found an official Microsoft support article that may help. One possible cause of this error is a mismatch between the ExchangeGUID of the Exchange Online MailUser object and the on-premises mailbox. You can refer to the solution in this article: “The remote server returned an Error 404” or "HTTP request has exceeded the allotted timeout" error when you move a mailbox from on-premises Exchange Server to Exchange Online - Microsoft Support
Furthermore, other users have reported similar issues caused by internet restrictions. Please double-check your firewall, load balancer (if applicable), or other network configurations that might affect connectivity.
After reviewing the above, you can also run the Test-MigrationServerAvailability cmdlet to verify whether the error message returned matches the one encountered during migration.
Please know that while our initial response might not resolve the issue right away, your input is incredibly valuable. With a bit more detail, we’ll work together to find the best solution for you.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread