Microsoft 365 Migration - Cannot Scan

Question

Microsoft 365 Migration - Cannot Scan

sb330 0

We are working through legacy file share migrations, these files sit in an on-prem server. We have installed the newest agent and have had successful migrations as of 9/16. However now the agent shows connected but in a state of cannot scan, we do not see any blockers from our security side, and have only seen 3 updates since the last successful migration. Those updates are KB5129238, KB5126048, and KB5122875. Removal and reinstallation of the agent did not solve the issue. The only other clue that i see is that there appears to be failed SSL requests for odyssey.prod.migrations.microsoft.com & api.prod.migrations.microsoft.com.

sb330 0 Reputation points

2026-10-06T16:16:39.39+00:00

I had a ticket [Moderator note: Personally Identifiable Information removed]) open about this issue, it appears that this is a known issue and is being worked on and we are currently awaiting ETA.
Elena-VH 2,130 Reputation points Independent Advisor

2026-10-06T16:20:49.33+00:00

Dear sb330,

Thank you for the update. Since you already have a support case open and Microsoft is currently investigating, at this point, I recommend continuing to work with the support engineer handling the case, as they will have access to the latest internal updates and any available workaround or resolution once it becomes available.

If Microsoft Support has identified this as a known issue, please feel free to share any public details or workaround they provide, as it may help other community members experiencing the same behavior.

Thank you for taking the time to update the thread. I hope the engineering team is able to provide a resolution soon.

2 answers

Your answer

sb330 0 Reputation points

2026-10-06T16:16:39.39+00:00

I had a ticket [Moderator note: Personally Identifiable Information removed]) open about this issue, it appears that this is a known issue and is being worked on and we are currently awaiting ETA.
Elena-VH 2,130 Reputation points Independent Advisor

2026-10-06T16:20:49.33+00:00

Dear sb330,

Thank you for the update. Since you already have a support case open and Microsoft is currently investigating, at this point, I recommend continuing to work with the support engineer handling the case, as they will have access to the latest internal updates and any available workaround or resolution once it becomes available.

If Microsoft Support has identified this as a known issue, please feel free to share any public details or workaround they provide, as it may help other community members experiencing the same behavior.

Thank you for taking the time to update the thread. I hope the engineering team is able to provide a resolution soon.

Answer 1

For file share migrations, an agent state of Cannot scan can be expected in US projects after April 1, 2023. In that configuration, the Scans tab becomes read-only for US projects, and agent status changes from Enabled to Cannot scan. Only EU projects keep the agent status as Enabled for scans.

If scan capability in the US project is required, reconfigure each agent to connect to the US project for scanning:

Open Task Manager and select the Services tab.
Right-click SharePoint Migration Service and select Stop.
Open this file: %AppData%\Microsoft\SPMigration\bin\Microsoft.SharePoint.Migration.ClientShared.dll.config
Under AppSettings, add:

<add key="UseUSScan" value="1" />

Return to Task Manager.
Right-click SharePoint Migration Service and select Start.

Since reinstalling the agent did not help, this configuration issue is the documented path that matches an agent showing Connected but Cannot scan.

Also verify the migration prerequisites and required endpoints, because scanning requires the required endpoints to be enabled, and the scan feature needs two additional endpoints. If scanning remains unavailable after the configuration change, review the required endpoints configuration.

References:

Answer 2

Dear sb330,

I understand that the Migration Manager agent is showing as Connected but Cannot scan, despite successful file share migrations on 9/16 and reinstalling the latest agent.‌

First of all, I recommend reconfiguring the Migration Manager scan settings and verifying that the agent is properly associated with the migration project. For more information, please refer to Step 1: Set up Migration Manager agents and Step 2: Scan and assess file shares

Additionally, because you are seeing SSL failures when connecting to odyssey.prod.migrations.microsoft.com and api.prod.migrations.microsoft.com, please verify that these endpoints are reachable from the migration server and that no firewall, proxy, SSL inspection, or certificate-related changes are blocking the connection. For reference: Check prerequisites and settings

If the issue still persists, to help narrow down the issue, could you please provide some additional information?‌

Does the problem occur with all file share migration sources, or only specific shares?‌
Is the issue affecting a single migration agent or multiple agents?‌
What is the exact error message shown in the Migration Manager portal or in the agent logs when a scan is initiated?

For more information and troubleshooting steps when using Migration Manager for file share migration, please refer to: Troubleshoot Migration Manager file migrations

Note: Since this is a community forum, please understand that I don't have access to your tenant, migration project, or Microsoft's backend systems.

If you have any questions or if I have misunderstood anything, please feel free to reach out. I'm looking forward to your update.