Microsoft Details Causes Behind Global 365 Service Disruption
A combination of a latent software bug, increased network traffic, and reduced server capacity triggered a cascading outage across Microsoft 365 services on November 12.
- A software bug introduced in July 2026 remained undetected until it caused a major outage on November 12.
- The incident was exacerbated by a spike in network traffic and a 14% reduction in overall server capacity.
- At the height of the disruption, over 80% of affected networking gateway servers were unresponsive.

Microsoft has identified three concurrent factors that resulted in a widespread service disruption on November 12, affecting major platforms including Exchange Online, Teams, SharePoint, and OneDrive. According to the company, the incident was triggered by a previously undetected software defect, a sudden surge in network demand, and a concurrent reduction in available server capacity.
The Root Cause of the Failure
The primary driver of the outage was a latent defect within a code change first implemented in July 2026. This software bug involved lock contention in an internal process, which led servers to become unresponsive under specific high-traffic conditions. The issue remained dormant for over three months because the company's internal load testing utilized different hardware configurations and traffic patterns than those found in the live environment. Microsoft noted that the flaw was particularly impactful on newer, higher-capacity server models, while their testing had primarily focused on older hardware.
Cascading Infrastructure Impact
The vulnerability was exposed when two additional conditions were met. Approximately 15 hours prior to the outage, a failover operation shifted Teams traffic to the primary gateway, significantly altering and increasing the load. Simultaneously, the network was operating with roughly 14% less server capacity due to an unrelated issue from the previous day. While these factors were within manageable limits individually, their convergence during peak usage periods initiated a failure.
As individual servers began to stop responding, the system’s automated traffic management redirected requests to the remaining operational hardware. This redistribution unintentionally overwhelmed the healthy servers, causing the defect to manifest across the network in a rapid, cascading sequence. More than 80% of the impacted networking gateway servers became unresponsive at the peak of the event. Furthermore, existing isolation mechanisms failed to prevent the disruption from spreading globally across network partitions.
Challenges in System Recovery
Recovery efforts proved complex because the company’s automated restoration protocols were not designed to manage a failure of this scale. As engineers brought servers back online, they were immediately overwhelmed by a backlog of pending requests, causing recurring outages. Microsoft confirmed that while some services like Teams and OneDrive were able to leverage failover paths to restore functionality sooner, others such as Exchange Online faced longer delays. The technical team eventually identified the faulty code and deployed a fix to stabilize the infrastructure. A comprehensive review of the incident and intended corrective measures is expected to follow.
- The root cause was a lock contention defect in networking gateway servers.
- Testing failed to uncover the bug because it did not accurately reflect real-world hardware or traffic.
- Standard automatic recovery systems were unable to cope with the cascading nature of the failure.
- Microsoft has identified three concurrent factors that resulted in a widespread service disruption on November 12, affecting major platforms including Exchange Online, Teams, SharePoint, and OneDrive.
Spotted an error? · Our editorial policy
UP NEXTSanjay Kapoor Stars in ‘Unexpected – Safed Sach’ Based on 2024 Dehradun CaseSwipe more stories · TechnologyQuick cards, a few lines each. Tap to open.More from Technology

Anthropic Researcher Claims AI-Assisted Proof for the Riemann Hypothesis

Grand Theft Auto VI Becomes Largest Entertainment Launch in History

Trump Backs Jensen Huang’s Return to Nvidia Amid Board Resistance and Intelligence Scrutiny
