Microsoft Corporation confirmed a series of platform issues within its Azure East US region on April 24, 2026, impacting a broad range of cloud services. According to the official Azure Service Health dashboard, the incident began at approximately 11:39 UTC. The disruption primarily affected customers attempting to provision new resources, scale existing workloads, or maintain stable connectivity to hosted applications.
Initial telemetry indicated that the root cause was localized to a single availability zone within the East US geography. However, as automated failover mechanisms and manual traffic rerouting protocols were initiated, secondary effects were observed across other zones in the region. This led to increased latency and intermittent request timeouts for services including Azure Virtual Machines, Azure App Service, and Azure Functions.
Technical logs provided by Microsoft identified specific failures in the underlying compute and storage clusters. Users reported that API calls to the Azure Resource Manager (ARM) were returning 500-series error codes, preventing administrative actions via the Azure Portal, Command Line Interface (CLI), and Software Development Kits (SDKs). Furthermore, the Azure Kubernetes Service (AKS) experienced control plane instability, hindering the deployment of containerized applications and the scaling of node pools.
Microsoft engineers issued a statement at 13:15 UTC, confirming that they were investigating a potential infrastructure power issue within one of the primary data centers in the region. The company noted that recovery efforts were underway and that they were working to shift traffic to healthy infrastructure while mitigating the impact on downstream services. By 14:30 UTC, some services began to show signs of recovery, though provisioning remained throttled to ensure platform stability.
The East US region is one of Azure's largest and most critical hubs, serving a high concentration of enterprise clients and government agencies. While Microsoft has not disclosed the exact number of affected organizations, the scope of the East US region suggests that thousands of subscription IDs were likely impacted. This event follows a period of high uptime for the region, highlighting the complexities of managing hyper-scale cloud environments.
As of the latest update at 15:00 UTC, Microsoft has successfully restored connectivity for the majority of existing workloads, but the backlog of provisioning requests continues to cause delays. The company has advised customers to monitor the Service Health dashboard for zone-specific updates and to consider utilizing cross-region disaster recovery strategies for mission-critical applications. A full Root Cause Analysis is expected to be released within 72 hours of the incident's resolution.