Azure Service Outage

From Microsoft updates:

An unintended configuration change in Azure Front Door (AFD) caused a global service disruption by introducing an invalid state that prevented numerous nodes from loading properly. This resulted in latency, timeouts, and uneven traffic distribution. The root cause was a deployment process flaw combined with a software defect that allowed the invalid configuration to bypass validation. Microsoft restored stability by rolling back to the last known good configuration and has since implemented additional safeguards to prevent recurrence.

For more details, please refer to the Microsoft status page: https://azure.status.microsoft/en-us/status/history/

If you experience any other issues, please don’t hesitate to contact our technical support by submitting a ticket: https://helpcenter.zensai.com/hc/en-us/articles/360019112178-Get-help-from-the-Zensai-Product-Support-team

We are pleased to report that functionality is beginning to return across all regions. Access to all aspects of Learn365 and Perform & Engage 365 should now start to be restored for users.
Please be aware that Microsoft is continuing efforts to fully resolve the issue, so you may still experience intermittent access or degraded performance during this time. We appreciate your patience and will provide further updates as the situation evolves.

Microsoft has identified the services affected by the outage:
Affected Azure services include, but are not limited to: App Service, Azure Active Directory B2C, Azure Communication Services, Azure Databricks, Azure Healthcare APIs, Azure Maps, Azure Portal, Azure SQL Database, Container Registry, Media Services, Microsoft Defender External Attack Surface Management, Microsoft Entra ID, Microsoft Purview, Microsoft Sentinel, Video Indexer, and Virtual Desktop.
Per Microsoft:
As recovery progresses, some requests may still land on unhealthy nodes, resulting in intermittent failures or reduced availability until more nodes are fully restored. This recovery effort involves reloading configurations and rebalancing traffic across a large volume of nodes to restore full operational scale. The process is gradual by design, ensuring stability and preventing overload as dependent services recover. We expect continued improvement across affected regions. This means we expect recovery to happen by 23:20 UTC on 29 October 2025

Current status from Microsoft:
We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement.

Current status from Microsoft:
We have confirmed that an inadvertent configuration change as the trigger event for this issue.

We have initiated the deployment of our 'last known good' configuration. This is expected to be fully deployed in about 30 minutes from which point customers will start to see initial signs of recovery. Once this is completed, the next stage is to start to recover nodes while we route traffic through these healthy nodes.

Customer configuration changes will remain blocked during this time as we work towards mitigation. We will communicate to customers when this block is reverted.

Microsoft has reported the following:

"We began experiencing Azure Front Door issues resulting in a loss of availability of some services. In addition, customers may experience issues accessing the Azure Portal."

We are continuing to assess the situation.

Starting at approximately 16:00 UTC, Microsoft reported DNS issues that are affecting access to the Azure Portal and potentially other services. Microsoft has initiated mitigation steps expected to restore portal access shortly and is actively investigating the root cause.

We are continuing to investigate this issue.

We are currently aware of an issue with an Azure service outage. We are actively investigating the issue.