Overview
- The outage began on Nov. 12 and lasted about 24 hours, leaving Exchange Online and many Microsoft 365 features unusable and generating roughly 130,000 user reports at the peak of the disruption.
- A preliminary probe led by Charles Lamanna found three colliding causes: a latent July update bug, routine Teams traffic shifting to Exchange Online, and an unrelated earlier glitch that reduced server capacity.
- Engineers rolled back the July connection code, added server capacity and traffic safeguards, and Microsoft opened a post‑incident review with a final report due on November 20 and an SLA credit claim window open through December 31.
- CEO Satya Nadella publicly apologised, called the event a “perfect storm,” and warned that AI‑driven faster bug discovery raises patch velocity that can destabilise older or unpatchable infrastructure.
- The outage exposed how reliant businesses and public services are on Exchange Online and sharpened pressure on Microsoft to modernise isolation, win local support for data centre expansion, and prevent repeat cascading failures.