SPMT and Migration Manager Errors: An Endpoint, Disk Space and Scan Checklist
By Mirko Peters ·
SPMT reports missing disk space, or the Migration Manager agent says Connected but cannot scan? Check the required endpoints, the local working folder, the target storage and the agent settings in this order.
A file share or on-premises SharePoint migration runs well for weeks. Then a library fails with a disk space message, a firewall refuses an endpoint, or the Migration Manager agent stays "Connected" and refuses to scan. Four Microsoft community threads from late 2025 to late 2026 show these cases. Only one of them has a reply marked as the solution, so this article combines them with the current Learn pages. It is a troubleshooting guide, not an official Microsoft procedure.
Key points
- Allow the full endpoint lists from Microsoft Learn, including api.office.com for SPMT and the scan endpoints for Migration Manager. A thread advises doing this by host name, not by IP address.
- A firewall that rejects an entry with https:// in it may need just the host name in an FQDN object, as reported in a thread that marked this as the solution.
- SPMT disk space errors that Learn documents point to the local working folder, so check free space on the migration computer first, then the storage of the target site.
- 'Cannot scan' with a connected agent had no confirmed fix in the threads. One asker had a support case that Microsoft treated as a known issue.
- Keep the failure report, the exact error code and the time (UTC) ready, because most threads ended with 'open a support case'.
What the symptoms look like
- Endpoint: The firewall of an SPMT computer rejects
https://api.office.comas an invalid entry. The poster had read that the API was deprecated, yet the SPMT prerequisites page still lists it (August 2026). - Disk space: A migration from SharePoint 2019 to SharePoint Online fails for two libraries with "There isn't enough disk space in the target site collection" and "Not all the items in the package have been migrated". The poster says the destination has plenty of space (August 2026).
- Cannot scan: A Migration Manager agent shows Connected but "Cannot scan". Migrations had worked until mid-September. Reinstalling the agent did not help, and the asker saw failed SSL requests to the Microsoft migration endpoints (October 2026).
- Certificate sign-in: After reinstalling the agent with certificate-based authentication, Add Source Path on the scan tab is greyed out and the agent log repeats
token_not_found(November 2025).
Step 1: Check the endpoints
Learn lists the endpoints for both tools as HTTPS URLs. For Migration Manager it says the agent sends requests to these endpoints and receives responses, that the endpoints can never call Migration Manager, and that the agent does not open a port for remote connections.
For SPMT, the Learn prerequisites page lists, among others:
- Authentication:
login.microsoftonline.com,login.windows.net,aadcdn.msftauth.net,aadcdn.msauth.net,secure.aadcdn.microsoftonline-p.com - Content move and validation APIs:
api.office.comandgraph.windows.net - Azure migration queues and storage:
.queue.core.windows.netand.blob.core.windows.net - Destination:
*.sharepoint.com - Graph for tenant and site information:
graph.microsoft.com
For Migration Manager, the Learn prerequisites page adds scan-related endpoints, for example api.mmp.svc.cloud.microsoft, odyssey.mmp.svc.cloud.microsoft, odyssey.prod.migrations.microsoft.com and several SignalR hosts. api.prod.migrations.microsoft.com is listed there as a requirement for the Migration Manager web UI. Always copy the current list from the page, because it changes. The introduction of the page also names production.odyssey.ops.mover.io for SignalR connections, and that host is not in its table, so read the text around the table.
The reply marked as the solution in the api.office.com thread gives this advice:
- Do not treat the firewall's rejection as proof that the endpoint is unneeded.
- Allow the host name over TCP 443 from the migration computer, and use DNS-based rules, not IP addresses. This is the thread's advice. Learn names no port.
- If the firewall field rejects the entry, enter only the host name in an FQDN object. The
https://prefix may be what the field refuses. This part is advice from the thread, not from Learn. - Test name resolution and an outbound TLS connection from the migration computer, then run the scan again.
A quick test from the migration computer:
``powershell Test-NetConnection api.office.com -Port 443 Test-NetConnection odyssey.prod.migrations.microsoft.com -Port 443 ``
A wildcard such as *.blob.core.windows.net cannot be tested as written. Test a real host name from your tenant instead. A reply in the "Cannot scan" thread also asks you to rule out proxy, firewall, SSL inspection or certificate changes between the agent and these hosts. I did not see SSL inspection mentioned on the two prerequisites pages, so treat that point as a community suggestion.
Step 2: Check free space on the migration computer
For SPMT, Learn's troubleshooting page documents these errors:
- "Scan File Failure: Not enough disk space to pack the file": the disk space for the migration working folder is too small for the size of the source file. Enlarge the working folder and try again.
- Error 0x02040012: the temporary storage on the local computer is too low, because SPMT caches the package in the working folder. Expand the temporary storage and retry.
Learn recommends 150 GB of free local storage for the computer that runs SPMT, in both the recommended and the minimum hardware profile. Check the system drive and the drive of your working folder. The working folder %appdata%\Microsoft\MigrationToolStorage is mentioned on the troubleshooting page, and several errors there say its files and folders must stay closed during a migration.
In the SharePoint 2019 thread, a reply from a community member with an MVP title said the message most likely points to local temporary storage, not to SharePoint Online limits. The Learn page lists the local errors above, and it does not list the exact "target site collection" wording. So the local check is the best-supported first step.
Step 3: Check the target site and tenant storage
Another reply in the same thread said the second message, "Not all the items in the package have been migrated", is probably a side effect of the first error. It suggested checking the storage limit of the destination site (in the SharePoint admin center under Active sites), the total tenant storage, and old versions and recycle bin content. That reply and the other one were not marked as a solution, and the poster did not report a result.
If the target is full, keep in mind what Learn says about storage: usage reports can lag by up to 48 hours, and in Manual storage mode each site has its own limit.
For the "not all items migrated" part, the Learn troubleshooting page lists error 0x01710009 twice: once with the text "Errors or time-out for Server Processing the file: Not all the items in the package are migrated", and once as a failure due to job end failures where some items failed in the package, with the advice to restart the migration. For missing dependencies on list items (error 0x01410010), check FailureSummaryReport.csv and make sure the dependencies are in the migration scope. The thread also suggests retrying one failed library in smaller batches, then running an incremental migration to catch missing items. That is a community suggestion, not a Learn step.
Step 4: Check the Migration Manager agent
Learn's Migration Manager troubleshooting page covers a few agent cases that are not "Cannot scan" but look similar:
- Agent disconnected: possible causes include network health on the agent computer, a password change or similar critical change to the tenant admin account (all agents must then be reinstalled), a failed auto-upgrade, and token expiry.
- Scan stays Queued: only agents in the Default agent group can be scheduled. If no agent is in that group, change the agent's group to Default.
- Failure to submit a job (0x01610002): the page recommends antivirus exceptions for
microsoft.sharepoint.migration.clientservice.exeandmicrosoft.sharepoint.migration.mthost.exe.
In the "Cannot scan" thread, one reply listed Microsoft's agent setup steps and asked whether all shares or only some are affected. An automatically generated answer in the same thread suggested editing an agent configuration file. Such answers are not evidence, and I found nothing like it in the Learn pages, so do not apply that change without a statement from Microsoft. The asker wrote that a support engineer told them it is a known issue being worked on. Microsoft staff did not confirm this in the thread. If your symptoms match, go to support early.
Step 5: Certificate sign-in for the agent
The certificate thread has no confirmed fix. A Microsoft staff moderator pointed to a missing or incomplete certificate configuration file as the reason for token_not_found, and asked to check the app permissions. The asker answered that the file had been checked and the agent reinstalled many times. The moderator then suggested endpoint checks and granting the app Read on the admin site, and the asker reported that the endpoint tests passed and the problem stayed. The last moderator comment suggested Microsoft Service Hub if the problem remains. No reply confirms a fix. I could not confirm the file format or permissions in the Learn pages I read, so use the official Migration Manager setup page for certificate authentication and do not rely on the thread.
Step 6: Collect evidence
Learn names these log locations for Migration Manager: %AppData%\Microsoft\SPMigration\Logs for failed tasks, and the Migration\MigrationTool[tenant_site] folder under %AppData%\Microsoft\SPMigration\Logs for the task report of a completed task (or under your custom working folder). Sort the subfolders by modified time and open the one closest to the task start. The SPMT page does not list its own log folders, so open the failed task's report in the tool (as one reply suggests). Note the first failed item, the error code, the correlation ID and the time in UTC, and add the destination site URL.
Limits and open points
- Only the endpoint question has a marked solution, and even there the asker wrote no confirmation.
- The disk space, "Cannot scan" and certificate threads are unresolved. Treat the steps for them as a checklist for narrowing the problem.
- The Migration Manager prerequisites page shows a visible update date of July 2025. Compare it with what the portal asks for today.
Related
Sources
- Microsoft Learn: SPMT prerequisites and required endpoints
- Microsoft Learn: Troubleshooting common SPMT issues
- Microsoft Learn: Migration Manager prerequisites and endpoints
- Microsoft Learn: Troubleshoot Migration Manager file migrations
- Microsoft Community Hub: SharePoint Migration Tool issue (August 2026)
- Microsoft Community Hub: SPMT Error help (August 2026)
- Microsoft Q&A: Microsoft 365 Migration - Cannot Scan (October 2026)
- Microsoft Q&A: Migration Manager (Certificate Authentication) Add Source Path greyed out (November 2025)