What happened
Microsoft Azure: ARM control plane blocked by a global Cosmos DB misconfiguration. Scope: Azure US Government regions.
CHYP.ai · ORBIT // Cloudy_Day Security Suite
OUTAGE DISSECTOR · CASE FILE · Meltdown Index · vendor post-incident report
Microsoft Azure: ARM control plane blocked by a global Cosmos DB misconfiguration. Scope: Azure US Government regions.
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: ARM control plane blocked by a global Cosmos DB misconfiguration. Scope: Azure US Government regions.
Azure Resource Manager, Azure portal, Azure App Service, Azure Kubernetes Service and 3 more.
24 catalogued services run on Microsoft Azure (inferred). Hit: Azure US Government regions.
Resolved after 1h 38m.
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.
Upon investigating, we discovered that a backend Cosmos DB was misconfigured to block legitimate access from Azure Resource Manager (ARM). This prevented ARM from serving any requests, as the account is global. While Cosmos DB accounts can be replicated to multiple regions, configuration settings are global. When this account was misconfigured, the change immediately applied to all replicas impacting ARM in all regions.
Window 14:47–16:25 EDT. Impacted control-plane operations (create, update, delete) in Azure Government.
Verbatim excerpt from Azure Post Incident Review — HSKF-FB0 (27 Sep 2024).
90% similar · same provider
Front Door: manual metadata cleanup bypassed protection
Config pushControl plane
90% similar · same provider
Front Door: network control-plane failure plus latent routing configuration
Control planeConfig push
65% similar · same provider
Front Door: incompatible metadata across two control-plane versions
Control planeConfig pushCascade
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-arm-gov-2024-09-27/"><img src="https://www.chyp.ai/dissect/m/azure-arm-gov-2024-09-27/card.svg" alt="ARM control plane blocked by a global Cosmos DB misconfigur… · ORBIT Outage Dissector" width="600"></a>