Azure

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. postmortem 2026-09-30 00:00 UTC

   What happened? Between 20:30 UTC on 30 September 2026 and 02:15 UTC on 1 October 2026, customers using several Azure networking services – including Azure ExpressRoute Gateway, Azure Application Gateway, Azure Firewall, Azure Bastion, Azure Virtual WAN, and Azure VPN Gateway –...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2026-09-29 00:00 UTC

   What happened? Between 10:03 UTC and 15:58 UTC on 29 September 2026, a platform issue resulted in impact to Azure OpenAI Service, Foundry Agent Service, Foundry Models, and Azure AI services in the Sweden Central region. Impacted customers experienced intermittent request...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Knock-on incidents at other vendors that started during this one and name Azure:

• JFrog: JFrog Cloud Platform outage affecting subset of customers in Azure US West region
• Optimizely: Digital Experience Platform (DXP) West US
• CloudAMQP: Servers Unreacheable - Azure West US
• MongoDB Atlas: Cluster connectivity issues in Azure westus
• Wiz: Portal and API Service Degradation Across Multiple US Data Centers
• Sumo Logic: Problem with Microsoft Azure Metrics Collection in North America 2 (US2)

1. postmortem 2026-07-23 00:00 UTC

   What happened? Between 14:44 and 19:41 UTC on 23 July 2026, a subset of customers experienced connectivity failures, increased latency, and/or difficulty accessing Azure services hosted within the West US region. Impact was limited to network traffic entering or exiting the...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Knock-on incidents at other vendors that started during this one and name Azure:

• Couchbase Capella: Performance Degradation in Azure West US 2 region.

1. postmortem 2026-05-29 00:00 UTC

   What happened? Between 09:39 UTC and 17:05 UTC on 29 May 2026, customers using the Azure OpenAI Service may have experienced increased latency, intermittent request failures, timeouts, and/or HTTP 5XX errors when submitting inference requests. The impact was more pronounced in...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Knock-on incidents at other vendors that started during this one and name Azure:

• Confluent Cloud: Elevated error rates and latencies in Azure westus2 region
• Elastic Cloud: Upstream Azure Outage Causing Service Degradation
• Snowflake: Azure - West US 2 (Washington): INC0157956
• Palo Alto Networks: Service degradation in westus2 due to Azure cloud service issue
• Couchbase Capella: Performance Degradation in Azure West US 2 region.

1. postmortem 2026-05-29 00:00 UTC

   What happened? Between 04:24 UTC on 29 May and 02:30 UTC on 30 May 2026, customers with resources in the West US 2 region may have experienced failures when attempting to access or manage some Azure services in the region. Impact included connectivity failures, resource...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Knock-on incidents at other vendors that started during this one and name Azure:

• JFrog: JFrog platform services outage affecting a subset of Azure customers in US East
• Datadog: Delays in AWS and Azure cloud integration metrics ingestion
• Couchbase Capella: Capella Operations Impacted by Azure East US Outage
• Confluent Cloud: Some customers using Confluent Cloud Flink on Azure with PrivateLink connectivity are experiencing issues submitting new Flink statements
• SingleStore: Azure Issues in East US

1. postmortem 2026-04-24 00:00 UTC

   What happened? Between 11:30 and 23:22 UTC on 24 April 2026, customers may have experienced failures or delays when attempting to provision, scale, or update resources in East US. Beyond this impact to service management, a small subset of customers may have encountered...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Knock-on incidents at other vendors that started during this one and name Azure:

• InfluxData: Intermittent Read/Write errors in Azure prod01-us-east-1

1. postmortem 2026-03-09 00:00 UTC

   What happened? Between 23:20 UTC on 9 March and 19:32 UTC on 10 March 2026, a platform issue resulted in impact to the Azure OpenAI Service. Impacted customers experienced HTTP 400 and HTTP 429 error responses, specifically for the GPT-5.2 model. All other GPT models were...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Knock-on incidents at other vendors that started during this one and name Azure:

• JFrog: Partial outage in JFrog Cloud Platform affecting services on Azure US West
• Wiz: We are monitoring an ongoing Microsoft Azure service degradation in West US. Some operations may be delayed or intermittently impacted. (Azure Status: https://azure.status.microsoft/en-us/status)

1. postmortem 2026-02-07 00:00 UTC

   What happened? Between 07:58 UTC on 07 February 2026 and 04:24 UTC on 08 February 2026, impacted customers experienced intermittent service unavailability, timeouts and/or higher than normal latency for services in the West US region. The event began following a power...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. postmortem 2026-02-02 00:00 UTC

   What happened? Between 18:03 UTC on 02 February 2026 and approximately 00:30 UTC on 03 February 2026, a platform issue caused some customers to experience degraded performance and control plane failures, for multiple Azure services across multiple regions. Impacted services...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2025-12-22 00:00 UTC

   What happened? Between 08:05 UTC and 18:30 UTC on 22 December 2025, the Microsoft Entra Privileged Identity Management (PIM) service experienced issues that impacted role activations for a subset of customers. Some requests returned server errors (5xx) and, for a portion of...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2025-12-08 00:00 UTC

   What happened? Between 11:04 and 14:13 EST on 08 December 2025, customers using any of the Azure Government regions may have experienced failures when attempting to perform service management operations through Azure Resource Manager (ARM). This included operations attempted...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2025-12-08 00:00 UTC

   What happened? Between 16:50 CST on 08 December 2025 and 02:00 CST on 09 December 2025 (China Standard Time) customers using any of the Azure in China regions may have experienced failures when attempting to perform service management operations through Azure Resource Manager...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Knock-on incidents at other vendors that started during this one and name Azure:

• CloudAMQP: Azure westeurope Availability Zone: 2

1. postmortem 2025-11-05 00:00 UTC

   What happened? Between approximately 16:53 UTC on 5 November 2025 and 02:25 UTC on 6 November 2025, a subset of customers in the West Europe region experienced service disruptions or degraded performance across multiple services, including Virtual Machines (VM), Azure Database...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Knock-on incidents at other vendors that started during this one and name Azure:

• Black Forest Labs: Global Outage
• Speechmatics: Outage affecting Portal, Batch SaaS API and Management Platform API
• GoTo: LogMeIn Resolve, GoToMyPC and Pro/Central - Issues with the application
• Harvey: Partial Service Disruption: Investigating Issues with logins (passwordless code)
• DigiCert: DigiCert Alert DC 1 Japan is not accessable
• Smartsheet: Investigating errors using Login with Microsoft
• Harvey: Microsoft Add-Ins ( intermittent issues )-Azure outage
• GeForce NOW: Xbox Game Sync Issues

1. postmortem 2025-10-29 00:00 UTC

   What happened? Between 15:41 UTC on 29 October and 00:05 UTC on 30 October 2025, customers and Microsoft services leveraging Azure Front Door (AFD) and Azure Content Delivery Network (CDN) experienced connection timeout errors and Domain Name System (DNS) resolution issues. From...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2025-10-09 00:00 UTC

   What happened? Between 19:43 UTC and 23:59 UTC on 09 October 2025, customers may have experienced availability issues and failures when loading content for the Azure Portal as well as other management portals across Microsoft. Over the course of the incident, approximately 45%...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2025-10-09 00:00 UTC

   What happened? Between 07:50 UTC and 16:00 UTC on 09 October 2025, Microsoft services and Azure customers leveraging Azure Front Door (AFD) and Azure Content Delivery Network (CDN) may have experienced increased latency and/or timeouts – primarily across Africa and Europe, as...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Knock-on incidents at other vendors that started during this one and name Azure:

• Hasura: Service Impact in Azure Switzerland North
• CloudAMQP: Issues with Azure region Switzerland North
• YugabyteDB: Partial Service Outage for YugabyteDB Aeon on Microsoft Azure in Switzerland North

1. postmortem 2025-09-26 00:00 UTC

   What happened? Between 23:54 UTC on 26 September 2025 and 21:59 UTC on 27 September 2025, a platform issue resulted in an impact to customers in Switzerland North who may have experienced service availability issues for resources hosted in the region. Many customers experienced...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. postmortem 2025-09-10 00:00 UTC

   What happened? Between 09:03 UTC and 18:50 UTC on 10 September 2025, an issue with the Allocator service in the Azure Compute control plane, led to degraded service management operations for resources in two Availability Zones (physical AZ02 and AZ03) in the East US 2 region....

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. postmortem 2025-03-18 00:00 UTC

   What happened? Between 13:37 and 16:52 UTC on 18 March, and again between 23:20 UTC on 18 March and 00:30 UTC on 19 March, 2025, a combination of a third-party fiber cut, and an internal tooling failure resulted in an impact to a subset of Azure customers with services in our...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2025-03-03 00:00 UTC

   What happened? Between 16:22 and 18:37 UTC on 3 March 2025, a subset of customers experienced issues when connecting to Microsoft services through our Toronto edge point-of-presence (PoP) location. This impacted customers connecting to Microsoft 365 and/or Azure services -...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2025-02-25 00:00 UTC

   What happened? Between 16:42 UTC on 25 February 2025 and 01:15 UTC on 26 February 2025, a platform issue affected Microsoft Entra ID, which prevented customers from authenticating via Microsoft Entra ID using the following features: Seamless Single Sign-On (Seamless SSO)...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2025-01-08 00:00 UTC

   What happened? Between 22:31 UTC on 8 January and 00:44 UTC on 11 January 2025, a networking configuration change in a single availability zone (physical zone AZ01) in East US 2 resulted in customers experiencing connectivity issues, prolonged timeouts, connection drops, and...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2024-12-26 00:00 UTC

   What happened? Between 18:40 UTC on 26 December and 19:30 UTC on 27 December 2024, multiple Azure services were impacted by a power event that occurred in one datacenter, within one Availability Zone (physical zone AZ03), in the South Central US region. Within the impacted...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2024-11-13 00:00 UTC

   What happened? Between 00:50 UTC and 12:30 UTC on 13 November 2024, a subset of Azure Blob Storage and Azure Data Lake Storage accounts experienced connectivity errors. The issue manifested as loss of access to Blob and Data Lake storage endpoints of the affected storage...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2024-09-27 00:00 UTC

   What happened? Between 14:47 and 16:25 EDT on 27 September 2024, a platform issue impacted the Azure Resource Manager (ARM) service in our Azure US Government regions. Impacted customers may have experienced issues attempting control plane operations including create, update and...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. postmortem 2024-09-16 00:00 UTC

   What happened? Between 18:46 UTC and 20:36 UTC on 16 September 2024, a platform issue resulted in an impact to a subset of customers using Azure Virtual Desktop in several US regions – specifically, those who have their Azure Virtual Desktop configuration and metadata stored in...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2024-09-05 00:00 UTC

   What happened? Between 08:00 and 21:30 CST on 5 September 2024, customers in the Azure China regions were seeing delays in long running control plane operations including create, update and delete operations on resources. Although these delays were affecting all regions, the...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2024-08-05 00:00 UTC

   What happened? Between 18:22 and 19:49 UTC on 5 August 2024, some customers experienced intermittent connection errors, timeouts, or increased latency while connecting to Microsoft services that leverage Azure Front Door (AFD), because of an issue that impacted multiple...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2024-07-30 00:00 UTC

   What happened? Between 11:45 and 13:58 UTC on 30 July 2024, a subset of customers experienced intermittent connection errors, timeouts, or latency spikes while connecting to Microsoft services that leverage Azure Front Door (AFD) and Azure Content Delivery Network (CDN). From...

Excerpts are shortened. Read the full incident on Azure's status page.

1. postmortem 2024-07-19 00:00 UTC

   Virtual Machines customers may have experienced unresponsiveness and startup failures on Windows machines using the CrowdStrike Falcon agent, affecting both on-premises and various cloud platforms. This issue was caused by a CrowdStrike antivirus software update, which resulted...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Knock-on incidents at other vendors that started during this one and name Azure:

• CockroachDB Cloud: CockroachDB Unavailable in Azure Central US

1. postmortem 2024-07-18 00:00 UTC

   What happened? Between 21:40 UTC on 18 July and 22:00 UTC on 19 July 2024, customers may have experienced issues with multiple Azure services in the Central US region, due to an Azure Storage availability event that was resolved by 02:55 UTC on 19 July 2024. This issue affected...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: OpenAI.

1. postmortem 2024-07-13 00:00 UTC

   What happened? Between 00:00 UTC and 23:35 UTC on 13 July 2024, an issue during a cleanup operation caused a subset of critical resources to be deleted, which impacted the Azure OpenAI (AOAI) service across multiple regions. A subset of customers experienced errors when calling...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2024-07-12 00:00 UTC

   What happened? A platform issue caused some of our 'Managed Identities for Azure resources' (formerly Managed Service Identity or MSI) customers to experience failures when requesting managed identity tokens or performing management operations for managed identities in the...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2024-04-22 00:00 UTC

   What happened? Between 03:45 CST and 06:00 CST on 23 Apr 2024, a configuration change performed through a domain registrar resulted in a service disruption to 2 system domains (chinacloudapp.cn and chinacloudsites.cn) that are critical in our cloud operations in China. This...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2024-04-19 00:00 UTC

   What happened? Between 04:26 UTC and 07:30 UTC on 19 April 2024, a platform issue in the West US region resulted in impact for the following services: Azure Database for MariaDB : Connectivity issues, all connections may have failed for a subset of customers. Retries would have...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2024-03-14 00:00 UTC

   What happened? Between 10:33 UTC on 14 March 2024 and 11:00 UTC on 15 March 2024, customers using Azure services in the South Africa North and/or South Africa West regions may have experienced network connectivity failures, including extended periods of increased latency or...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2024-01-21 00:00 UTC

   What happened? Between 01:30 and 08:58 UTC on 21 January 2024, customers attempting to leverage Azure Resource Manager (ARM) may have experienced issues when performing resource management operations. This impacted ARM calls that were made via Azure CLI, Azure PowerShell and the...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2023-09-16 00:00 UTC

   What happened? Between 07:24 and 19:00 UTC on 16 September 2023, a subset of customers using Virtual Machines (VMs) in the East US region experienced connectivity issues. This incident was triggered when a number of scale units within one of the datacenters in one of the...

Excerpts are shortened. Read the full incident on Azure's status page.

1. postmortem 2023-08-30 00:00 UTC

   What happened? Starting at approximately 10:30 UTC on 30 August 2023, customers may have experienced issues accessing or using Azure, Microsoft 365 and Power Platform services. This incident was triggered by a utility power sag at 08:41 UTC on 30 August 2023, which impacted one...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2023-07-06 00:00 UTC

   What happened? Between 23:15 UTC on 6 July 2023 and 09:00 UTC on 7 July 2023, a subset of data for Azure Monitor Log Analytics and Microsoft Sentinel failed to ingest. Additionally, platform logs gathered via Diagnostic Settings failed to route some data to customer destinations...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2023-07-05 00:00 UTC

   What happened? Between approximately 07:22 UTC and 16:00 UTC on 5 July 2023, Azure customers using the West Europe region may have experienced packet drops, timeouts, and/or increased latency. This impact resulted from a fiber cut caused by severe weather conditions in the...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2023-06-16 00:00 UTC

   What happened? Between 02:34 UTC and 07:25 UTC on 16 June 2023, a network issue caused excessive packet loss that affected traffic entering or leaving the West Europe region and, to a lesser extent, traffic between Availability Zones inside the West Europe region. Resources...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: An external attack. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2023-06-09 00:00 UTC

   What happened? Between 15:10 and 17:00 UTC on 9 June 2023, customers may have experienced error notifications when trying to access the Azure Portal (portal.azure.com), and actions to load new HTTP content in the Azure Portal may have resulted in error notifications. Customers...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2023-03-23 00:00 UTC

   What happened? Between 02:20 UTC and 07:30 UTC on 23 March 2023 you may have experienced issues using Azure Resource Manager (ARM) when performing resource management operations in the West Europe region. This impacted users of Azure CLI, Azure PowerShell, the Azure portal, as...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2023-03-06 00:00 UTC

   What happened? Between 03:50 UTC and 17:55 UTC on 6 March 2023, a subset of customers using Azure Storage may have experienced greater than expected throttling when performing requests against Storage resources located in the West Europe region. Azure services dependent on Azure...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2023-02-07 00:00 UTC

   What happened? Between 20:19 UTC on 7 February 2023 and 04:30 UTC on 9 February 2023, a subset of customers with workloads hosted in the Southeast Asia and East Asia regions experienced difficulties accessing and managing resources deployed in these regions. One Availability...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. postmortem 2023-01-31 00:00 UTC

   What happened? Between 05:55 UTC on 31 January 2023 and 00:58 UTC on 1 February 2023, a subset of customers using Virtual Machines (VMs) in the East US 2 region may have received error notifications when performing service management operations – such as create, delete, update,...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2023-01-25 00:00 UTC

   What happened? Between 07:08 UTC and 12:43 UTC on 25 January 2023, customers experienced issues with network connectivity, manifesting as long network latency and/or timeouts when attempting to connect to resources hosted in Azure regions, as well as other Microsoft services...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2023-01-23 00:00 UTC

   What happened? Between 15:39 UTC and 19:38 UTC on 23 January 2023, a subset of customers in the South Central US region may have experienced increased latency and/or intermittent connectivity issues while accessing services hosted in the region. Downstream services that were...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2023-01-18 00:00 UTC

   What happened? Between 09:44 and 13:10 UTC on 18 January 2023, a subset of customers using Storage services in West Europe may have experienced higher than expected latency, timeouts or HTTP 500 errors when accessing data stored on Storage accounts hosted in this region. Other...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2022-11-02 00:00 UTC

   What happened? Between 00:42 UTC on 2 November and 05:55 UTC on 3 November 2022, customers experienced failures when attempting to provision new resources in a subset of Azure services including Application Gateway, Bastion, Container Apps, Database Services (MySQL - Flexible...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2022-10-26 00:00 UTC

   What happened? Between 00:25 UTC and 06:00 UTC on 26 October 2022, a subset of customers using Azure Cosmos DB in the East US region may have experienced issues connecting to the service. Connections to Azure Cosmos DB accounts in this region may have resulted in an error or...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: An external attack. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2022-09-07 00:00 UTC

   What happened? Between 16:10 and 19:55 UTC on 07 Sep 2022, a subset of customers using Azure Front Door (AFD) experienced intermittent availability drops, connection timeouts and increased latency. At its peak, this impacted approximately 25% of the traffic, and on average, 10%...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2022-09-07 00:00 UTC

   What happened? Between 09:50 UTC and 17:21 UTC on 07 Sep 2022, a subset of customers using Azure Cosmos DB in North Europe may have experienced issues accessing services. Connections to Cosmos DB accounts in this region may have resulted in an error or timeout. Downstream Azure...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2022-08-30 00:00 UTC

   What happened? Between 06:00 UTC on 30 Aug 2022 and 16:00 UTC on 31 Aug 2022, customers running Ubuntu 18.04 (bionic) Virtual Machines (VMs) who had Ubuntu Unattended-Upgrades enabled received a systemd version that resulted in Domain Name System (DNS) resolution errors. This...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2022-08-27 00:00 UTC

   What happened? Between 02:47 UTC on 27 Aug 2022 and 02:00 UTC on 28 Aug 2022, a subset of customers experienced failures when trying to access resources hosted in the West US 2 region. Although initially triggered by a utility power outage that affected all of our datacenters in...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. postmortem 2022-08-18 00:00 UTC

   What happened? Between 16:30 UTC on 18 Aug 2022 and 02:22 UTC on 19 Aug 2022, a platform issue caused Azure offerings such as Bastion, ExpressRoute, Azure Container Apps, Azure ML, Azure Managed HSM, Azure Confidential VMs, Azure Database Services (MySQL - Flexible Server,...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2022-08-12 00:00 UTC

   What happened? Between 18:13 UTC on 12 Aug 2022 and 03:30 UTC on 13 Aug 2022, customers using Azure Communication Services (ACS) may have experienced authentication failures, or failures using our APIs. As a result, multiple scenarios may have been impacted including SMS, Chat,...

Excerpts are shortened. Read the full incident on Azure's status page.

1. postmortem 2022-07-29 00:00 UTC

   What happened? Between 08:00 UTC and until 13:20 UTC on 29 July 2022, customers may have experienced connectivity issues such as network drops, latency, and/or degradation when attempting to access or manage Azure resources in multiple regions. The most significant impact would...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2022-07-21 00:00 UTC

   What happened? Between 03:47 UTC and 13:30 UTC on 21 Jul 2022, customers using SQL Database and SQL Data Warehouse in West Europe may have experienced issues accessing services. During this time, new connections to databases in this region may have resulted in errors or...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2022-06-29 00:00 UTC

   What happened? Across 28 and 29 June, 2022, two independent Azure networking service incidents occurred simultaneously. While very few customer subscriptions were impacted by both, the overlapping nature of the incident timelines meant that we previously delivered a Preliminary...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2022-06-28 00:00 UTC

   What happened? Across 28 and 29 June, 2022, two independent Azure networking service incidents occurred simultaneously. While very few customer subscriptions were impacted by both, the overlapping nature of the incident timelines meant that we previously delivered a Preliminary...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2022-06-07 00:00 UTC

   What happened? Between 02:41 and 14:30 UTC on 07 Jun 2022, a subset of customers experienced difficulties connecting to resources hosted in one particular Availability Zone (AZ) of the East US 2 region. This issue impacted a subset of storage and compute resources within one of...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. postmortem 2022-05-31 00:00 UTC

   Summary of impact: Between 21:35 UTC on 31 May and 09:54 UTC on 01 Jun 2022, you were identified as a customer who may have experienced significant delays in the availability of logging data for resources such as sign in and audit logs, for Azure Active Directory and related...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. postmortem 2022-04-08 00:00 UTC

   Summary of Impact: Between 12:25 UTC on 08 Apr 2022 and 14:40 UTC on 09 Apr 2022, customers running services in the East US 2 region may have experienced service management errors, delays, and/or timeouts. Customers may have experienced issues that caused GET and PUT errors...

Excerpts are shortened. Read the full incident on Azure's status page.

1. postmortem 2022-03-16 00:00 UTC

   Summary of Impact: Between 09:13 and 10:22 UTC on March 16, 2022, end-users of customers using Azure Active Directory B2C may have experienced errors and timeouts when attempting to sign in or sign up. Retry attempts were likely to succeed during this incident Root Cause: The...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2022-03-01 00:00 UTC

   Summary of Impact : Between 11:49 EST on 01 March 2022 and 03:08 EST on 03 Mar 2022, a subset of customers experienced errors when using Azure Resource Manager to perform service management operations in the Azure Government cloud. Root Cause : A synchronization issue occurred...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2022-02-16 00:00 UTC

   Summary of Impact : Between 07:31 UTC and 15:31 UTC on 16 Feb 2022, a subset of customers using SQL Database instances in West Europe may have experienced database connectivity errors in this region including when attempting to create new connections. Retries may have been...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2022-02-12 00:00 UTC

   Summary of Impact: Between 11:45 UTC on 12 Feb 2022 and 11:43 UTC on 15 Feb 2022, a limited subset of customers using SQL Databases or Cosmos DB experienced database unavailability and may have seen errors when connecting to their database instances. This issue affected a...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. postmortem 2022-02-12 00:00 UTC

   Impact Statement : Between 04:38 UTC and 6:30 UTC on 12 Feb 2022, you were identified as a customer using Virtual Machines, Azure SQL and Storage in West US who may have experienced connection failures when trying to access some resources hosted in the region. Additional...

Excerpts are shortened. Read the full incident on Azure's status page.

1. postmortem 2022-02-02 00:00 UTC

   Summary of Impact : Between 19:50 UTC and 22:06 UTC on Feb 2, 2022, customers using Azure Active Directory (Azure AD) may have experienced failures when performing any service management operations. During this incident, the Azure AD REST API service experienced some...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. postmortem 2022-01-13 00:00 UTC

   Summary of Impact: Between 10:10 UTC on 13 Jan 2022 and 20:00 UTC on 14 Jan 2022, a subset of customers may have experienced issues, timeouts, or failures for some service management operations for services leveraging Azure Resource Manager (ARM). This could have also included...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2022-01-13 00:00 UTC

   Summary of Impact: Between 09:00 UTC on 13 Jan 2022 and 20:00 UTC on 14 Jan 2022, a subset of customers using Azure Resource Manager (ARM) to deploy, modify, or remove Azure resources experienced delays, timeouts, and failures which were visible for long running operations...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2022-01-04 00:00 UTC

   Summary of Impact: Between 12:30 UTC on 04 Jan 2022 and 7:41 UTC on 5 Jan 2022, customers with Azure Cosmos DB accounts in East US may have experienced connectivity and service availability errors while accessing their Cosmos DB databases. One Cosmos DB cluster in the East US...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. postmortem 2021-12-16 00:00 UTC

   Summary of Impact: Between 14:00 UTC and 17:30 UTC on 16 December 2021, a subset of users in North America may have experienced performance issues and timeout errors with Microsoft Graph APIs. Preliminary Root Cause: We determined that the scaling out process was affected by an...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2021-12-16 00:00 UTC

   Summary of impact: Between 01:00 UTC and 02:25 UTC on 16 December 2021, Azure Active Directory (Azure AD) users may have experienced impact when accessing Microsoft 365, Dynamics 365 and Azure services. Customers using desktop and mobile applications, such as Microsoft Teams,...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. postmortem 2021-12-13 00:00 UTC

   Summary of Impact: Between approximately 06:30 UTC and 12:30 UTC on 13 December 2021, you were identified as a customer that may have experienced intermittent errors accessing Azure Data Factory resources (ADF) in West Europe. Root Cause: We determined a backend service,...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2021-12-09 00:00 UTC

   Summary of Impact: Between approximately 21:00 UTC on 09 Dec 2021 and 00:23 UTC on 10 Dec 2021, a subset of customers using App Service and/or Azure Functions may have encountered issues with deployments using web deploy, managing WebJobs, connecting to Web SSH console,...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. postmortem 2021-11-16 00:00 UTC

   Summary of Impact: (Updated on 28 Sep 2022 to reflect the correct incident duration) Between 19:30 UTC and 22:10 UTC on 16 Nov 2021 and between 23:00 UTC on 16 Nov 2021 and 02:50 UTC on 17 Nov 2021, a subset of customers using Azure Active Directory B2C in the Australia region...

Excerpts are shortened. Read the full incident on Azure's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. postmortem 2021-11-12 00:00 UTC

   Summary of Impact: Between 02:00 UTC on 12 Nov 2021 and 17:00 UTC on 15 Nov 2021, a subset of customers primarily located in the North America and APAC geographies may have encountered intermittent 400-level errors when attempting to access Microsoft Graph APIs. Preliminary Root...

Excerpts are shortened. Read the full incident on Azure's status page.

1. postmortem 2021-11-09 00:00 UTC

   Summary of Impact : Between 14:03 UTC and 19:28 UTC on Nov 9 2021, customers using Azure Active Directory’s Access Panel whose traffic was routed through West Central US and Central US may have experienced issues when attempting to access or use Access Panel functionality. Users...

Excerpts are shortened. Read the full incident on Azure's status page.

1. postmortem 2021-10-27 00:00 UTC

   Starting at 10:03 UTC, a subset of customers using SMS for Multi-Factor Authentication in United States are experiencing difficulties signing into Azure resources, such as Azure Active Directory, when Multi-Factor Authentication is required by policy. Workaround: Customers are...

Excerpts are shortened. Read the full incident on Azure's status page.