If you run OneDrive or SharePoint migrations across tenants or geographies, you likely hit a wall starting 18:29 UTC on 28 October. Microsoft's own admin centre tracked the fault for 117h 15m, and the cause sat entirely on Microsoft's side of the fence.
Started
18:29 UTC
Duration
Lasted 4d 21h
Source
IsDown
Next time
Microsoft 365 is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
What happened?
The incident began at 18:29 UTC on 28 October and ran for 117h 15m before Microsoft called it resolved. The title Microsoft settled on was "Admins were unable to complete Microsoft OneDrive or SharePoint site migrations", though the first update actually described a narrower problem: cross-tenant OneDrive migrations stuck in a Scheduled or Queued state. By the fourth update the scope had widened to cover newly initiated Cross-Geo and Cross-Tenant moves for both OneDrive and SharePoint failing to start. Microsoft was explicit that this applied only to the M365 Multi-Geo and Cross-Tenant Migration features, and that other migration routes such as Migration Manager or third-party tools were untouched. For the first day, Microsoft's updates described investigation rather than resolution: reviewing move request jobs, then isolating the underlying migration infrastructure. A fix was identified and tested before deployment began, with Microsoft estimating around eight hours for the rollout to complete and noting that some organisations would see relief as sections of the service received the update. The final update, filed at 23:57 UTC on 2 November, states the deployment completed successfully and that Microsoft was contacting a sample of previously affected admins to confirm the fix held. No post-mortem has been published beyond that confirmation. No components were listed as affected in Microsoft's own breakdown, and no user reports were filed during this window on our side.
Learning
This incident sat entirely inside Microsoft's backend migration infrastructure, not in anything an external uptime check against your own domain or a login page would ever touch. A synthetic probe hitting Microsoft 365's main service endpoints would have stayed green throughout, because the sign-in, mail and file-access layers were never the problem. The fault was specific to the machinery that moves OneDrive and SharePoint sites between tenants and geographies, something you can only notice by actually running a migration job and watching it stall in Scheduled or Queued. That is a layer no amount of watching your own product's uptime will reveal, since the job queue lives on Microsoft's infrastructure, not yours. Microsoft's 90-day record shows 59 incidents with a median duration of 8 hours 12 minutes, so a stuck migration running past four days was well outside the typical pattern. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.