Microsoft Azure Outage Disrupts Global Services

On Wednesday, October 29, 2025, Microsoft’s Azure cloud services experienced a significant outage, causing widespread disruption for customers globally. The incident, which began around 9 a.m. Pacific Standard Time (16:00 UTC), impacted a broad array of services, from major airlines and financial platforms to popular gaming networks and productivity tools. This event follows closely on the heels of a massive Amazon Web Services (AWS) outage just last week, raising concerns about the resilience of the internet’s increasingly centralized infrastructure.

The Cause: An Inadvertent Configuration Change

Microsoft quickly acknowledged the issues, stating on its Azure status page that the disruption stemmed from “Azure Front Door (AFD) issues resulting in a loss of availability of some services.” The company “suspect[ed] that an inadvertent configuration change” was the trigger event, leading to DNS (Domain Name System) problems. Azure Front Door is a global content delivery network (CDN) service that helps deliver web content efficiently, and its malfunction had far-reaching consequences.

Widespread Impact Across Industries

The outage crippled numerous Microsoft-owned services and many third-party platforms that rely on Azure’s cloud infrastructure:

• Microsoft Services: Users reported issues with Microsoft 365 (including Office apps like Word, Excel, Outlook, and Teams), Xbox (Game Pass, Xbox Live), Minecraft, Microsoft Copilot, Microsoft Entra, and the Microsoft Store. Even access to the Azure Portal itself was affected, with Microsoft advising customers to use programmatic methods like PowerShell or CLI to access resources.
• Airline Operations: Alaska Airlines was among the high-profile casualties, posting on X (formerly Twitter) that the Azure outage was disrupting systems, including their website function. Passengers for both Alaska and Hawaiian airlines were directed to agents for check-in as online services were unavailable.
• Consumer and Business Platforms: Downdetector, an outage tracking website, showed spikes of nearly 10,000 reports across multiple Microsoft platforms, with Azure alone seeing over 19,600 user reports. Affected services included Starbucks.com, Chris Hemsworth’s fitness app Centr, Workfront via the Adobe Experience Platform, the Pearson Vue testing system for schools, and even some university document upload systems. Other major brands like Capital One banking, Kroger, Costco, Xfinity, and Walmart also experienced issues. The Dutch railway system reported problems with its online travel planning and ticket machines.

Microsoft’s Response and Ongoing Recovery Efforts

In response to the crisis, Microsoft initiated several concurrent actions. The company blocked all changes to AFD services and began rolling back its AFD configuration to a “last known good state.” They also rerouted affected traffic to “alternate healthy infrastructure” as a short-term mitigation. Despite these efforts, Microsoft did not provide an immediate estimated time of arrival (ETA) for when the rollback would be completed, indicating a complex recovery process. At one point, even Microsoft’s own Azure status page became inaccessible, further complicating communication.

A Recurring Theme: Cloud Vulnerability

This Azure outage marks the second major cloud service disruption in less than two weeks. Just nine days prior, on October 20, 2025, Amazon Web Services (AWS) suffered a “massive outage” due to DNS issues in its US-EAST-1 region. That incident, which also stemmed from a “single point of failure,” affected millions of users and over 1,000 companies globally, including Snapchat, Reddit, Fortnite, Venmo, Alexa, and Prime Video, as reported by digitaltrendstoday.com. Some reports even suggested that AWS was experiencing additional issues simultaneously with the Azure problems on October 29th.

The back-to-back failures of two of the world’s largest cloud providers underscore the inherent vulnerabilities of a highly centralized internet. As more of our digital lives and critical business operations migrate to these vast cloud infrastructures, the ripple effect of a single technical fault can be catastrophic. These incidents serve as a powerful reminder of the fragility that comes with heavy reliance on a few key players and reignite discussions about the need for more distributed and resilient internet architectures.