Microsoft Azure

Recent incidents

1. Active -Azure Portal access issues affecting Australia Regions

   Major · 14 Aug 2026, 06:28 · resolved 10 days ago

   • resolved14 Aug, 07:20

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • investigating14 Aug, 06:30

     We are aware of an issue affecting access to the Azure portal in the Australia regions. Our engineers are actively investigating the cause and impact. Further updates will be provided as more information becomes available.

2. Issues connecting to resources in West US

   Major · 23 Jul 2026, 17:29 · resolved about 1 month ago

   • resolved23 Jul, 21:18

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • investigating23 Jul, 20:57

     Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: Application Gateway, Application Insights, Azure AD B2C, Azure AI Speech, Azure API Management, Azure Bastion, Azure Bot Service, Azure Data Explorer, Azure Firewall, Azure Kubernetes Service (AKS), Azure Monitor, Azure Virtual Desktop, Azure VMware Solution, Log Analytics, Microsoft Graph, Microsoft Sentinel, Partner Center, Power BI Embedded, Virtual WAN Current Status: We identified a recent change that was strongly correlated with the onset of impact. We have completed the rollback of this change and telemetry across services are continuing to show signs of recovery. Customer should be observing recovery at this time. We are closely monitoring service health and downstream recovery and will provide additional updates as we validate restoration.

   • investigating23 Jul, 20:52

     Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: Application Gateway, Application Insights, Azure AD B2C, Azure AI Search, Azure AI Speech, Azure API Management, Azure Bastion, Azure Bot Service, Azure Data Explorer, Azure Firewall, Azure Kubernetes Service (AKS), Azure Monitor, Azure Virtual Desktop, Azure VMware Solution, Log Analytics, Microsoft Graph, Microsoft Sentinel, Partner Center, Power BI Embedded, Virtual WAN Current Status: We identified a recent change that was strongly correlated with the onset of impact. We have completed the rollback of this change and telemetry across services are continuing to show signs of recovery. Customer should be observing recovery at this time. We are closely monitoring service health and downstream recovery and will provide additional updates as we validate restoration.

   • investigating23 Jul, 20:18

     Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: Application Gateway, Application Insights, Azure AD B2C, Azure AI Search, Azure AI Speech, Azure API Management, Azure Bastion, Azure Bot Service, Azure Data Explorer, Azure Database for PostgreSQL, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure Monitoring Essentials, Azure Virtual Desktop, Azure VMware Solution, Log Analytics, Microsoft Graph, Microsoft Sentinel, Partner Center, Power BI Embedded, Virtual WAN Current Status: We identified a recent change that was strongly correlated with the onset of impact. We have completed the rollback of this change and telemetry across services are continuing to show signs of recovery. Customer should be observing recovery at this time. We are closely monitoring service health and downstream recovery and will provide additional updates as we validate restoration.

   • investigating23 Jul, 20:06

     Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: Application Gateway, Application Insights, Azure AD B2C, Azure AI Search, Azure AI Speech, Azure API Management, Azure Bastion, Azure Bot Service, Azure Data Explorer, Azure Database for PostgreSQL, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure Monitoring Essentials, Azure Virtual Desktop, Azure VMware Solution, ExpressRoute Circuits, ExpressRoute Gateways, Log Analytics, Microsoft Sentinel, Partner Center, Power BI Embedded, Virtual WAN, VPN Gateway Current Status: We identified a recent change that was strongly correlated with the onset of impact. We have completed the rollback of this change and telemetry across services are continuing to show signs of recovery. We are closely monitoring service health and downstream recovery and will provide additional updates as we validate restoration

   • investigating23 Jul, 19:48

     Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: Application Gateway, Application Insights, Azure AD B2C, Azure AI Search, Azure AI Speech, Azure API Management, Azure Bastion, Azure Bot Service, Azure Data Explorer, Azure Database for PostgreSQL, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure Monitoring Essentials, Azure Virtual Desktop, Azure VMware Solution, ExpressRoute Circuits, ExpressRoute Gateways, Log Analytics, Microsoft Sentinel, Partner Center, Power BI Embedded, Virtual WAN, VPN Gateway Current Status: We identified a recent change that was strongly correlated with the onset of impact. We have completed the rollback of this change and telemetry across services are continuing to show signs of recovery. Customer should be observing recovery at this time. We are closely monitoring service health and downstream recovery and will provide additional updates as we validate restoration

   • investigating23 Jul, 19:34

     Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: Application Gateway, Azure AD B2C, Azure AI Search, Azure AI Speech, Azure API Management, Azure Bastion, Azure Bot Service, Azure Data Explorer, Azure Database for PostgreSQL, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure Virtual Desktop, Azure VMware Solution, ExpressRoute Circuits, ExpressRoute Gateways, Partner Center, Power BI Embedded, Virtual WAN, VPN Gateway Current Status: We identified a recent change that was strongly correlated with the onset of impact and have initiated rollback actions. The rollback is currently in progress and making steady progress toward completion. Telemetry across services is beginning to show signs of recovery. We are closely monitoring service health and traffic recovery as these actions are completed and will provide additional updates as we confirm measurable improvement.

   • investigating23 Jul, 19:14

     Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: App Service, Application Gateway, Azure AD B2C, Azure AI Search, Azure API Management, Azure Bastion, Azure Bot Service, Azure Database for PostgreSQL - Flexible Server, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure Virtual Desktop, Azure VMware Solution, ExpressRoute Circuits, ExpressRoute Gateways, Partner Center, Power BI Embedded, Virtual WAN, VPN Gateway Current Status: We may have identified the likely cause of the issue and are actively deploying mitigation actions. Based on our current progress, we expect to have additional information on the effectiveness of these actions within approximately 30 minutes. We are closely monitoring service recovery as this action is rolling out.

   • investigating23 Jul, 19:06

     Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: App Service, Application Gateway, Azure AD B2C, Azure AI Search, Azure API Management, Azure Bastion, Azure Bot Service, Azure Database for PostgreSQL - Flexible Server, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure Virtual Desktop, Azure VMware Solution, ExpressRoute Circuits, ExpressRoute Gateways, Partner Center, Power BI Embedded, Virtual WAN, VPN Gateway Current Status: We may have identified the likely cause of the issue and are actively deploying mitigation actions. Based on our current progress, we expect to have additional information on the effectiveness of these actions within approximately 30 minutes. We are closely monitoring service recovery as this action is rolling out.

   • investigating23 Jul, 18:49

     Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: API Management, Application Gateway, Azure AD B2C, Azure AI Search, Azure Bastion, Azure Bot Service, Azure Database for PostgreSQL, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure VMware Solutions, ExpressRoute Circuits, ExpressRoute Gateways, Network Infrastructure, Power BI Embedded, Virtual WAN, VPN Gateway We are actively investigating networking and traffic-routing anomalies associated with the onset of impact. We have successfully redirected portions of traffic away from potentially affected network paths and tested mitigation actions. At this time, those actions have not produced a broad improvement in impacted service telemetry. Engineering teams continue investigating routing and network-path anomalies that align with the start of the incident and are evaluating additional mitigation options. While we do not have an estimated time for mitigation at this stage, we will provide updates as they become available. Customers may wish to review their business continuity and disaster recovery plans and take actions appropriate for their environment.

   • investigating23 Jul, 18:46

     Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud services (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: API Management, Application Gateway, Azure AD B2C, Azure AI Search, Azure Bastion, Azure Bot Service, Azure Database for PostgreSQL, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure VMware Solutions, ExpressRoute Circuits, ExpressRoute Gateways, Network Infrastructure, Power BI Embedded, Virtual WAN, VPN Gateway We are actively investigating networking and traffic-routing anomalies associated with the onset of impact. We have successfully redirected portions of traffic away from potentially affected network paths and tested mitigation actions. At this time, those actions have not produced a broad improvement in impacted service telemetry. Engineering teams continue investigating routing and network-path anomalies that align with the start of the incident and are evaluating additional mitigation options. While we do not have an estimated time for mitigation at this stage, we will provide updates as they become available. Customers may wish to review their business continuity and disaster recovery plans and take actions appropriate for their environment.

   • investigating23 Jul, 18:37

     Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: API Management, Application Gateway, Azure AD B2C, Azure AI Search, Azure Bastion, Azure Bot Service, Azure Database for PostgreSQL, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure VMware Solutions, ExpressRoute Circuits, ExpressRoute Gateways, Network Infrastructure, Power BI Embedded, Virtual WAN, VPN Gateway We are actively investigating networking and traffic-routing anomalies associated with the onset of impact. We have successfully redirected portions of traffic away from potentially affected network paths and tested mitigation actions. At this time, those actions have not produced a broad improvement in impacted service telemetry. Engineering teams continue investigating routing and network-path anomalies that align with the start of the incident and are evaluating additional mitigation options. While we do not have an estimated time for mitigation at this stage, we will provide updates as they become available. Customers may wish to review their business continuity and disaster recovery plans and take actions appropriate for their environment. If you are unable to access the Azure portal or create a support request during this event, contact Microsoft Customer Service using the phone number for your country or region listed here: https://support.microsoft.com/en-us/contactus

   • investigating23 Jul, 18:34

     Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: API Management, Application Gateway, Azure AD B2C, Azure AI Search, Azure Bastion, Azure Bot Service, Azure Database for PostgreSQL, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure VMware Solutions, ExpressRoute Circuits, ExpressRoute Gateways, Network Infrastructure, Power BI Embedded, Virtual WAN, VPN Gateway We are actively investigating networking and traffic-routing anomalies associated with the onset of impact. We have successfully redirected portions of traffic away from potentially affected network paths and tested mitigation actions. At this time, those actions have not produced a broad improvement in impacted service telemetry. Engineering teams continue investigating routing and network-path anomalies that align with the start of the incident and are evaluating additional mitigation options. While we do not have an estimated time for mitigation at this stage, we will provide updates as they become available. Customers may wish to review their business continuity and disaster recovery plans and take actions appropriate for their environment. If you are unable to access the Azure portal or create a support request during this event, contact Microsoft Customer Service using the phone number for your country or region listed here: https://support.microsoft.com/en-us/contactus

   • investigating23 Jul, 18:10

     Starting at 14:44 UTC on 23 July, 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure services in West US region. Customers with traffic traversing the West US region may also experience downstream impact. Impacted services include, but are not limited to: API Management, Application Gateway, Azure Database for PostgreSQL, Azure Kubernetes Service (AKS), ExpressRoute Circuits, ExpressRoute Gateways, Network Infrastructure, Power BI Embedded, Virtual WAN, VPN Gateway We have identified a potential trigger and are isolating certain impacted devices and redirecting portions of traffic to healthier devices as part of a mitigation plan. We are actively monitoring traffic patterns and service recovery. We will continue to evaluate the effectiveness of mitigation, assess customer impact, and investigate contributing factors. We will provide additional information as soon as it becomes available.

   • investigating23 Jul, 18:02

     Starting at 14:44 UTC on 23 July, 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure services in West US region. Customers with traffic traversing the West US region may also experience downstream impact. Impacted services include, but are not limited to: API Management, Application Gateway, Azure Database for PostgreSQL, Azure Kubernetes Service (AKS), ExpressRoute Circuits, ExpressRoute Gateways, Network Infrastructure, Power BI Embedded, Virtual WAN, VPN Gateway We have identified a potential trigger and are isolating certain impacted devices and redirecting portions of traffic to healthier devices as part of a mitigation plan. We are actively monitoring traffic patterns and service recovery. We will continue to evaluate the effectiveness of mitigation, assess customer impact, and investigate contributing factors. We will provide additional information as soon as it becomes available.

   • investigating23 Jul, 17:50

     Starting at 14:44 UTC on 23 July, 2026, we began investigating a networking issue affecting connectivity to Azure services in the West US region. Impacted customers may be experiencing intermittent connectivity failures, increased latency, or difficulty accessing Azure services. Customers with traffic traversing the West US region may also experience downstream impact. Our investigation is currently focused on network infrastructure within the affected region. We have implemented mitigation actions on affected network components by removing the problematic devices from rotation, redirecting portions of traffic, and are actively monitoring traffic patterns and service recovery. Initial findings indicate the issue may be related to network path disruption within the affected infrastructure; however, analysis remains ongoing. We continue to evaluate the effectiveness of mitigations, assess customer impact, and investigate contributing factors. We will provide additional information as it becomes available.

   • investigating23 Jul, 17:31

     We are investigating a networking issue affecting connectivity to Azure services in the West US region. Impacted customers may experience intermittent connectivity failures, increased latency, or difficulty accessing Azure services. Customers with traffic traversing the West US region may also experience downstream impact. We are exploring mitigation options on affected network devices. Early indications suggest the issue is related to network traffic flow through the impacted infrastructure; however our analysis remains ongoing. We are closely monitoring traffic while continuing our investigation. We will provide additional information as it becomes available.

3. Active – Connectivity Issues Affecting Azure Services in West US

   Major · 23 Jul 2026, 16:50 · resolved about 1 month ago

   • resolved23 Jul, 21:18

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • investigating23 Jul, 16:52

     We are investigating an issue affecting connectivity to Azure services for a subset of customers in the West US region. Impacted customers may experience intermittent issues when accessing Azure services.We will provide more information as it becomes available.

4. GitHub Issue

   Major · 8 Jul 2026, 20:41 · resolved about 2 months ago

   • resolved8 Jul, 22:46

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • investigating8 Jul, 20:48

     GitHub Enterprise Cloud with Data Residency is experiencing a service outage impacting all services, issue identified and mitigation in progress. For details please go here: : https://us.githubstatus.com/posts/details/PBJ0QTY

   • investigating8 Jul, 20:46

     GitHub Enterprise Cloud is experiencing a service outage impacting all services, issue identified and mitigation in progress. For details please go here: GitHub Enterprise Cloud - US: https://us.githubstatus.com/posts/details/PBJ0QTY

   • investigating8 Jul, 20:43

     GitHub Enterprise Cloud is experiencing a service outage impacting all services, issue identified and mitigation in progress. For details please go here: GitHub Enterprise Cloud - US

5. Mitigated – Customers leveraging a subset of services may experience 401 authentication errors

   Major · 16 Jun 2026, 01:01 · resolved 2 months ago

   • resolved16 Jun, 01:42

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • investigating16 Jun, 01:02

     What happened?Between 21:45 UTC and 23:23 UTC on 15 June 2026, Azure customers leveraging services which depend upon Microsoft Artifact Registry (MAR) may have experienced 401 authentication errors when attempting to pull images from MAR . This incident is now mitigated. Further details will be provided directly to impacted customers through the Azure Portal.

6. Active – Customers leveraging a subset of services may experience 401 authentication errors

   Major · 16 Jun 2026, 00:44 · resolved 2 months ago

   • resolved16 Jun, 01:42

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • investigating16 Jun, 00:46

     Impact Statement: Starting at 21:45 UTC on 15 June 2026, a subset of Azure customers leveraging services which depend upon MCR (Microsoft Container Registry) for storing images may experience 401 authentication errors for requests attempting to pull Microsoft images from mcr.microsoft.com.Current Status: We detected this issue via internal service monitoring upon identifying a spike of 401 errors. We’ve identified a potential underlying factor to be a recent update which introduced a code regression, and we've completed roll out of a hotfix to address the code regression and mitigate impact for affected customers. We are closely monitoring internal telemetry to validate full mitigation and prevent further occurrences. The next update will be provided within 60 minutes, or as events warrant.

7. Investigating a spike in 401 authentication errors

   Major · 16 Jun 2026, 00:04 · resolved 2 months ago

   • resolved16 Jun, 01:42

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • investigating16 Jun, 00:06

     We are actively investigating customer alerts of 401 authentication errors when pulling images from mcr.microsoft.com. We’ve identified a potential underlying factor related to a recent update made to a backed service and we are actively working on determining mitigation workstreams. More information will be provided shortly.

8. Active - Azure OpenAI Service Elevated Error Rates in multiple regions

   Major · 29 May 2026, 10:39 · resolved 3 months ago

   • resolved29 May, 22:40

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • investigating29 May, 13:42

     Impact Statement: Starting at 09:39 UTC on 29 May 2026, customers using Azure OpenAI service in multiple regions who may experience degraded request success where some requests returned errors or failed to complete. Current Status: We identified this issue through internal automated service monitoring after detecting a drop in call success rates. Our investigation indicates that the issue is linked to elevated server-side errors within a backend service layer in the affected region. We are actively investigating and working to determine the full scope and mitigation steps. The next update will be provided within 60 minutes, or sooner if there are significant developments.

   • investigating29 May, 13:34

     Impact Statement: Starting at 09:39 UTC on 29 May 2026, you have been identified as a subset of customers using Azure OpenAI service in multiple regions who may experience degraded request success where some requests returned errors or failed to complete. Current Status: We identified this issue through internal automated service monitoring after detecting a drop in call success rates. Our investigation indicates that the issue is linked to elevated server-side errors within a backend service layer in the affected region. We are actively investigating and working to determine the full scope and mitigation steps. The next update will be provided within 60 minutes, or sooner if there are significant developments.

9. Active – Network connectivity degradation in West US 2

   Major · 29 May 2026, 07:57 · resolved 3 months ago

   • resolved29 May, 22:40

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • investigating29 May, 08:10

     Impact Statement- Starting at 04:27 UTC on 29 May 2026, customers may experience increased latency, intermittent connectivity, or timeouts when accessing resources hosted in the West US 2 region, due to a power event. We are in process of recovering power and working to restore infrastructure in the region. We started seeing partial recovery and will be sending targeted communications to impacted customers through the Azure Service Health dashboard. The next update will be provided within 60 minutes.

   • investigating29 May, 07:59

     Impact Statement- Starting at 04:27 UTC on 29 May 2026, customers may experience increased latency, intermittent connectivity, or timeouts when accessing resources hosted in the West US 2 region. Engineers are actively investigating the issue and working to restore network stability. Some requests may succeed upon retry as connectivity intermittently recovers. We are sending targeted communications to impacted customers through the Azure Service Health dashboard. The next update will be provided within 60 minutes.

10. Active – Recovering - Multiple Services experiencing degradation in West US 2

    Major · 29 May 2026, 05:27 · resolved 3 months ago

    • resolved29 May, 22:40

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating29 May, 21:30

      Impact statement: Starting at 04:27 UTC on 29 May 2026, a severe thunderstorm caused widespread utility power loss across multiple West US 2 datacenter facilities, resulting in impact to multiple Azure services. Datacenter power has been fully restored, and the majority of network and storage infrastructure has recovered. Infrastructure in Availability Zone 2 has recovered and is operating normally. Residual impact is now concentrated on a subset of infrastructure within Availability Zones 1 and 3, where two storage stamps are undergoing final recovery and validation. Customers with resources deployed exclusively in Availability Zone 2 should not be affected by the remaining recovery activities; however, those with dependencies in Availability Zones 1 or 3 may continue to experience intermittent connectivity, elevated latency, or resource unavailability. The following Azure services are in the final stages of recovery: Azure SQL, Virtual Machines, Virtual Machine Scale Sets, Azure Kubernetes Service, Application Insights, Azure Monitor, and Azure Log Analytics. The following services have recovered and are operating normally: Azure Managed Grafana, Azure Database for MySQL Flexible Server, Azure Functions, Azure Database for PostgreSQL Flexible Server, Service Bus, Azure Storage, App Service (Web Apps), Azure Site Recovery, Backup (MAB), Azure Cosmos DB, Azure Resource Manager, Azure Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Data Factory, Azure Databricks, Azure Cache for Redis, and Azure Synapse Analytics. Current Status: A severe weather event, including multiple lightning strikes, affected several datacenter facilities in the West US 2 region, resulting in concurrent utility power interruptions across multiple availability zones. Backup generators activated as designed; however, during the transition to sustained generator operation, a subset of generator systems were unable to fully synchronize under the sudden facility load, while others subsequently shut down due to thermal protection mechanisms as cooling systems were impacted by the broader power disruption. Because these events occurred across multiple facilities within the same timeframe, the resulting conditions exceeded the resiliency designed for this particular failure scenario. Datacenter utility power has been fully restored. HVAC systems have normalized, ambient temperatures have returned to expected operating ranges, and the majority of network and storage infrastructure has recovered successfully. While most services have returned to normal operation, two storage stamps are completing final recovery and validation activities. These stamps have shown consistent improvement throughout the recovery process, with functionality progressively returning to expected levels. The remaining impacted services should continue recovering incrementally as validation activities complete; we are monitoring stamp health to confirm sustained stability before declaring full mitigation. Estimated Time to Resolution: With datacenter power restored and the majority of network and storage infrastructure recovered, remaining work is focused on two storage stamps completing final recovery and data integrity validation activities. Based on current progress, we estimate full-service restoration within approximately 1-2 hours. Individual services dependent on these stamps will recover progressively as validation activities are completed. Customer Guidance: Single-region workloads will recover automatically as infrastructure restoration activities are completed; no customer action is required. We recommend postponing new deployments into West US 2 until this incident is resolved and using alternate regions for urgent deployment needs. Logical availability zones assigned to customer subscriptions may map to different physical availability zones. Customers can use the Locations API to understand this mapping: https://learn.microsoft.com/rest/api/resources/subscriptions/list-locations?HTTP#availabilityzonemappings. Next Update: We will provide our next status update within 60 minutes, or sooner if significant progress is made.

    • investigating29 May, 21:26

      Impact statement: Starting at 04:27 UTC on 29 May 2026, a severe thunderstorm caused widespread utility power loss across multiple West US 2 datacenter facilities, resulting in impact to multiple Azure services. Datacenter power has been fully restored, and the majority of network and storage infrastructure has recovered. Infrastructure in Availability Zone 2 has recovered and is operating normally. Residual impact is now concentrated on a subset of infrastructure within Availability Zones 1 and 3, where two storage stamps are undergoing final recovery and validation. Customers with resources deployed exclusively in Availability Zone 2 should not be affected by the remaining recovery activities; however, those with dependencies in Availability Zones 1 or 3 may continue to experience intermittent connectivity, elevated latency, or resource unavailability. The following Azure services are in the final stages of recovery: Azure SQL, Virtual Machines, Virtual Machine Scale Sets, Azure Kubernetes Service, Azure Storage, Application Insights, Azure Monitor, and Azure Log Analytics. The following services have recovered and are operating normally: Azure Managed Grafana, Azure Database for MySQL Flexible Server, Azure Functions, Azure Database for PostgreSQL Flexible Server, Service Bus, App Service (Web Apps), Azure Site Recovery, Backup (MAB), Azure Cosmos DB, Azure Resource Manager, Azure Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Data Factory, Azure Databricks, Azure Cache for Redis, and Azure Synapse Analytics. Current Status: A severe weather event, including multiple lightning strikes, affected several datacenter facilities in the West US 2 region, resulting in concurrent utility power interruptions across multiple availability zones. Backup generators activated as designed; however, during the transition to sustained generator operation, a subset of generator systems were unable to fully synchronize under the sudden facility load, while others subsequently shut down due to thermal protection mechanisms as cooling systems were impacted by the broader power disruption. Because these events occurred across multiple facilities within the same timeframe, the resulting conditions exceeded the resiliency designed for this particular failure scenario. Datacenter utility power has been fully restored. HVAC systems have normalized, ambient temperatures have returned to expected operating ranges, and the majority of network and storage infrastructure has recovered successfully. While most services have returned to normal operation, two storage stamps are completing final recovery and validation activities. These stamps have shown consistent improvement throughout the recovery process, with functionality progressively returning to expected levels. The remaining impacted services should continue recovering incrementally as validation activities complete; we are monitoring stamp health to confirm sustained stability before declaring full mitigation. Estimated Time to Resolution: With datacenter power restored and the majority of network and storage infrastructure recovered, remaining work is focused on two storage stamps completing final recovery and data integrity validation activities. Based on current progress, we estimate full-service restoration within approximately 1-2 hours. Individual services dependent on these stamps will recover progressively as validation activities are completed. Customer Guidance: Single-region workloads will recover automatically as infrastructure restoration activities are completed; no customer action is required. We recommend postponing new deployments into West US 2 until this incident is resolved and using alternate regions for urgent deployment needs. Logical availability zones assigned to customer subscriptions may map to different physical availability zones. Customers can use the Locations API to understand this mapping: https://learn.microsoft.com/rest/api/resources/subscriptions/list-locations?HTTP#availabilityzonemappings. Next Update: We will provide our next status update within 60 minutes, or sooner if significant progress is made.

    • investigating29 May, 21:17

      Impact statement: Starting at 04:27 UTC on 29 May 2026, a severe thunderstorm caused widespread utility power loss across multiple West US 2 datacenter facilities, resulting in impact to multiple Azure services. Datacenter power has been fully restored, and the majority of network and storage infrastructure has recovered. Infrastructure in Availability Zone 2 has recovered and is operating normally. Residual impact is now concentrated on a subset of infrastructure within Availability Zones 1 and 3, where two storage stamps are undergoing final recovery and validation. Customers with resources deployed exclusively in Availability Zone 2 should not be affected by the remaining recovery activities; however, those with dependencies in Availability Zones 1 or 3 may continue to experience intermittent connectivity, elevated latency, or resource unavailability. Currently affected Azure services include, but may not be limited to (recovery validation underway): Azure SQL, Azure Managed Grafana, Virtual Machines, Virtual Machine Scale Sets, Azure Kubernetes Service, Azure Storage, Application Insights, Azure Monitor, and Azure Log Analytics. The following services have recovered and are operating normally: Azure Database for MySQL Flexible Server, Azure Functions, Azure Database for PostgreSQL Flexible Server, Service Bus, App Service (Web Apps), Azure Site Recovery, Backup (MAB), Azure Cosmos DB, Azure Resource Manager, Azure Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Data Factory, Azure Databricks, Azure Cache for Redis, and Azure Synapse Analytics. Current Status: A severe weather event, including multiple lightning strikes, affected several datacenter facilities in the West US 2 region, resulting in concurrent utility power interruptions across multiple availability zones. Backup generators activated as designed; however, during the transition to sustained generator operation, a subset of generator systems were unable to fully synchronize under the sudden facility load, while others subsequently shut down due to thermal protection mechanisms as cooling systems were impacted by the broader power disruption. Because these events occurred across multiple facilities within the same timeframe, the resulting conditions exceeded the resiliency designed for this particular failure scenario. Datacenter utility power has been fully restored. HVAC systems have normalized, ambient temperatures have returned to expected operating ranges, and the majority of network and storage infrastructure has recovered successfully. While most services have returned to normal operation, two storage stamps are completing final recovery and validation activities. These stamps have shown consistent improvement throughout the recovery process, with functionality progressively returning to expected levels. The remaining impacted services should continue recovering incrementally as validation activities complete; we are monitoring stamp health to confirm sustained stability before declaring full mitigation. Estimated Time to Resolution: With datacenter power restored and the majority of network and storage infrastructure recovered, remaining work is focused on two storage stamps completing final recovery and data integrity validation activities. Based on current progress, we estimate full-service restoration within approximately 1-2 hours. Individual services dependent on these stamps will recover progressively as validation activities are completed. Customer Guidance: Single-region workloads will recover automatically as infrastructure restoration activities are completed; no customer action is required. We recommend postponing new deployments into West US 2 until this incident is resolved and using alternate regions for urgent deployment needs. Logical availability zones assigned to customer subscriptions may map to different physical availability zones. Customers can use the Locations API to understand this mapping: https://learn.microsoft.com/rest/api/resources/subscriptions/list-locations?HTTP#availabilityzonemappings. Next Update: We will provide our next status update within 60 minutes, or sooner if significant progress is made.

    • investigating29 May, 21:14

      Impact statement: Starting at 04:27 UTC on 29 May 2026, a severe thunderstorm caused widespread utility power loss across multiple West US 2 datacenter facilities, resulting in impact to multiple Azure services. Datacenter power has been fully restored, and the majority of network and storage infrastructure has recovered. Infrastructure in Availability Zone 2 has recovered and is operating normally. Residual impact is now concentrated on a subset of infrastructure within Availability Zones 1 and 3, where two storage stamps are undergoing final recovery and validation. Customers with resources deployed exclusively in Availability Zone 2 should not be affected by the remaining recovery activities; however, those with dependencies in Availability Zones 1 or 3 may continue to experience intermittent connectivity, elevated latency, or resource unavailability. Currently affected Azure services include, but may not be limited to (recovery validation underway): Azure Database for MySQL Flexible Server, Azure SQL, Azure Managed Grafana, Virtual Machines, Virtual Machine Scale Sets, Azure Kubernetes Service, Azure Storage, Application Insights, Azure Monitor, and Azure Log Analytics. The following services have recovered and are operating normally: Azure Functions, Azure Database for PostgreSQL Flexible Server, Service Bus, App Service (Web Apps), Azure Site Recovery, Backup (MAB), Azure Cosmos DB, Azure Resource Manager, Azure Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Data Factory, Azure Databricks, Azure Cache for Redis, and Azure Synapse Analytics. Current Status: A severe weather event, including multiple lightning strikes, affected several datacenter facilities in the West US 2 region, resulting in concurrent utility power interruptions across multiple availability zones. Backup generators activated as designed; however, during the transition to sustained generator operation, a subset of generator systems were unable to fully synchronize under the sudden facility load, while others subsequently shut down due to thermal protection mechanisms as cooling systems were impacted by the broader power disruption. Because these events occurred across multiple facilities within the same timeframe, the resulting conditions exceeded the resiliency designed for this particular failure scenario. Datacenter utility power has been fully restored. HVAC systems have normalized, ambient temperatures have returned to expected operating ranges, and the majority of network and storage infrastructure has recovered successfully. While most services have returned to normal operation, two storage stamps are completing final recovery and validation activities. These stamps have shown consistent improvement throughout the recovery process, with functionality progressively returning to expected levels. The remaining impacted services should continue recovering incrementally as validation activities complete; we are monitoring stamp health to confirm sustained stability before declaring full mitigation. Estimated Time to Resolution: With datacenter power restored and the majority of network and storage infrastructure recovered, remaining work is focused on two storage stamps completing final recovery and data integrity validation activities. Based on current progress, we estimate full-service restoration within approximately 1-2 hours. Individual services dependent on these stamps will recover progressively as validation activities are completed. Customer Guidance: Single-region workloads will recover automatically as infrastructure restoration activities are completed; no customer action is required. We recommend postponing new deployments into West US 2 until this incident is resolved and using alternate regions for urgent deployment needs. Logical availability zones assigned to customer subscriptions may map to different physical availability zones. Customers can use the Locations API to understand this mapping: https://learn.microsoft.com/rest/api/resources/subscriptions/list-locations?HTTP#availabilityzonemappings. Next Update: We will provide our next status update within 60 minutes, or sooner if significant progress is made.

    • investigating29 May, 20:57

      Impact statement: Starting at 04:27 UTC on 29 May 2026, a severe thunderstorm caused widespread utility power loss across multiple West US 2 datacenter facilities, resulting in impact to multiple Azure services. Datacenter power has been fully restored, and the majority of network and storage infrastructure has recovered. Infrastructure in Availability Zone 2 has recovered and is operating normally. Residual impact is now concentrated on a subset of infrastructure within Availability Zones 1 and 3, where two storage stamps are undergoing final recovery and validation. Customers with resources deployed exclusively in Availability Zone 2 should not be affected by the remaining recovery activities; however, those with dependencies in Availability Zones 1 or 3 may continue to experience intermittent connectivity, elevated latency, or resource unavailability. Currently affected Azure services include, but may not be limited to (recovery validation underway): Azure Functions, Azure Database for MySQL Flexible Server, Azure SQL, Azure Managed Grafana, Virtual Machines, Virtual Machine Scale Sets, Azure Kubernetes Service, Azure Storage, Application Insights, Azure Monitor, and Azure Log Analytics. The following services have recovered and are operating normally: Service Bus, App Service (Web Apps), Azure Site Recovery, Backup (MAB), Azure Cosmos DB, Azure Resource Manager, Azure Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Data Factory, Azure Databricks, Azure Cache for Redis, Azure Database for PostgreSQL Flexible Server and Azure Synapse Analytics. Current Status: A severe weather event, including multiple lightning strikes, affected several datacenter facilities in the West US 2 region, resulting in concurrent utility power interruptions across multiple availability zones. Backup generators activated as designed; however, during the transition to sustained generator operation, a subset of generator systems were unable to fully synchronize under the sudden facility load, while others subsequently shut down due to thermal protection mechanisms as cooling systems were impacted by the broader power disruption. Because these events occurred across multiple facilities within the same timeframe, the resulting conditions exceeded the resiliency designed for this particular failure scenario. Datacenter utility power has been fully restored. HVAC systems have normalized, ambient temperatures have returned to expected operating ranges, and the majority of network and storage infrastructure has recovered successfully. While most services have returned to normal operation, a small subset of storage clusters and network devices did not recover cleanly and continue to limit full-service restoration. Some storage clusters remain partially unavailable or dependent on ongoing network recovery activities, and a limited number of network devices connecting compute resources to storage infrastructure remain impaired. As a result, some virtual machines are currently unable to access their underlying storage dependencies and may remain unavailable. Recovery efforts have transitioned from broad infrastructure restoration to targeted remediation of specific network devices, storage clusters, and isolated compute nodes. As these components are restored, validated, and returned to service, dependent workloads are recovering incrementally. Two storage stamps are currently completing final recovery and integrity validation activities, and services dependent on those stamps are expected to recover as this work is completed. Estimated Time to Resolution: With datacenter power restored and the majority of network and storage infrastructure recovered, remaining work is focused on two storage stamps completing final recovery and data integrity validation activities. Based on current progress, we estimate full-service restoration within approximately 2-3 hours. Individual services dependent on these stamps will recover progressively as validation activities are completed. Customer Guidance: Single-region workloads will recover automatically as infrastructure restoration activities are completed; no customer action is required. We recommend postponing new deployments into West US 2 until this incident is resolved and using alternate regions for urgent deployment needs. Logical availability zones assigned to customer subscriptions may map to different physical availability zones. Customers can use the Locations API to understand this mapping: https://learn.microsoft.com/rest/api/resources/subscriptions/list-locations?HTTP#availabilityzonemappings. Next Update: We will provide our next status update within 60 minutes, or sooner if significant progress is made.

    • investigating29 May, 20:14

      Impact statement: Starting at 04:27 UTC on 29 May 2026, a severe thunderstorm caused widespread utility power loss across multiple West US 2 datacenter facilities, resulting in impact to multiple Azure services. Datacenter power has been fully restored, and the majority of network and storage infrastructure has recovered. Infrastructure in Availability Zone 2 has recovered and is operating normally. Residual impact is now concentrated on a subset of infrastructure within Availability Zones 1 and 3, where two storage stamps are undergoing final recovery and validation. Customers with resources deployed exclusively in Availability Zone 2 should not be affected by the remaining recovery activities; however, those with dependencies in Availability Zones 1 or 3 may continue to experience intermittent connectivity, elevated latency, or resource unavailability. Currently affected Azure services include, but may not be limited to (recovery validation underway): Azure Functions, Azure Database for MySQL Flexible Server, Azure Database for PostgreSQL Flexible Server, Azure SQL, Azure Managed Grafana, Virtual Machines, Virtual Machine Scale Sets, Azure Kubernetes Service, Azure Storage, Application Insights, Azure Monitor, and Azure Log Analytics. The following services have recovered and are operating normally: Service Bus, App Service (Web Apps), Azure Site Recovery, Backup (MAB), Azure Cosmos DB, Azure Resource Manager, Azure Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Data Factory, Azure Databricks, Azure Cache for Redis, and Azure Synapse Analytics. Current Status: A severe weather event, including multiple lightning strikes, affected several datacenter facilities in the West US 2 region, resulting in concurrent utility power interruptions across multiple availability zones. Backup generators activated as designed; however, during the transition to sustained generator operation, a subset of generator systems were unable to fully synchronize under the sudden facility load, while others subsequently shut down due to thermal protection mechanisms as cooling systems were impacted by the broader power disruption. Because these events occurred across multiple facilities within the same timeframe, the resulting conditions exceeded the resiliency designed for this particular failure scenario. Datacenter utility power has been fully restored. HVAC systems have normalized, ambient temperatures have returned to expected operating ranges, and the majority of network and storage infrastructure has recovered successfully. While most services have returned to normal operation, a small subset of storage clusters and network devices did not recover cleanly and continue to limit full-service restoration. Some storage clusters remain partially unavailable or dependent on ongoing network recovery activities, and a limited number of network devices connecting compute resources to storage infrastructure remain impaired. As a result, some virtual machines are currently unable to access their underlying storage dependencies and may remain unavailable. Recovery efforts have transitioned from broad infrastructure restoration to targeted remediation of specific network devices, storage clusters, and isolated compute nodes. As these components are restored, validated, and returned to service, dependent workloads are recovering incrementally. Two storage stamps are currently completing final recovery and integrity validation activities, and services dependent on those stamps are expected to recover as this work is completed. Estimated Time to Resolution: With datacenter power restored and the majority of network and storage infrastructure recovered, remaining work is focused on two storage stamps completing final recovery and data integrity validation activities. Based on current progress, we estimate full-service restoration within approximately 2-3 hours. Individual services dependent on these stamps will recover progressively as validation activities are completed. Customer Guidance: Single-region workloads will recover automatically as infrastructure restoration activities are completed; no customer action is required. We recommend postponing new deployments into West US 2 until this incident is resolved and using alternate regions for urgent deployment needs. Logical availability zones assigned to customer subscriptions may map to different physical availability zones. Customers can use the Locations API to understand this mapping: https://learn.microsoft.com/rest/api/resources/subscriptions/list-locations?HTTP#availabilityzonemappings. Next Update: We will provide our next status update within 60 minutes, or sooner if significant progress is made.