Email Migration

Fix Exchange 2010 to Office 365 Cutover Migration Endpoint Failures

Adam DavisAdam Davis Nov 14, 2026 868 views

Question details

Determine why a cutover migration cannot discover the Exchange 2010 migration endpoint or transfer mailbox data to Office 365.

Fix Exchange 2010 to Office 365 Cutover Migration Endpoint Failures
Product
Exchange Server 2010 and Exchange Online
Device & OS
not provided
Scenario
An administrator is migrating Exchange 2010 mailboxes to Office 365 using a cutover migration.
Observed behavior
The migration reports zero data transferred and returns TooManyTransientFailureRetriesPermanentException and MapiExceptionNoSupport errors. Outlook Anywhere passes connectivity tests, but Autodiscover cannot detect the migration endpoint.
Before you start

Have an affected mailbox address, migration administrator credentials, and the latest migration error details available. Confirm that your account can connect to Exchange Online PowerShell and review current Microsoft support requirements for Exchange 2010 migration.

Solution 1Recommended

Test Autodiscover and the migration endpoint

Use Exchange Online PowerShell and Microsoft's connectivity tests to identify where endpoint discovery fails.

1
Connect to Exchange Online

Open PowerShell with the Exchange Online PowerShell module installed, run Connect-ExchangeOnline, and sign in with an appropriately authorized account.

2
Test endpoint discovery

Run $cred = Get-Credential, then run Test-MigrationServerAvailability -ExchangeOutlookAnywhere -Autodiscover -EmailAddress user@example.com -Credentials $cred. Replace user@example.com with an affected source mailbox address and enter the appropriate source credentials.

3
Review external connectivity

Open the Microsoft Remote Connectivity Analyzer and run the Exchange Server Outlook Connectivity and Autodiscover tests for the affected mailbox. Review the detailed results for DNS, certificate, authentication, and endpoint errors.

4
Correct discovery issues and retest

Check the public Autodiscover DNS record and the externally published Autodiscover and Outlook Anywhere URLs. Correct any DNS, certificate, or publishing issues indicated by the test results, then rerun Test-MigrationServerAvailability.

Test Autodiscover and the migration endpoint
A passing Outlook Anywhere test is not enough: The migration service must also be able to discover and reach the required endpoints. Review the Autodiscover results even if Outlook Anywhere connectivity passes.
Free Microsoft Office alternative

Work with Office documents in WPS Office

WPS Office is a free, lightweight alternative with a familiar interface for working with Office files as you move between productivity tools. It does not repair Exchange migration endpoints or migrate mailboxes.

Open and edit Microsoft Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTXUse a familiar interface for everyday document workKeep migration plans and checklists in compatible documents and spreadsheetsMove existing Office files into a lightweight, free productivity suite
microsoft office alternative - wps office

Frequently Asked Questions

Why does endpoint discovery fail when Outlook Anywhere passes its test?

Outlook Anywhere connectivity and Autodiscover endpoint discovery are separate checks. Run Test-MigrationServerAvailability with the -Autodiscover option and review the Microsoft Remote Connectivity Analyzer Autodiscover results.

What should I check if Autodiscover cannot be located?

Check public Autodiscover DNS, the externally published URL, its TLS certificate, and firewall or proxy rules. Use the Microsoft Remote Connectivity Analyzer to identify the specific failing step.

Does TooManyTransientFailureRetriesPermanentException identify the root cause?

No. It indicates that repeated transient failures led to a permanent migration failure. Review the underlying migration report and endpoint test results for the connection or configuration error.

Can WPS Office fix a failed Exchange cutover migration?

No. The mailbox migration and endpoint configuration must be investigated in Exchange and Microsoft 365. WPS Office can be used separately to work with compatible Office documents and spreadsheets.