On Wednesday, October 29, Microsoft’s Azure cloud platform and several of its associated productivity services suffered a major global outage, affecting thousands of users and disrupting key business operations worldwide. According to reports a platform that tracks online service interruptions more than 16,600 users reported issues with Azure, while nearly 9,000 experienced problems with Microsoft 365. At the peak of the outage, reports surpassed 18,000 for Azure alone.

Microsoft confirmed that the disruption resulted from an inadvertent configuration change to a portion of its Azure infrastructure, specifically impacting the Azure Front Door service and its Domain Name System (DNS). Azure Front Door is Microsoft’s global networking system designed to efficiently route traffic across its vast cloud ecosystem. A failure in DNS, which functions as the Internet’s address book, can block users entirely from reaching web applications and cloud-hosted services. The company stated that the issue began around 16:00 UTC (12 p.m. ET) and affected users across multiple regions.

The outage’s impact extended well beyond Microsoft’s direct ecosystem. Users reported disruptions with Office 365, Minecraft, Xbox Live, and Copilot, as well as delays accessing the Microsoft 365 admin center. Outlook users also faced network connectivity and add-in synchronization problems. Given Azure’s foundational role in global cloud infrastructure, the outage cascaded across industries, affecting major corporations and institutions such as Starbucks, Kroger, Costco, Alaska Airlines, Vodafone UK, and Heathrow Airport.
Alaska Airlines confirmed via its website and social media channels that its website and app were temporarily down, preventing passengers from checking in online (Reuters, The Verge).

In response, Microsoft began rolling out a recovery deployment, announcing that engineering teams were working to resolve access disruptions tied to the Azure Front Door service. The company deployed its “last known good” configuration to restore normal operations and rerouted traffic away from affected Azure components to reduce impact.
Customers unable to access Azure via the web portal were advised to use PowerShell or Command-Line Interface (CLI) tools as temporary alternatives. During mitigation efforts, Microsoft also temporarily suspended customer configuration changes to prevent further instability (Microsoft Azure Status).

The incident highlights the growing fragility of global digital infrastructure, especially as organizations increasingly rely on a few dominant cloud service providers. The outage came just over a week after a similar large-scale disruption at Amazon Web Services (AWS), which took down platforms like Reddit and Snapchat (BBC). Analysts have drawn parallels between these incidents and last year’s CrowdStrike malfunction, which caused widespread global IT outages — emphasizing how a single technical misstep can paralyze major segments of the internet.

Notably, Microsoft’s Azure disruption occurred just hours before the company’s scheduled quarterly earnings report, underscoring the delicate balance between rapid digital expansion and the systemic risks embedded within modern cloud infrastructure.