Microsoft traced the worldwide Microsoft 365 outage on November 12-13, 2026 to a hidden Windows bug that overwhelmed servers handling cloud connections. Its preliminary incident report says a software change shifted traffic and reduced server capacity, and Exchange Online took the greatest impact.
Service outage tied to capacity shift
The disruption ran from 4:20 PM UTC on November 12 until 4:10 PM UTC on November 13. Most users could not reach Exchange Online mailboxes through Outlook or other clients, and many saw delayed emails. Other Microsoft cloud services were also affected.
The defect came from a fix prepared for Microsoft 365 networking gateway servers. Deployment started in July, and the change ran globally for more than three months without visible problems. Microsoft said neither the defect nor that fix applies to general Windows deployments, which separates this event from a Windows desktop issue.
Inside an internal Windows process, competing tasks were waiting for access to shared resources, a condition called lock contention. Under certain traffic conditions, that consumed processor and memory capacity. Connection requests then piled up until servers stopped responding.
Traffic changes and missing capacity
Two conditions exposed the bug. About fifteen hours before the outage, Teams traffic moved from an alternative gateway to the primary gateway shared with Exchange Online. At the same time, nearly 14% of gateway server capacity was unavailable because of an unrelated issue.
Microsoft said the remaining capacity would have been enough on its own, but the combination triggered the defect. Its tests missed the issue because they focused on weaker machines, while the fault became worse on newer hardware with more cores.
Automatic recovery widened the failure
When servers failed, automated systems moved connections to healthy endpoints. That extra work triggered the same fault elsewhere and spread failures across regions in less than two hours. More than 80% of servers became unresponsive at the worst point.
Microsoft-hosted incident discussions also recorded unavailable servers placing extra load on the remaining infrastructure. A separate failure in the boundaries meant to contain faults allowed the outage to spread globally. Restarted servers quickly failed again when waiting traffic returned.
Teams, SharePoint, and OneDrive could move eligible traffic away, but Exchange Online could not fully switch paths at its operating scale. Engineers developed an update that returned Windows connection handling to its earlier working state. They removed large server groups from service, applied the change, restarted them, and restored traffic gradually.
Microsoft also added capacity and extended the email delivery window so queued messages would not be returned as undeliverable. The report remains preliminary, with repair details due November 20. For administrators, incidents EX1550543 and MO1550821 identify the disruption in service health records.
Microsoft’s published guidance said tenant or device configuration changes were unnecessary. The failure was inside Microsoft’s cloud infrastructure, not customer Windows systems.