The SharePoint Migration Agent was working normally until today, but it is now stuck in the "Cannot Scan" state. I can't add new source paths or scan any existing ones. I completely uninstalled the agent, removed it from the migration administration center, and reinstalled it, but the problem remains. Has anyone encountered this issue or found a workaround?
3 Answers
There may also be a wider Microsoft issue involved. We’ve had an unrelated device-enrollment automation script hang indefinitely at the same time, so it’s worth checking tenant service health and waiting for Microsoft to acknowledge a possible outage before making major changes.
We’re seeing something similar. Migration tasks can still be created, but the agent won’t accept a source path or start a scan. It worked normally recently and then stopped without any configuration changes. The service health dashboard doesn’t appear to show an incident yet, so this may be a backend issue or a newly introduced service problem.
For on-premises migrations to SharePoint or OneDrive, some administrators avoid the built-in migration agent because it can be unreliable. A third-party migration tool or another supported migration route may be worth considering if this becomes a recurring issue.
I’ve completed hundreds of migrations with this tool without trouble until now. I’m open to alternatives, but I’d prefer to identify whether this is just a temporary service outage first.
That matches what I’m seeing exactly. Hopefully the service status gets updated soon, because reinstalling the agent didn’t make any difference.