Cloud · Microsoft
Azure West US power event
- Started
- Feb 7, 2026, 07:58 UTC
- Resolved
- Feb 9, 2026, 03:42 UTC
- Duration
- 43h 44m (from provider timestamps)
- Affected
- Azure Storage, Azure Virtual Machines, Azure Kubernetes Service, Azure App Service, Azure SQL Database, Azure Cosmos DB, Azure Event Hubs, Azure Service Bus, Azure Monitor / Application Insights, Azure Key Vault, Azure Databricks, Azure Database for MySQL Flexible Server, Azure Database for PostgreSQL Flexible Server, Microsoft Store, Windows Update
- Cause
- Final reviewAn onsite transformer failed and cut utility power to one West US datacenter. Generators started, but a cascading control system failure stopped the automatic transfer of load to them, so UPS batteries ran down and racks lost power. Two storage scale units then failed to boot cleanly and a surge of compute recovery work slowed restoration.
- Was it an attack?
- Not stated
- State
- resolved
Anatomy
1. Trigger
Power failure
2. Already broken
Generator or UPS failure, Failover failed
3. What made it spread
Recovery backlog
4. Blast radius
single region: West US
5. Cause category
Power or cooling
Labels follow the root-cause taxonomy. A person's change is recorded as the trigger and the missing safeguard as what was already broken; “human error” is never a cause here.
How the explanation changed
February 9, 2026 · Preliminary cause
“an unexpected interruption to utility power at one of our West US datacenters”
The Register: Azure power hiccup gives Windows admins a rare break from updates (9 Feb 2026)
Date not shown on the source · Final review
“an electrical failure in an onsite transformer resulted in the loss of utility power to the datacenter. Although generators started as designed, a cascading failure within a control system prevented the automated transfer of load from utility power to generator power.”
Azure status history PIR, tracking ID _SVS-5_G (served by the history page's results endpoint)
What the provider committed to change
- Control system and dependent components inspected, reconfigured and validated for transfer-to-generator events (completed)
- Reprioritize critical infrastructure earlier in the power restoration sequence (completed)
- Add prioritization and throttling to the recovery system for surge scenarios (estimated July 2026)
Impact, as reported
- storage scale units affected: six storage scale units, four of which recovered as expected once power was restored, according to Microsoft Azure PIR (Azure status history PIR, tracking ID _SVS-5_G (served by the history page's results endpoint)).
Every figure is attributed to whoever stated it. Crowd reports are labelled user reports and never treated as users affected.
Post-incident reviews
Other Microsoft incidents
- Microsoft 365 global outage: latent networking gateway defect cascades across the fleet (EX1550543 / MO1550821), November 12, 2026
- Azure West US loses connectivity to the WAN after an over-scoped break-fix repair, July 23, 2026
- Azure East US control plane failures, April 24, 2026
- Azure Front Door and Azure CDN global connectivity and DNS outage, October 29, 2025
Sources
- Azure status history PIR, tracking ID _SVS-5_G (served by the history page's results endpoint) (provider, read November 17, 2026)
- Azure status history page (provider, read November 17, 2026)
- The Register: Azure power hiccup gives Windows admins a rare break from updates (9 Feb 2026) (news, read November 17, 2026)
Last verified November 17, 2026. Spot an error? The methodology page says how corrections work.