Microsoft says dormant July bug caused last week's 365/Exchange outage
Microsoft's preliminary Post-Incident Report attributes a nearly 24-hour outage affecting Microsoft 365 and Exchange, running from November 12 to November 13, to a defect introduced in a cloud gateway update in July. The company says the bug went undetected because test hardware had fewer CPU cores than some production machines, and it only surfaced when routine network maintenance shifted traffic and strained already-reduced server capacity. Microsoft classified the incident as a technical issue unrelated to cyber attacks or AI systems.
GoKawiil's interpretation of the reporting above, not reported fact.
The explanation suggests that Microsoft's pre-release testing environment did not mirror the hardware diversity of its live production fleet, a gap that could leave similar latent defects undetected until maintenance or traffic changes expose them. For businesses and government offices reliant on Microsoft 365, the incident underscores how a months-old, unnoticed change can cascade into a near full-day disruption once ordinary operational triggers align.
- Outage ran from Nov 12, 16:20 UTC to Nov 13, 16:10 UTC, with monitoring through Nov 14.
- Root cause: a July gateway update bug that went undetected due to less powerful test hardware.
- Microsoft says the issue was purely technical, not caused by cyberattacks or AI systems.
Source: arstechnica.com, 2026-11-16
Published there as: “Microsoft details how three problems combined for a global outage”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.