On October 29, 2025, Microsoft experienced a major Azure outage starting around noon, disrupting services including Microsoft 365, Xbox, and Minecraft. The issue stemmed from problems with Azure Front Door, affecting availability and Azure Portal access, while investigations examined domain name system involvement.
The outage impacted consumers and businesses reliant on Azure infrastructure. Microsoft 365 users reported difficulties with email, collaboration tools, and productivity applications. Xbox players encountered login issues and service interruptions during online gaming sessions. Minecraft servers faced connectivity problems, halting multiplayer experiences for numerous users worldwide.
Business operations suffered as well, with Alaska Airlines among the affected entities. The airline reported disruptions to its systems, potentially delaying customer services and internal processes dependent on Azure-hosted applications. Other organizations using Azure for cloud-based operations encountered similar challenges in accessing data and running workloads.
Microsoft identified the root cause in Azure Front Door, a service managing traffic distribution and load balancing across global data centers. This component’s malfunction led to cascading effects, reducing service availability and complicating portal logins for administrators and developers. Parallel probes revealed complications in the domain name system, which resolves internet addresses and directs traffic to Azure resources.
The timing amplified the incident’s visibility, occurring hours before Microsoft’s quarterly earnings report release. This proximity underscored the extensive reliance of Microsoft’s ecosystem on Azure for operational stability and revenue generation.
Outage reports surged on monitoring platforms like Downdetector, with user complaints peaking in the afternoon. Thousands of entries documented issues across affected services, providing real-time visibility into the disruption’s scale.
To address the problem, Microsoft rerouted the Azure Portal traffic away from the faulty Azure Front Door configuration. The company advised users to employ alternative access methods, including programmatic tools such as PowerShell scripts and command-line interfaces (CLI), which bypassed the portal’s web-based entry points and restored functionality for many tasks.
Efforts focused on restoring full service capacity, with updates communicated through official channels to keep stakeholders informed during the resolution process.
