Impact Statement: Starting at 04:27 UTC on 29 May 2026, we are investigating an incident which is impacting multiple services in West US 2, due to a power event. This impacts service accessibility in the region, with customers potentially experiencing increased latency and intermittent connectivity, including timeouts when connecting to resources. Affected Azure services include, but are not limited to: App Service, Azure Backup, Azure Container Registry, Azure Cosmos DB, Azure Database for MySQL flexible servers, Azure IoT Hub, Azure Kubernetes Service (AKS), Azure Monitor, Application Insights, Log Analytics, Azure NetApp Files, Azure Site Recovery, Azure Synapse Analytics, Microsoft Defender for Cloud, Azure Databricks and Azure Storage. Current Status: We identified this issue through our automated monitoring after detecting elevated alerts related to network and infrastructure health in the West US 2 region.  The issue was triggered by a power event in the datacenter, which impacted underlying infrastructure and led to increased latency and intermittent connectivity for select resources. We are aware of the impact and are actively investigating.  Mitigation efforts are underway to restore affected network components across dependent services, including Storage and Compute. Customers may begin to see signs of recovery as these actions progress.  The next update will be provided within 60 minutes, or sooner if there are significant developments.

A severe thunderstorm caused a widespread power outage at the West US 2 datacenter starting on May 29, 2026. This resulted in a region-wide, multi-service outage affecting many Azure services, including compute, database, and monitoring tools. Customers are experiencing connectivity failures, timeouts, and elevated error rates as a result. The outage was caused by a complete utility power loss and subsequent generator failures, exceeding the datacenter's redundancy capabilities. Backup generators initially activated but failed to fully compensate due to various mechanical and electrical issues. HVAC systems are being restarted, and equipment is being staged-powered to prevent thermal issues. Network devices and storage arrays are being restored in sequence, with storage dependencies acting as a bottleneck. Several services have been confirmed to be operating normally, including Azure Service Bus and Cosmos DB. Customers are advised to consider failing over to other regions and pause new deployments to West US 2. Constant monitoring is recommended via the Azure status page for live updates. The next update regarding the situation will be released within an hour.

Impact Statement: Starting at 11:39 UTC on 24 April 2026, a platform issue resulted in provisioning, scaling, and connectivity issues for customers with Azure workloads hosted in the East US region. This issue initially affected one availability zone in East US. As traffic was automatically rerouted and shared services were involved, some customers in other availability zones may have also experienced an impact. Current Status: We detected this issue through our automated monitoring, which identified an unusual increase in failures within the services supporting virtual machine and virtual machine scale set operations in the East US region. We have taken steps to stabilize the affected services and address the underlying issue, while continuing the investigation to determine contributing factors. The next update will be shared within 60 minutes, or as events warrant.

Impact statement: As early as 19:46 UTC on 2 February 2026, we became aware of an ongoing issue causing customers to receive error notifications when performing service management operations - such as create, delete, update, scaling, start, stop - for Virtual Machines (VMs) across multiple regions. These issues are also causing impact to services with dependencies on these service management operations - including Azure Arc Enabled Servers, Azure Batch, Azure Cache for Redis, Azure Container Apps, Azure DevOps (ADO), Azure Kubernetes Service (AKS), Azure Load Testing, Azure Firewall, Azure Search, Azure Virtual Machine Scale Sets (VMSS), and GitHub (see https://www.githubstatus.com). Current status: We determined that these issues were caused by a recent configuration change that affected public access to certain Microsoft‑managed storage accounts, used to host extension packages. We have applied our mitigation across all impacted regions, so the vast majority of customers and services should be mitigated. We are actively working to mitigate any remaining impact, currently performing final checks to ensure that all Storage accounts have been mitigated appropriately. We expect that any customers still experiencing residual impact should be mitigated by approximately 02:00 UTC, one hour from now. Our next update will be provided by then, or sooner if we have progress to share.

We have identified an issue in Network Infrastructure in North Central US for a subset of customers. More information will be provided by communications on Service Health section of the Azure Portal under the tracking ID FMGC-N_G.

Impact Statement: Starting at 16:50 China Standard Time (CST) on 08 December 2025, customers in Azure China regions experienced failures accessing resources through Azure Portal or performing service management operations. Login attempts via Azure REST APIs, PowerShell, or CLI failed. Retrying operations might have succeeded intermittently. Current Status: Engineering teams identified the cause and applied mitigation. All Azure China regions have recovered at 23:53 on 08 December 2025 China Standard Time (CST) and are being actively monitored for stability. Work continues to restore Azure Databricks to 100% availability. Next Update: We will provide the next update within 60 minutes or sooner if significant developments occur

We are currently receiving telemetry and additional reports from customers who may be experiencing intermittent latency when accessing resource in the Azure Portal in Europe. We are actively investigating.

Azure Resource Manager (ARM) is experiencing an issue starting from 08:00 CST on 05 September 2024, affecting several services for Service Management operations. This includes Azure Databricks, Azure Data Factory, Microsoft Purview, Azure MySQL, and other services leveraging ARM in China North 3. For Azure Databricks, customers may experience failures when launching job and all-purpose cluster resources. In Azure Data Factory, publishing changes in the portal for resources in China North 3 will not be completed as expected. Similarly, create/update/delete operations for Microsoft Purview Account and Azure MySQL in China North 3 will not be completed as expected. Other services using ARM within Resource Groups in China North 3 may also face service management operation failures. Engineers have identified a possible underlying cause and are working on mitigation options. The next update will be provided in 2 hours, or as events warrant.

Impact Statement: Starting approximately at 11:45 UTC on 30 July 2024, a subset of customers may have experienced issues connecting to Microsoft services globally. Current Status: An unexpected usage spike resulted in Azure Front Door (AFD) and Azure Content Delivery Network (CDN) components performing below acceptable thresholds, leading to intermittent errors, timeout, and latency spikes. We have implemented network configuration changes and have performed failovers to provide alternate network paths for relief. Our monitoring telemetry shows improvement in service availability from approximately 14:10 UTC onwards. As we investigate reports of specific services and regions that are still experiencing intermittent errors, we believe that our network configuration changes have successfully mitigated the impacts of the usage spike, but that these changes are causing some side effects to certain services. We are updating our mitigation approach to minimize these side effects, and applying these following Safe Deployment Practices - beginning in Asia Pacific regions and then expanding in phases. We will provide an update on our continued mitigation efforts by 19:00 UTC, or sooner if we have progress to share.

We are aware of an issue that started on 19 July 2024 at 04:09 UTC, which resulted in customers experiencing unresponsiveness and startup failures on Windows machines using the CrowdStrike Falcon agent, affecting both on-premises and various cloud platforms (Azure, AWS, and Google Cloud). For additional recovery options please review https://aka.ms/CSfalcon-VMRecoveryOptions

Impact Statement: Starting at approximately 21:56 UTC on 18 Jul 2024, a subset of customers may experience issues with multiple Azure services in the Central US region including failures with service management operations and connectivity or availability of services. Current Status: We are aware of this issue and have engaged multiple teams. We’ve determined the underlying cause. A backend cluster management workflow deployed a configuration change causing backend access to be blocked between a subset of Azure Storage clusters and compute resources in the Central US region. This resulted in the compute resources automatically restarting when connectivity was lost to virtual disks. We are currently applying mitigation. Customers should see signs of recovery at this time as mitigation applies across resources in the region. The next update will be provided in 60 minutes, or as events warrant. https://learn.microsoft.com/azure/architecture/resiliency/recovery-loss-azure-region

- CrowdStrike Falcon agents on Windows VMs may cause a bug check and restart loop since July 18th, 19:00 UTC. - Microsoft recommends attempting multiple restarts through the Azure Portal or CLI. - Restoring from a backup prior to July 18th, 19:00 UTC is recommended. - Repairing the OS disk offline and deleting the file "Windows/System/System32/Drivers/CrowdStrike/C00000291*.sys" may resolve the issue. - CrowdStrike has removed the affected update. - Customers facing persistent issues should contact CrowdStrike. - Microsoft is investigating further mitigation options. - Encrypted disks may require additional steps for unlocking. - The disk can be reattached to the original VM after the file deletion. - Microsoft will provide updates on mitigation options as they become available.