A DNS misconfiguration caused widespread interruptions to major cloud, collaboration, gaming and critical enterprise applications worldwide.
On October 29, 2025, Azure cloud services and Microsoft 365 platforms experienced a widespread global DNS outage that severely impacted access.
According to various reports, the outage began at approximately 16:00 UTC due to an inadvertent configuration change in Microsoft’s Azure Front Door (AFD) content delivery network, which manages DNS traffic routing for many Microsoft services. This DNS misconfiguration blocked tens of thousands of users worldwide from accessing critical platforms such as the Azure Portal, Microsoft 365 admin center, Outlook, Teams, SharePoint, Intune, Xbox Live, and Minecraft.
The outage caused extensive disruptions for a broad range of users, including enterprises in healthcare, finance, and education, along with consumers relying on Microsoft’s gaming ecosystem. Authentication failures had prevented many employees from logging into corporate networks, and major organizations like the Dutch railway system had reported issues with travel planning and ticketing platforms. Even Microsoft’s own status pages suffered outages, preventing users from monitoring the incident effectively during the early stages.
To mitigate service impact, Microsoft engineers responded promptly, by halting all new AFD configuration changes, rolling back to the last stable setup, and rerouting traffic to unaffected infrastructure. Despite these efforts, users experienced intermittent access issues, request failures, and latency for several hours.
Microsoft has recommended customers to use command-line tools such as PowerShell and CLI as workarounds to manage Azure resources temporarily.
This incident highlights how DNS infrastructure is a critical vulnerability point within cloud ecosystems, as DNS failures prevent access to services regardless of underlying server availability. The timing followed a recent substantial DNS outage at Amazon Web Services (AWS), emphasizing ongoing concerns about centralized cloud and DNS resilience. Microsoft projected full recovery by late October 29, and has advised users to implement failover solutions such as Azure Traffic Manager to improve service continuity during such incidents.
This DNS outage demonstrates the profound operational impact that DNS-level failures have on both enterprise and consumer users globally, exposing the cascading risks inherent in centralized cloud infrastructure dependencies.
