Know before it hits your SLAs.
All monitored Azure services are responding normally. Status is re-checked every minute from public Azure health data.
Post-mortems
What actually broke, why, and what it means for your business continuity plan - every major Azure incident, explained clearly.
A bug in an automated cryptographic key rotation process left an old signing key in a state where Azure AD could no longer validate the tokens it issued. Sign-in to Microsoft 365, the Azure portal, and any app that authenticates through Azure AD failed worldwide for several hours until Microsoft rolled the key back.
8 min read
Three overlapping bugs in the Azure multi-factor authentication service combined so that MFA requests could not complete. Because so many tenants require MFA at sign-in, users could not finish authenticating to Microsoft 365 and Azure AD worldwide. It took Microsoft the better part of a day to fully mitigate the layered failure.
8 min read
A severe thunderstorm near the South Central US datacenter caused voltage swells that damaged cooling and electrical infrastructure. Hardware overheated and shut down to protect itself, taking a large slice of the region offline. Recovery took more than a day, and dependencies on the affected region briefly rippled into some services worldwide.
9 min read
A configuration change meant to improve Azure Storage performance contained a bug and was rolled out far more broadly than intended, bypassing the normal staged deployment. Storage front ends entered a loop and stopped serving requests, and because so many Azure services depend on Storage, the failure cascaded worldwide for hours.
8 min read
An allowlist configuration error on Azure Storage scale units made storage unavailable across an availability zone in Central US. Because Virtual Machines cannot run without their disks, the failure cascaded into VMs, dependent Azure services, and Microsoft 365 for many hours - landing in the same week as the unrelated CrowdStrike incident.
9 min read
Layer-7 DDoS attacks - attributed by Microsoft to the actor it tracks as Storm-1359 - flooded the web front ends of the Azure Portal, Outlook on the web, and OneDrive across several days in early June 2023. Authentication and portal access failed intermittently, showing how an attack on web tiers reads as an identity outage to the business.
8 min read
Guides
Evergreen business-continuity playbooks written from real Azure incident patterns.
How Azure Backup and Azure Site Recovery deliver disaster recovery: backup vs DR, setting RTO and RPO, recovery plans, and non-disruptive test failover.
9 min read
Why Microsoft Entra ID is your most critical dependency and how to survive an identity outage with break-glass accounts and backup authentication.
9 min read
When to use Azure Front Door vs Traffic Manager for global routing and failover: DNS vs anycast, health probes, routing methods, and combining both.
9 min read
For IT leaders
The resources our enterprise readers use in audits, board briefings, and DR reviews.
The complete hub: BIA and RTO/RPO tiers, Azure’s resilience primitives, compliance drivers (ISO 22301, DORA, SOC 2), and a five-step implementation path with game days.
Read the pillar guide →Instant incident alerts with affected services and regions - brief your stakeholders before the ticket queue does - plus the gated BC/DR guide download for your team.
Get the briefing →Instant email alerts the moment an Azure incident is detected - with the affected services and regions, not a vague status tweet.
azure