Active - Multiservice impact for Azure Workloads in East US

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: Starting at 11:39 UTC on 24 April 2026, a subset of customers with resources in the East US region may experience failures or delays when provisioning, scaling, or updating Azure resources. 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 also experience impact. Existing running workloads may also have intermittent connectivity issues to existing Virtual Machines and Virtual Desktop sessions.Services with reported impact in East USVirtual Machines and Virtual Machine Scale Sets, Azure Kubernetes Service (AKS), Azure Application Gateway, Azure Virtual Desktop, Azure Databricks, Azure Data Explorer, Azure Cache for Redis, Azure Synapse, Azure Database for PostgreSQL, Azure Database for PostgreSQL - Flexible Server, and Microsoft Fabric, and additional services that depend on new compute allocation in the region.Current Status: Engineering has identified a suspected triggering deployment and a rolling rollback is actively underway across the affected availability zones. Traffic is being rebalanced within the region. Mitigation is progressing; full recovery has not yet been validated.Recommended customer actionsFor new deployments where workload placement allows, consider alternate Azure regions while mitigation continues.Consider pausing East US CI/CD pipelines to avoid cascading failures from failed retries.Defer non-urgent AKS node pool updates and cluster scale operations in East US.The next update will be shared within 60 minutes, or as events warrant.

Impact Statement: Starting at 11:39 UTC on 24 April 2026, a subset of customers with resources in the East US region may experience failures or delays when provisioning, scaling, or updating Azure resources. 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 also experience impact. Existing running workloads may also have intermittent connectivity issues to existing Virtual Machines and Virtual Desktop sessions.Current Status: Engineering has identified a suspected triggering deployment and a rolling rollback is actively underway across the affected availability zones. Traffic is being rebalanced within the region. Customers may begin to see recovery if using resources in AZ 02 and AZ03, with Availability Zone 01 currently in progress. Please refer to this documentation to understand the logical to physical availability zone mapping for your subscription. Mitigation is progressing; full recovery has not yet been validated.The next update will be shared within 60 minutes, or as events warrant.

Impact Statement: Starting at 11:39 UTC on 24 April 2026, a subset of customers with resources in the East US region may experience failures or delays when provisioning, scaling, or updating Azure resources. 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 also experience impact. Existing running workloads may also have intermittent connectivity issues to existing Virtual Machines and Virtual Desktop sessions.Current Status: Our team has identified a suspected triggering deployment and a rollback is actively underway across the affected availability zones (AZs). Traffic is being rebalanced within the region.Customers using resources in AZ02 and AZ03 should begin to see recovery, while mitigation in AZ01 is still in progress (some recovery may be observed). Please refer to this documentation to understand the logical to physical availability zone mapping for your subscription. Some downstream services are also starting to recover. Mitigation is progressing; full recovery has not yet been validated.The next update will be shared within 60 minutes, or as events warrant.

Impact Statement: Starting at 11:39 UTC on 24 April 2026, a subset of customers with resources in the East US region may experience failures or delays when provisioning, scaling, or updating Azure resources. 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 also experience impact. Existing running workloads may also have intermittent connectivity issues to existing Virtual Machines and Virtual Desktop sessions.Current Status: Our team has identified a suspected triggering deployment, and a rollback is actively underway across the Availability Zone (AZ) 01 and is showing significant improvements. As the mitigation efforts are ongoing, we detected a potential slight regression in AZ02 and AZ03 which we are actively investigating and monitoring.  Please refer to this documentation to understand the logical to physical availability zone mapping for your subscription. Some downstream services are also starting to recover. We expect mitigation to be completed in the next 60 minutes. The next update will be shared within 60 minutes, or as events warrant.

Impact Statement: Starting at 11:39 UTC on 24 April 2026, a subset of customers with resources in the East US region may experience failures or delays when provisioning, scaling, or updating Azure resources. 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 also experience impact. Existing running workloads may also have intermittent connectivity issues to existing Virtual Machines and Virtual Desktop sessions.Current Status: Our team has identified a suspected triggering deployment, and rollback is on progress and is now completed across the Availability Zones AZ01 and AZ03. Customers using those availability zones should start to see significant improvements. Some downstream services are also starting to recover and should yield successful results.To address the potential slight regression in AZ02, we're currently rolling back as a fix which is expected to be completed in the next 3 hours. We are actively monitoring the fix as it is being applied in the mentioned AZs.Please refer to this documentation to understand the logical to physical availability zone mapping for your subscription. Some downstream services are also starting to recover. We expect mitigation to be completed in the next 60 minutes. The next update will be shared within 60 minutes, or as events warrant.

Impact Statement: Starting at 11:39 UTC on 24 April 2026, a subset of customers with resources in the East US region may experience failures or delays when provisioning, scaling, or updating Azure resources. 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 also experience impact. Existing running workloads may also have intermittent connectivity issues to existing Virtual Machines and Virtual Desktop sessions.Current Status: Our team has identified a suspected triggering deployment, and rollback is on progress and is now completed across the Availability Zones AZ01 and AZ03. Customers using those availability zones should start to see significant improvements. Some downstream services are also starting to recover and should yield successful results.To address the potential slight regression in AZ02, we're currently rolling back as a fix which is expected to be completed in the next 3 hours. We are actively monitoring the fix as it is being applied in the mentioned AZs.Please refer to this documentation to understand the logical to physical availability zone mapping for your subscription. Some downstream services are also starting to recover. We expect mitigation to be completed in the next 3 hours. The next update will be shared within 60 minutes, or as events warrant.

Impact Statement: Starting at 11:39 UTC on 24 April 2026, a subset of customers with resources in the East US region may experience failures or delays when provisioning, scaling, or updating Azure resources. 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 also experience impact. Existing running workloads may also have intermittent connectivity issues to existing Virtual Machines and Virtual Desktop sessions.Current Status: We identified a suspected triggering deployment, and a rollback has been completed Availability Zone (AZ) 01. Customers should observe improvements with the services. Some downstream services are also starting to recover. While previous communications indicated AZ03 recovery was complete, we are now addressing a regression and we're rolling back changes in AZ02 and AZ03 extending our previous ETA estimates. Mitigation in these zones is expected to be completed within the next 2 hours.Please refer to this documentation to understand the logical to physical availability zone mapping for your subscription. The next update will be shared within 60 minutes, or as events warrant.

Impact Statement: Starting at 11:39 UTC on 24 April 2026, a subset of customers with resources in the East US region may experience failures or delays when provisioning, scaling, or updating Azure resources. 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 also experience impact. Existing running workloads may also have intermittent connectivity issues to existing Virtual Machines and Virtual Desktop sessions.Current Status: Rollback is complete for Availability Zone (AZ) 01 and AZ03, and is still in progress for AZ02. Mitigation is expected to complete within the next 1 hour.Customers should observe improvements to their services, and downstream services are also starting to recover.Please refer to this documentation to understand the logical to physical availability zone mapping for your subscription. The next update will be shared within 60 minutes, or as events warrant.

Impact Statement: Starting at 11:39 UTC on 24 April 2026, a subset of customers with resources in the East US region may experience failures or delays when provisioning, scaling, or updating Azure resources. 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 also experience impact. Existing running workloads may also have intermittent connectivity issues to existing Virtual Machines and Virtual Desktop sessions.Current Status: Rollback is complete across all AZs, and availability has returned to expected levels. We are monitoring recovery as downstream services continue to mitigate. If customers are still experiencing issues, restarting resources should restore application health.The next update will be shared within 30 minutes, or as events warrant.

Between 11:39 UTC on 24 April 2026 and 00:15 UTC on 25 April 2026, a platform issue resulted in an impact to a subset of Azure services in the East US region. Impacted customers experienced failures or delays when provisioning, scaling, or updating Azure resources. Intermittent connectivity issues may also be seen on existing running workloads in Virtual Machines and Azure Virtual Desktop sessions. This issue is now mitigated. An update with more information will be provided shortly via Azure Service Health portal and on the Azure status history page.