What happened
Microsoft Azure: Exchange / Microsoft 365: servers unexpectedly unavailable, core process overwhelmed. Scope: Global.
CHYP.ai · ORBIT // Cloudy_Day Security Suite
OUTAGE DISSECTOR · CASE FILE · Meltdown Index · vendor post-incident report
Microsoft Azure: Exchange / Microsoft 365: servers unexpectedly unavailable, core process overwhelmed. Scope: Global.
Meltdown
Drag or press Play to replay what was public at each moment. Each dot links to its evidence. Lanes are kept separate on purpose.
Microsoft Azure: Exchange / Microsoft 365: servers unexpectedly unavailable, core process overwhelmed. Scope: Global.
Exchange Online, Outlook, Microsoft Teams, SharePoint Online and 9 more.
24 catalogued services run on Microsoft Azure (inferred). Hit: Global.
Mitigated after 8d 19h (vendor wording: Ongoing as of 3:19 PM PT (no official full-restore time in the sourced notes)).
Center: Microsoft Azure. Inner ring: what it runs on. Outer ring: catalogued services that run on it, coloured by their official status right now. Dependencies are inferred from public information.
Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.
Failure modes as stated in the vendor's own post-incident report (Meltdown Index).
Correlation is not causation
Five independent lanes across the window. Brighter = stronger item. Items landing in the same column are coincidence unless the provider says otherwise.
We've determined that the elevated load isn't driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable, which is shifting load onto the remaining infrastructure.
Start about 9:30 AM PT (ThousandEyes public analysis cited ~17:30 UTC); the campus StatusHub incident was created at 10:24 AM PT. Official wording is Microsoft’s, republished on the StatusHub mirror (update 4 at 11:53 AM PT; update 8 at 2:21 PM PT). A StatusHub update 9 around 3:19 PM PT had not declared a full restore. Microsoft’s public status.cloud.microsoft page, captured around 4:07 PM PT the same day, no longer showed a live incident banner. No confirmed official end time is recorded.
Verbatim excerpt from University of Illinois StatusHub incident 982055 (Microsoft service-health notes, 12 Nov 2026).
66% similar · same provider
Front Door: incompatible metadata across two control-plane versions
Control planeConfig pushCascade
50% similar
Bot Management feature file doubled and crashed traffic-routing software
Config pushCapacityCascade
45% similar · same provider
Front Door: manual metadata cleanup bypassed protection
Config pushControl plane
Nearest matches in the Control-Plane Meltdown Index (1.0.0, vendor-sourced, tracked since 2024 with earlier landmark cases). Similarity = provider + failure modes + scope.
Automated take: rules written by Cloudy_Day, applied to public data. Not a human verdict on this incident, not a root-cause finding, not affiliated with Microsoft Azure.
Everything above as one shareable, citable capsule with a content hash.
JSON capsuleMarkdownShare card (SVG)
Open Microsoft Azure in the War Room →Status page →
<a href="https://www.chyp.ai/dissect/m/ms365-2026-11-12/"><img src="https://www.chyp.ai/dissect/m/ms365-2026-11-12/card.svg" alt="Exchange / Microsoft 365: servers unexpectedly unavailable,… · ORBIT Outage Dissector" width="600"></a>