Microsoft Azure Outage History

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.

Azure SQL Managed Instance experienced intermittent start and failover issues across multiple regions, causing customers to encounter exceptions and errors during create or update operations. The incident lasted 1.1 hours, during which Microsoft identified the root cause and applied mitigation steps to affected resources.

Starting at 08:10 UTC on February 26, 2026, a subset of Azure SQL Managed Instance customers experienced failures during start, stop, or failover operations, resulting in temporary unavailability of their database instances across multiple regions. The incident lasted 1.3 hours and was classified as a minor service disruption. The issue has been resolved, restoring normal functionality to affected Azure SQL Managed Instance services.