SaaS · Microsoft
Microsoft 365 global outage: latent networking gateway defect cascades across the fleet (EX1550543 / MO1550821)
- Started
- Nov 12, 2026, 16:20 UTC
- Resolved
- Nov 14, 2026, 04:15 UTC
- Duration
- 35h 55m (from provider timestamps)
- Affected
- Exchange Online, Copilot, Teams, SharePoint, OneDrive, Defender, Purview, Fabric, Intune, Planner, Power Apps, To Do, Power BI, Universal Print
- Cause
- Preliminary causeA defect shipped in July in a fix for Microsoft 365 networking gateway servers caused lock contention that exhausted CPU and memory under certain load. A routine Teams failover onto the gateway shared with Exchange Online, with about 14% of gateway capacity already out of service, pushed servers into that state, and rerouting load to healthy servers spread the failure until more than 80% were unresponsive. Bulkheads between capacity units did not hold, and recovering servers were overwhelmed by waiting traffic until a fix reverting the code path was rolled out.
- Was it an attack?
- No, per the provider or investigators
- State
- resolved
Anatomy
1. Trigger
Traffic surge
2. Already broken
Latent bug, No feature flag
3. What made it spread
Health-check cascade, Retry storm, Recovery backlog
4. Blast radius
global: global
5. Cause category
Software or automation
Labels follow the root-cause taxonomy. A person's change is recorded as the trigger and the missing safeguard as what was already broken; “human error” is never a cause here.
How the explanation changed
November 13, 2026 · Preliminary cause
“The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change.”
Windows Latest, Microsoft statement in admin center (2026-11-14)
November 15, 2026 · Preliminary cause
“The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services.”
November 15, 2026 · Preliminary cause
“First, a latent defect caused Windows servers to become overwhelmed and unresponsive under certain load conditions. This was due to lock contention inside an internal Windows process which caused the machine’s resources (CPU & memory) to be exhausted.”
What the provider committed to change
- Update returning the connection handling code path to the previous known good state (completed)
- Extended the email delivery window so queued mail was not returned undeliverable (completed)
- Added capacity as a proactive measure (completed)
- Additional monitoring for traffic-redirection patterns and connection-handling health (completed)
- Guardrails for traffic distribution to avoid cascading impact (completed)
- Comprehensive repair item list in the final PIR (due 2026-11-20)
Impact, as reported
- Gateway servers unresponsive at worst point: more than 80%, according to Microsoft preliminary PIR (Microsoft preliminary Post Incident Report EX1550543/MO1550821, dated 2026-11-15 (copy hosted by Next.ink)).
- Hospital network declared Code Grey: Unity Health Toronto, according to Unity Health Toronto statement, as reported by Fortune (Fortune, 2026-11-13).
Every figure is attributed to whoever stated it. Crowd reports are labelled user reports and never treated as users affected.
Attack or not
“there is no indication this is the result of malicious or cyber activity”
Charles Lamanna, Microsoft EVP of Copilot, Agents and Platform, on X (as reported by Al Jazeera), November 12, 2026 (Al Jazeera, Microsoft hit by global outages: what happened and why (2026-11-13))
Security aftermath
- Microsoft Threat Intelligence observed a coordinated, high-volume phishing campaign on 13 Nov 2026 using fake Microsoft 365 service-health notifications as lures, targeting organisations across multiple sectors. Microsoft assessed it as likely credential phishing but said evidence did not confirm credential capture or malware delivery. (Microsoft Security blog, High volume phishing campaign uses Microsoft 365 outage lures (2026-11-16))
Post-incident reviews
- Preliminary review, November 15, 2026
Other Microsoft incidents
- Azure West US loses connectivity to the WAN after an over-scoped break-fix repair, July 23, 2026
- Azure East US control plane failures, April 24, 2026
- Azure West US power event, February 7, 2026
- Azure Front Door and Azure CDN global connectivity and DNS outage, October 29, 2025
Sources
- Microsoft preliminary Post Incident Report EX1550543/MO1550821, dated 2026-11-15 (copy hosted by Next.ink) (provider, read November 17, 2026)
- Microsoft Security blog, High volume phishing campaign uses Microsoft 365 outage lures (2026-11-16) (provider, read November 17, 2026)
- Al Jazeera, Microsoft hit by global outages: what happened and why (2026-11-13) (news, read November 17, 2026)
- BleepingComputer, Microsoft says months-old bug caused global Microsoft 365 outage (2026-11-16) (news, read November 17, 2026)
- PCWorld, Microsoft: AI, hackers not to blame for Outlook services outage (2026-11-13) (news, read November 17, 2026)
- Windows Latest, Microsoft statement in admin center (2026-11-14) (news, read November 17, 2026)
- ITPro, Lamanna explains cascading failure (2026-11-16) (news, read November 17, 2026)
- Fortune, 2026-11-13 (news, read November 17, 2026)
Last verified November 17, 2026. Spot an error? The methodology page says how corrections work.