Microsoft has issued that the issues have been resolved.
Official Microsoft Update :
"Impact Statement:
Starting at approximately 16:00 UTC on 29 October 2025, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. We have confirmed that an inadvertent configuration change was the trigger event for this issue.
Affected Azure services may have included, but were not limited to:
App Service, Azure Active Directory B2C, Azure Communication Services, Azure Databricks, Azure Healthcare APIs, Azure Maps, Azure Portal, Azure SQL Database, Azure Virtual Desktop, Container Registry, Media Services, Microsoft Defender External Attack Surface Management, Microsoft Entra ID (Mobility Management Policy Service, Identity & Access Management, and User Management UX), Microsoft Purview, Microsoft Sentinel (Threat Intelligence), and Video Indexer.
Current status:
We have completed deployment of our ‘last known good’ configuration, and recovery is progressing steadily. We are currently recovering nodes and re-routing traffic through healthy nodes across the global fleet. As recovery continues, some requests may still land on unhealthy nodes, resulting in intermittent failures or reduced availability for a subset of customers.
This recovery effort involves reloading configurations and rebalancing traffic across a large number of nodes to restore full operational scale. The process is gradual by design, ensuring stability and preventing overload as dependent services recover.
Mitigation has been implemented for the AFD service for most customers, and services across the affected regions have largely recovered. We are continuing to work on residual impact and will closely monitor the situation in the coming hours.
Customer configuration changes remain temporarily blocked to prevent new deployments that could interfere with recovery. We will notify customers once this block has been lifted."
Posted Oct 29, 2025 - 22:37 EDT