Microsoft blames months-old bug for global Microsoft 365 outage

A defect shipped in July to Microsoft 365 networking gateway servers combined with extra Teams traffic and reduced capacity. At the worst point, more than 80% of servers stopped responding.

Aerial view of the Microsoft headquarters campus in Redmond, Washington, with construction cranes and Lake Sammamish beyond.
File photo: Microsoft headquarters campus redevelopment in Redmond, Washington, 2021Photo: Atomic Taco / Wikimedia CommonsCC BY-SA 2.0Source

Microsoft says a defect in an update it released in July for its Microsoft 365 networking gateway servers was behind the nearly 24-hour worldwide outage on 12 November, BleepingComputer reported1.

The disruption started at 11:20 ET on Thursday 12 November and ended at 11:10 ET the next day, when Microsoft confirmed that services were fully restored1. Outlook, Exchange Online, Teams and Copilot were affected, and users lost access to email or faced lengthy waits for messages to arrive1.

In an initial post-incident report shared through the Microsoft 365 Admin Center, the company named three contributing problems: the previously unnoticed bug, extra traffic following a Teams failover, and reduced server capacity1. The update had run for more than three months without trouble, but under certain traffic patterns the bug could overload servers until they stopped responding1.

Microsoft executive Charles Lamanna described the bug as a "latent defect" that caused lock contention, which stopped machines from responding2. Lock contention happens when several processes wait on the same lock, so work stalls until it is released. Lamanna said the faulty code came from a fix written specifically for the gateway servers, and that neither the fix nor the underlying defect applies to wider Windows deployments2. He said Microsoft first observed the issue during an earlier Microsoft 365 update in July 20262.

Petri reports that the defect lay dormant since July 2026 and escaped testing because Microsoft's validation environments mostly used older hardware, while the bug was more likely to surface on newer servers with higher core counts under specific workloads3. Microsoft had recently moved Teams traffic onto the gateways that also serve Exchange Online, and a separate issue had already cut available capacity3.

Automated systems then shifted traffic to servers that were still healthy, where the same defect was triggered, according to Petri3. Lamanna said the load was spread over ever fewer servers, and within less than two hours the defect had been hit across the fleet; at its lowest point, more than 80% of servers were unresponsive2.

We are deeply sorry for the impact to all our customers

Charles Lamanna, MicrosoftITPro

Microsoft says its investigation is continuing and that it expects to publish a final post-incident report later this week1.

Sources

  1. 1
    Microsoft says months-old bug caused global Microsoft 365 outage

    IndependentBleepingComputerAccessed

  2. 2
  3. 3
    Microsoft Explains Causes of Microsoft 365 Outage

    IndependentPetriAccessed

ITANU’s newsroom system produced this article with AI and checked it against the sources listed above. How we work

ITANU Magazine

Technology news, checked against its sources