A Windows server defect introduced in July 2026 triggered a global Microsoft 365 outage that disrupted Outlook, Teams, and Copilot for nearly 24 hours, according to a preliminary post-incident report from Microsoft.
The disruption began at 4:20 PM UTC on November 12 and lasted until 4:10 PM UTC on November 13. Exchange Online experienced the most significant impact, preventing users from accessing mailboxes or sending and receiving emails. Because several other services depend on Exchange Online, users also reported issues with Teams, Copilot, SharePoint, and OneDrive.
Microsoft identified a defect in a Windows update deployed to Microsoft 365 networking gateway servers in July. The bug caused an internal Windows process to experience lock contention under specific workloads, which exhausted CPU and memory resources and rendered servers unresponsive. The company noted the defect escaped testing because laboratory hardware used fewer CPU cores than the production environment, making the issue less likely to emerge during evaluation.
The outage was exacerbated by two additional factors. Approximately 15 hours before the disruption, Microsoft Teams traffic was automatically redirected to the primary gateway shared with Exchange Online. Additionally, 14% of the networking gateway's server capacity was already unavailable due to an unrelated issue from the previous day. As servers became unresponsive, automated traffic-management systems redirected requests to the remaining operational machines, creating a cascading failure that overwhelmed the infrastructure.
Within two hours of the initial failure, more than 80% of the networking gateway servers had stopped responding. Microsoft stated that safeguards designed to contain failures within individual regions failed to prevent the disruption from spreading globally. The company clarified that the defect was specific to the Microsoft 365 gateway infrastructure and does not affect broader Windows deployments.
Engineers eventually restored services by deploying a fix that returned connection-handling code to its previously functional state. Recovery was complicated by the fact that servers frequently became unresponsive again after being restarted and receiving accumulated traffic. Webmail availability returned to normal levels worldwide by 2:17 PM UTC on November 13.
Microsoft confirmed the incident was a technical failure and found no indication of malicious activity or involvement from AI agents. The company has since implemented additional traffic-distribution safeguards, expanded infrastructure monitoring, and increased capacity. A final report detailing further corrective measures is expected by November 20, 2026.














