Microsoft 365 outage: Hidden flaw, traffic surge, 14% server loss hit 80% servers
Synopsis
Key Takeaways
A hidden software defect, a sudden spike in network traffic, and a simultaneous reduction in server capacity combined to trigger the major global Microsoft 365 outage on 12 November 2026, the company confirmed on Monday, 16 November. The disruption, which affected services including Teams, OneDrive, SharePoint, and Office applications, was among the most widespread in the platform's recent history.
What Caused the Outage
According to Microsoft, the fault originated in a networking layer that sits in front of several Microsoft 365 services. A hidden software flaw caused servers to become overloaded and stop responding under specific conditions. The flawed code had been deployed in July and had been running globally for over three months without incident — going undetected because internal testing environments used different traffic patterns and hardware configurations than live production systems.
Approximately 15 hours before the outage began, Teams traffic was migrated from a backup system to the primary system, sharply increasing load on the affected infrastructure. At the same time, nearly 14 per cent of server capacity was offline due to an unrelated issue from the previous day. Neither factor alone would have been sufficient to cause a failure, but together they exposed the latent defect, causing requests to accumulate until servers stopped responding during peak US traffic hours.
How the Failure Spread Globally
Microsoft's automatic failover systems initially attempted to reroute users to healthy servers. However, this redirection increased load on functioning infrastructure, raising the probability of cascading failures. A separate, unrelated issue also disabled internal containment systems — safeguards designed to restrict failures to a single geographic region — allowing the fault to propagate across Microsoft's global network.
At the peak of the incident, more than 80 per cent of the affected servers had stopped responding, according to the company's Executive Vice President for Copilot, Agents and Platform, who apologised to customers and shared the early findings in a post on X.
Why Recovery Took So Long
Recovery proved difficult because servers that returned online were immediately overwhelmed by a backlog of pending requests and stopped responding again. Microsoft acknowledged that its existing automatic recovery mechanisms were not designed to handle a failure at this scale. Engineers ultimately identified the faulty code and developed a targeted update that restored normal operations.
What Microsoft Has Promised
The company said it will publish a full post-incident review — including additional technical details and corrective measures — later this week. The review is expected to address structural gaps in testing protocols, failover architecture, and regional containment systems that the November outage exposed. This comes amid growing scrutiny of cloud-service resilience after a series of high-profile global outages across major providers in recent years.