LIVE

How a latent software bug and server strain caused a massive Microsoft 365 outage

🧠 AI Analysis 2 min read 👁 7

A preliminary incident report from Microsoft reveals that a combination of a hidden gateway defect, traffic shifts, and reduced capacity triggered a nearly 24-hour outage affecting Microsoft 365 and Exchange.

How a latent software bug and server strain caused a massive Microsoft 365 outage🧠AI Analysis

Photo: arstechnica.com

Key points

  • Microsoft 365 and Exchange experienced a nearly 24-hour outage between November 12 and 13.
  • The disruption was driven by a hidden software defect, unexpected traffic shifts, and a 14 percent deficit in server capacity.
  • Microsoft confirmed the incident was technical and unrelated to cybersecurity or artificial intelligence.

A preliminary Post-Incident Report published by Microsoft details how a sequence of three minor technical failures resulted in one of the most significant service disruptions in the company's history. The incident took place between November 12 and November 13, knocking out large portions of the Microsoft 365 and Exchange infrastructure for nearly 24 hours and disrupting operations across various businesses and public offices.

The Anatomy of the Outage

The root of the issue was a dormant software defect introduced into Microsoft's cloud gateway during updates deployed as early as July. According to the company, pre-release testing failed to spot the bug because testing hardware lacked the higher CPU core counts found on newer production machines, which ultimately contributed to the system lockout.

This hidden flaw was triggered when routine network maintenance prompted a shift in Teams traffic to the primary gateway, altering request patterns. Compounding the issue, the gateway server fleet was operating at 14 percent below optimal capacity due to an existing fault. When US business hours peaked, the resulting surge in demand overwhelmed the resources, causing over 80 percent of the affected gateway servers to freeze.

Recovery Challenges and Prevention

Standard recovery procedures, such as system reboots or rollbacks, proved ineffective because massive queues of waiting requests immediately re-triggered resource exhaustion upon restart. Engineers ultimately had to apply targeted software updates to resolve the lockups gradually.

Microsoft explicitly stated that the technical failure was entirely unrelated to cyberattacks or artificial intelligence agents. To prevent similar incidents, the company has incorporated additional server capacity and introduced new traffic-distribution guardrails.

What to watch next: Further updates from Microsoft regarding why regional isolation systems failed to contain the incident.

Source arstechnica.com — arstechnica.com/gadgets/2026/11/microsoft-details-how-three-problems-co… ↗

Contact the newsroom

Got a tip, a proposal or a partnership question? Write to us and we will reply shortly.