Microsoft Azure Outage History

A power event in Microsoft Azure's West US 2 region starting at 04:27 UTC on May 29, 2026 caused customers to experience increased latency, intermittent connectivity, and timeouts when accessing hosted resources. The incident lasted 45 minutes with Azure working to recover power and restore infrastructure. Partial recovery was observed during the incident with targeted communications sent to affected customers through the Azure Service Health dashboard.

A severe thunderstorm with lightning strikes caused widespread power outages across multiple Microsoft Azure West US 2 datacenters starting at 04:27 UTC on May 29, 2026, leading to backup generator failures and impacting numerous Azure services including Virtual Machines, Azure SQL, Kubernetes Service, and Application Insights. The incident affected multiple availability zones, with customers experiencing intermittent connectivity, elevated latency, and resource unavailability, particularly those with dependencies in Availability Zones 1 and 3. Datacenter power has been fully restored and most services have recovered, with final recovery efforts focused on two remaining storage stamps completing data integrity validation activities.

Starting at 08:40 UTC on May 27, 2026, some Azure Synapse Analytics customers using private link experienced delays or failures when accessing Synapse Studio or workspaces across multiple regions. Microsoft implemented mitigation measures and reported initial signs of recovery after 41 minutes.

Azure Synapse Analytics in East US experienced connectivity issues starting at 08:40 UTC on May 27, 2026, affecting customers using private link connections who encountered delays or failures when accessing Synapse Studio or workspaces. The service detected elevated connection failures through automated monitoring and actively investigated the issue. The incident lasted approximately 1.1 hours with minor impact classification.

Starting at 13:59 UTC on May 18, 2026, Microsoft Fabric, Power BI, and Power BI Embedded services experienced delays and failures across multiple Azure regions due to an unexpected increase in request traffic that caused infrastructure to operate below optimal levels. The incident affected customers' ability to interact with these services for approximately 4.9 hours. Microsoft's engineering teams identified contributing factors and began applying mitigations, initially testing them in a single region before broader deployment.

Microsoft Fabric and Power BI services experienced degraded performance across multiple Azure regions starting at 13:59 UTC on May 18, 2026, with users encountering delays and failures when accessing the services. The issue was caused by an unexpected surge in request traffic that overwhelmed portions of the infrastructure, operating below optimal capacity. Microsoft's engineering teams were actively investigating mitigations with an expected resolution by 18:45 UTC, approximately 90 minutes after the incident began.

A platform issue in Microsoft Azure's East US region caused failures and delays when provisioning, scaling, or updating Azure resources, along with intermittent connectivity issues for existing Virtual Machines and Azure Virtual Desktop sessions. The incident affected multiple services including Virtual Machines, AKS, Application Gateway, Azure Databricks, and others across availability zones in the region. Microsoft resolved the issue by identifying and rolling back a suspected triggering deployment, with full mitigation completed after 13.5 hours.

Between 15:05 UTC and 15:35 UTC on March 20, 2026, multiple Azure services in the East US region experienced degraded performance for approximately 30 minutes. Customers in that region may have encountered reduced service quality during this timeframe. The issue was mitigated and resolved, with further updates available through the Azure Service Health portal.

Between 15:05 UTC and 15:35 UTC on March 20, 2026, multiple Azure services in the East US region experienced degraded performance for approximately 21 minutes. The issue affected customers' ability to use various Azure services normally during this timeframe. Microsoft mitigated the problem and restored normal service operations.

Starting at 23:20 UTC on March 9, 2026, Azure OpenAI Service experienced intermittent request failures and reduced availability across multiple regions for 7.6 hours, affecting a subset of customers using specific model deployments. The issue was caused by a recent change that impacted certain model workloads and was detected through automated monitoring showing elevated failure rates. Microsoft implemented mitigation actions and rollback activities across affected regions, with service health gradually improving as recovery efforts progressed.