Microsoft Reports Strong Earnings Amid Major Azure Outage

On October 29, 2025, Azure Portal and Microsoft 365 went down worldwide. Applications that depend on Microsoft servers slowed down or stopped working. Users could not access websites, apps, or cloud-connected services. This was one of the most severe outages in Microsoft's recent history. It began between 11:30 a.m. and 12 p.m. ET (16:00 UTC), according to Downdetector, just hours before the company announced its quarterly earnings. The investor relations and status pages were also down. Microsoft confirmed the outage on its status page and classified the incident as Critical across all Azure regions worldwide (North America, South America, Europe, Asia-Pacific, the Middle East, and Africa).

Companies Affected by Microsoft Outage

Users could not access Azure management functions, the Microsoft Store, Copilot AI products, or Microsoft 365 tools (Outlook, Teams, Word Online, Excel Online). Failures, delays, or timeouts continued.

Many large companies and government organizations that use Azure had a hard time.

Alaska Airlines and Hawaiian Airlines could not check in passengers or access their systems. Customers had to go to an agent at the airport to get their boarding passes and were told to expect delays. The same thing happened to Hawaiian Airlines passengers, since they rely on Alaska's systems. Heathrow Airport's website was offline.

Customers at Starbucks, Kroger, and Costco had problems with mobile ordering, loyalty programs, and point-of-sale systems. Big U.K. brands Asda and O2 said their clients could not place orders, make transactions, or talk to customer support.

Capital One, Royal Bank of Scotland, and British Telecom customers could not access their online account services. NatWest's website was impacted. The Scottish Parliament had to suspend its online voting.

Corporate IT teams processing end-of-month payroll were affected.

Microsoft Entra ID authentication failed. Developers saw endless loading screens and could not log in to Microsoft services.

Microsoft Outage Root Cause

 Microsoft said someone accidentally changed a setting in Azure Front Door. That caused the routing to break, so Azure could not direct user requests to the right servers The cloud provider also found that the Azure Front Door problem caused connection issues inside Microsoft 365's own systems.

Engineers locked down Azure Front Door so nobody could make any more changes, and turned off the broken route to stop it from causing more issues.

Microsoft started rolling things back to the last setup that actually worked, though they couldn't say how long that would take.

The company started to send traffic around the broken parts of Azure Front Door and temporarily moved the Azure Portal over to backup servers. This let users get some basic management tasks done.

Microsoft recommends the use of PowerShell or CLI to manage resources when the Azure Portal is not working. They also recommend setting up Azure Traffic Manager as a backup plan for when Front Door goes down. This is a standard redundancy and high-availability practice.

Microsoft’s Azure incident lasted over 8 hours. The company will conduct an internal retrospective and share its findings within 14 days in a final Post-Incident Review.

Microsoft Reports Strong Earnings

Microsoft reported Q1 earnings of $3.72 per share vs. $3.68 expected and revenue of $77.7 billion vs. $75.5 billion expected, up from $3.30 EPS and $65.6 billion a year ago, despite a major outage.

Azure grew about 40% and topped expectations. Operating income rose 24% to $38 billion, and net income reached $27.7 billion.

Microsoft lifted quarterly spending on new AI projects to $34.9 billion, which is 74% higher than the same quarter last year. Data centers are set to double in the next two years to serve demand that is already booked.

Microsoft holds 27 percent of OpenAI Group PBC, valued around $135 billion.

The Bigger Picture

The outage took down things you use for fun and shopping: gaming servers like Xbox Live and Minecraft, services at coffee shops, and grocery stores. It also broke important infrastructure: airline systems, banking, and government services.

An Azure outage shows how a small configuration mistake can take down an entire cloud network, affecting thousands of companies. When everything is run by just a few massive cloud companies, a problem that used to only affect one service now hits millions of people.

Amazon Web Services had a similar outage. A broken DNS configuration for DynamoDB affected social media, gaming, and financial platforms. The Azure outage is the second major failure by a different tech giant within two weeks.

The same configuration mistakes happening at big cloud companies show where the cloud setup has a built-in weakness.

Discussions resumed on how to prevent such outages. Experts say we need more backup options. Some talk about building systems that can work across multiple cloud providers. Others think governments should step in to regulate or oversee how these companies manage risk.