Skip to content
See the World Through ScienceA project of ALLATRA

Microsoft Says Three Faults Had to Coincide to Take Down Microsoft 365

AI & Technology

Republish this story

Our work is licensed under Creative Commons BY-NC 4.0. You may republish this piece for free — with credit to ALLATRA Media and a link to the original, unedited beyond length trims, and not for commercial use.

Read the full license

A long, low data center building with rows of rooftop cooling units stands behind a fence across dry grassland under a blue sky.
Cooling plant lines the roof of a server campus run by Microsoft on the high plains, photographed July 18, 2026. The gateway that stalled fronts Exchange Online from company sites like this one (illustrative)."Microsoft Datacenter in Cheyenne, Wyoming" by Tony Webster, via Flickr, CC BY 4.0, cropped

Microsoft has published a preliminary account of the Microsoft 365 outage of Nov. 12, 2026, and says three faults had to coincide. Charles Lamanna, a Microsoft executive vice president, set out "three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services" in a post on Nov. 16, 2026.

Lamanna describes his statement as an abridged version of a preliminary report, and says a final post-incident review is still to come. He writes that the defect came from a fix prepared for the Microsoft 365 networking gateway servers alone, and that "neither the underlying defect nor the fix applies to broader Windows deployments."

He names three. A latent defect, first deployed in July 2026, that made servers stall under certain loads and then ran worldwide for more than three months without trouble. A routine failover about fifteen hours before the outage, which moved Microsoft Teams onto the same gateway that carries Exchange Online and raised the load on it. And nearly 14% of the gateway's capacity already out of service after an unrelated problem the day before. Lamanna says that shortfall alone would have done nothing, because the service had spare capacity.

Lamanna writes that the extra load and the reduced capacity together pushed the gateway into the July defect. Requests piled up until servers stopped responding, and the systems that route users to healthy servers spread the same load across fewer machines, knocking those over too. "In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive," the statement says. "At its lowest, more than 80% of servers were unresponsive."

He adds that Teams, OneDrive, SharePoint and the Office apps could be moved off the faulty gateway and came back earlier, and that Exchange Online cannot be moved off it.

He writes that recovery was slow because servers were overwhelmed again by waiting traffic as soon as they returned, and because the company's usual tools for undoing a change could not quickly revert a defect that old.

Sources

By Olga SchmidtEditor-in-Chief, Writer

Spot an error?

Spot an error?

Report an error

Spotted a mistake on this page? Tell us what's wrong and our editors will take a look.

What kind of problem?

Only if you'd like us to be able to follow up. We won't use it for anything else.

We correct mistakes openly. Select any text to flag it. Fixes are logged under our Corrections Policy.

Report an error

Reporting on

Microsoft Says Three Faults Had to Coincide to Take Down Microsoft 365

What kind of problem?

Only if you'd like us to be able to follow up. We won't use it for anything else.

We read every report. Corrections are logged publicly.