What happened
Microsoft Azure: Front Door: incompatible metadata across two control-plane versions. Scope: Global.
CHYP.ai · ORBIT // Cloudy_Day Security Suite
OUTAGE DISSECTOR · CASE FILE · Meltdown Index · vendor post-incident report
Microsoft Azure: Front Door: incompatible metadata across two control-plane versions. Scope: Global.
Severe storm
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: Front Door: incompatible metadata across two control-plane versions. Scope: Global.
Azure Front Door, Azure CDN, Azure Portal, Microsoft Entra and 2 more.
24 catalogued services run on Microsoft Azure (inferred). Hit: Global.
Resolved after 8h 24m.
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.
A specific sequence of customer configuration changes, performed across two different control plane build versions, resulted in incompatible customer configuration metadata being generated. These customer configuration changes themselves were valid and non-malicious – however they produced metadata that, when deployed to edge site servers, exposed a latent bug in the data plane.
Official window 15:41 UTC 29 Oct–00:05 UTC 30 Oct. Microsoft also published a lessons-learned post: https://techcommunity.microsoft.com/blog/azurenetworkingblog/azure-front-door-implementing-lessons-learned-following-october-outages/4479416
Verbatim excerpt from Azure Post Incident Review — YKYN-BWZ (29–30 Oct 2025).
75% similar · same provider
Front Door: manual metadata cleanup bypassed protection
Config pushControl plane
75% similar · same provider
Front Door: network control-plane failure plus latent routing configuration
Control planeConfig push
66% similar · same provider
Exchange / Microsoft 365: servers unexpectedly unavailable, core process overwhelmed
CapacityCascade
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/azure-afd-2025-10-29/"><img src="https://www.chyp.ai/dissect/m/azure-afd-2025-10-29/card.svg" alt="Front Door: incompatible metadata across two control-plane … · ORBIT Outage Dissector" width="600"></a>