Microsoft Azure

Impact Statement:Starting at approximately 17:00 UTC on 05 November 2025, a subset of customers in the West Europe region may experience service disruptions or degraded performance across multiple services, including Virtual Machines, Azure Database for PostgreSQL Flexible Server, MySQL Flexible Server, Azure Kubernetes Service, Storage, Service Bus, and Virtual Machine Scale Sets, among others. Customers using Azure Databricks in West Europe may observe degraded performance when launching or scaling all-purpose and job compute workloads, which could impact Unity Catalog and Databricks SQL operations. The issue was caused by a thermal event affecting datacenter cooling systems, which led to a subset of storage scale units going offline in a single availability zone. Resources in other availability zones that depend on these storage units may also be affected.Current Status:We have recovered two of the impacted storage scale units, and customers are beginning to see signs of recovery. Recovery efforts are ongoing and progressing in parallel across other impacted storage scale units. We anticipate recovery on these units in approximately 2 hours. The next update will be provided within 2 hours, or sooner if significant developments occur.

Impact StatementStarting at 16:05 UTC on 3 November 2025, we began investigating an issue in the Australia East region that is affecting the ability to create new Virtual Machines (VMs). This issue has downstream impact on services that rely on VM creation, including Azure Backup, Azure Synapse Analytics, Azure Virtual Machines, and Azure Storage. Customers attempting to rename or modify any disk operations (including renaming resources) may also experience failures. Azure Databricks customers may experience intermittent delays or failures when launching or upsizing all‑purpose compute resources and submitting jobs. Existing VMs and running resources are not impacted.Current StatusIn this context, a pool manager is part of the orchestration layer responsible for resource creation. The issue first surfaced with one pool manager in the region, where we observed persistent allocation errors. Similar failures have since been detected across multiple pool managers. While several pool managers remain healthy and some allocations continue to succeed, retries are likely to fail due to the current load distribution design.Initial mitigation steps included restarting affected pool managers, purging cache, and moving partitions to alternate nodes. These actions did not resolve the issue. We also evaluated recent deployments and have ruled them out as a contributing factor. The service that manages these create requests has built-in resiliency to protect against this class of failure. However, during the investigation, we discovered a recent bug causing a data format inconsistency, which introduced an incompatibility between datasets and removed a layer of resiliency. We are evaluating options to deploy a hotfix to mitigate the bug, in parallel with continued analysis to determine the trigger event.We are now focusing on canceling stuck transactions that are contributing to request queue saturation and throttling, with the goal of freeing up resources and accelerating recovery. Part of this work involves ensuring internal services persist resource creation requests, which will help reduce pressure on the pool managers.While we do not yet have an estimated time of recovery (ETA), we will provide an update within 60 minutes, or sooner as new information becomes available.

Starting at approximately 16:00 UTC, customers and Microsoft services that leverage Azure Front Door (AFD) may have experienced issues resulting in latencies, timeouts and errors. We have confirmed that an inadvertent configuration change as the trigger event for this issue.We are taking several concurrent actions: Firstly where we are blocking all changes to the AFD services, this includes customer configuration changes as well. At the same time, we are rolling back our AFD configuration to our last known good state. As we rollback we want to ensure that the problematic configuration doesn't re-initiate upon recovery.Customers may have experienced problems accessing the Azure management portal. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly, while all portal extensions are working correctly there may be a small number of endpoints that might have a problem loading (i.e. Marketplace).We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update.While we dont have an ETA yet. customers can consider implementing failover strategies with Azure Traffic Manager, to fail over from Azure Front Door to your origins: https://learn.microsoft.com/azure/architecture/guide/networking/global-web-applications/overview

Users report worldwide Azure service outage, affecting access to portal.azure.com and app services. Repeated issues noted.

Impact Summary: Starting at 19:43 UTC on 09 October 2025, a subset of customers may experience issues accessing the Azure Portal or Azure Portal extensions. There is no impact to the availability of Azure resources as a result of this. Current Status: We’ve identified an underlying issue and are currently failing away from content delivery service resources that the Azure Portal interface relies on to mitigate. As we perform these mitigation steps, customers may begin to experience recovery. The next update will be provided in 60 minutes or as events warrant.

We're aware of reports of customers experiencing issues accessing the Azure Portal that we're actively investigating. More information will be provided as it is known.

Users report issues with Azure including an inability to load admin blades, general portal loading failures, repetitive VM connectivity problems, and difficulties logging in.

Impact Summary: Starting at 19:43 UTC on 09 October 2025, a subset of customers may experience issues accessing the Azure Portal, Entra Admin Portal, Intune Admin Portal and Portal extensions. The availability of Azure resources or the management of resources via programmatic methods like API is not impacted.Current Status: We have moved traffic away from the previous content delivery service resources that the Azure Portal relied on for extension content, and taken additional steps to purge caches to mitigate impact. To mitigate residual impact, we are evaluating our configuration and additional recovery steps to migrate traffic to content hosting endpoints. Some customers should be able to access. For customers continuing to experience issues, we recommend attempting a cache refresh on your browser. The next update will be provided in 2 hours or as events warrant.

Users report slow performance and login failures on Azure portal, suggesting either server overload or regional outages.

Impact Statement: Starting at 07:40 UTC on 09 October 2025, Azure customers using Azure Front Door (AFD) from EMEA, Middle East and Africa may experience intermittent delays or timeouts when accessing their services.Current Status: Azure customers using Azure Front Door (AFD) should see consistent availability with slightly higher latencies decreasing as we continue to recover additional resources.The next update will be provided within 60 minutes.