Cloud Outage Analysis

Azure Outage Cost - History, Real Losses & Your Exposure

Updated August 2026 · 8 major incidents documented

Direct Answer

Azure's most recent major outage was 2-3 February 2026, a roughly 12-hour multi-stage control-plane failure (tracking ID FNJ8-VQZ). A remediation workflow wrongly disabled anonymous read access on Microsoft-managed storage accounts that host VM extension packages, and a data-synchronization fault in its targeting logic propagated the change across multiple regions - so virtual machines, VM Scale Sets, and AKS failed to provision or scale worldwide. The rushed recovery then overwhelmed the Managed Identities token-issuance backplane, causing identity failures in East US and West US. Before that, the 29 October 2025 Azure Front Door outage was a roughly 8.5-hour global edge/CDN failure that cascaded across Microsoft 365, Outlook, Copilot, the Azure Portal, and Xbox, and took down Alaska Airlines, Costco, and Starbucks. Azure outages tend to be global and control-plane-, authentication-, or edge-related rather than single-region, which makes a multi-region or multi-cloud failover plan the main mitigation. Full chronology and SLA credit math below.

Azure Outage History

DateServicesDurationImpactEst. Cost
Feb 2026VM provisioning/scaling, VMSS, AKS, Managed Identities (token issuance); Azure DevOps, GitHub Actions, Arc, PostgreSQL~12 hours (multi-stage)Multi-region control-plane; VM lifecycle failures globally, then managed-identity token failures in East US & West USNot quantified
Oct 2025Front Door (global edge/CDN); cascaded M365, Entra ID, Azure Portal, Xbox~8.5 hoursGlobal; Microsoft 365, Outlook, Copilot, Xbox; Alaska Airlines, Costco, StarbucksNot yet quantified
Jul 2024Azure VMs (CrowdStrike-adjacent)Varies by recoveryWindows Azure VMs running CrowdStrike Falcon crashedIncluded in $5.4B CrowdStrike total
Jun 2023Outlook, OneDrive, Azure Portal (Layer-7 DDoS by Storm-1359 / Anonymous Sudan)Intermittent over ~3 daysPortal and service access disrupted (Outlook 7 Jun, OneDrive 8 Jun, Azure Portal 9 Jun); no data compromise reportedNot quantified
Jan 2023Global WAN / network (BGP router config change); Teams, Outlook, SharePoint, OneDrive, Azure connectivity~5 hoursGlobal connectivity failures across Azure and Microsoft 365 (25 Jan, 07:05-12:43 UTC)Not quantified
Apr 2021Azure DNS~1 hourDNS resolution failures (spike-mitigation code defect) cascading to many services (1 Apr, ~21:21-22:00 UTC)Not quantified
Sep 2020Azure AD (authentication)~3 hoursGlobal auth failures; Azure Portal, Teams, and M365 logins blocked (latent code defect in a service update plus rollback-tooling faults; 28 Sep, 21:25-00:23 UTC)Not quantified
Sep 2018South Central US region (lightning to cooling failure)~21+ hoursStorage servers physically damaged; Azure DevOps region-wide plus global cross-service impact (4 Sep)Not quantified

Microsoft does not disclose per-incident customer-loss figures, so historical incidents without a published third-party estimate are marked "Not quantified" rather than guessed. Incident dates, durations, and root causes are per Microsoft's Azure status history and Post-Incident Reviews (Feb 2026 tracking ID FNJ8-VQZ; Sep 2020 Azure AD; Jan 2023 WAN; Apr 2021 DNS; Sep 2018 South Central US Azure DevOps postmortem) and contemporaneous reporting by The Register, Network World, ThousandEyes, and BleepingComputer. The February 2026 event was a control-plane/service-management failure (running workloads largely stayed up while provisioning, scaling, and token issuance failed). The October 2025 Front Door outage has no firm published insured-loss estimate. The CrowdStrike July 2024 figure is Parametrix's $5.4B Fortune 500 aggregate. Updated August 2026.

Azure SLA Credits (Updated 2024)

Monthly Uptime %CreditNotes
99.99%+No credit (SLA met)Standard commitment for most services
99% - 99.99%25% of monthly feeAuto-applied for some incidents since 2024
<99%100% of monthly feeMaximum credit per service per month

Full SLA credit vs actual loss analysis - credits cover only a fraction of business loss.

Frequently Asked

What caused the February 2026 Azure outage?
The 2-3 February 2026 Azure outage (tracking ID FNJ8-VQZ) was a roughly 12-hour, multi-stage control-plane failure. A remediation workflow wrongly disabled anonymous read access on Microsoft-managed storage accounts hosting VM extension packages, and a data-sync fault in its targeting logic spread the change across multiple regions - so Virtual Machines, VM Scale Sets, and AKS failed to provision or scale worldwide (roughly 18:03 UTC 2 Feb to 00:30 UTC 3 Feb). The rushed recovery then overwhelmed the Managed Identities token-issuance backplane, causing identity failures in East US and West US (about 00:08 to 06:05 UTC). Running workloads that did not need to scale or fetch tokens were largely unaffected, so no loss figure has been published.
What caused the October 2025 Azure outage?
The 29 October 2025 Azure outage was a roughly 8.5-hour global failure of Azure Front Door, Microsoft's edge and CDN entry point. A faulty configuration change in the Front Door data plane caused nodes across the global fleet to fail to load correctly, cascading to Microsoft 365, Outlook, Copilot, the Azure Portal, and Xbox, and to customer sites including Alaska Airlines, Costco, and Starbucks. It began around 15:45 UTC and was largely resolved by 00:05 UTC on 30 October after Microsoft rolled back the change. No firm insured-loss figure has been published.
How reliable is Azure compared to AWS?
Azure and AWS have comparable uptime records for major incidents. Azure incidents often affect Microsoft 365 and Teams - extremely visible to enterprise users. The CrowdStrike July 2024 outage affected Azure customers running Falcon on Windows Azure VMs, creating a compound incident included in the $5.4B Fortune 500 loss estimate.
How do Azure SLA credits work?
Azure credits are 25% of monthly service fees when uptime falls to 99%-99.99%, and 100% below 99%. In 2024, Azure updated to automatically apply some credits for verified incidents. Credits are Azure billing credits, not cash refunds, and are capped at the monthly fee for the affected service.

Updated 2026-04-27