Azure outage latest update: Azure services restored? What went wrong hours before Microsoft's Q3 results announcement and how was it fixed

Azure outage restored: Microsoft on Thursday confirmed that its Azure services have been restored across affected regions after the cloud computing platform on Wednesday reported a massive outage. The widespread disruption impacted not only Microsoft-owned platforms like Microsoft 365, Minecraft, Outlook, and Xbox Live, but also Alaska Airlines, Starbucks, and other services, impacting millions of users across industries temporarily disconnected. Outage tracker Downdetector showed thousands of reports of issues with a number of websites around the world over several hours.

Microsoft said some users of Microsoft 365 saw delays with Outlook among other services, but by 21:00GMT, many websites that went down were once again accessible after the company restored a prior update.

Microsoft posted strong third-quarter earnings despite a major Azure service outage. The company said its Intelligent Cloud segment recorded solid growth, with Azure maintaining double-digit gains. CEO Satya Nadella highlighted Microsoft’s focus on resilience and innovation, adding that adoption of Copilot across Microsoft 365 and Bing is growing rapidly.


ALSO READ: November stimulus payments for US citizens confirmed: Check amount of money, eligibility criteria, key dates and more

Azure service outage: What caused the disruption?

Microsoft Azure services experienced an outage between 3:45pm UTC (9:15pm IST) on October 29 and 12:05am UTC (5:35am IST) on October 30. Customers and Microsoft services that use AFD experienced latencies, timeouts, and errors, the company explained on a support page.

Microsoft said business Microsoft 365 customers experienced problems. Some web pages on Microsoft also directed users to an error notifications that read "Uh oh! Something went wrong with the previous request."

Microsoft has confirmed that a DNS failure in its Azure Front Door service caused the recent outage. The issue, which began at 15:45 UTC on October 29 and lasted until 00:05 UTC on October 30, 2025, affected customers and Microsoft services using Azure Front Door, leading to delays, timeouts, and errors.

ALSO READ: 3I/ATLAS Interstellar comet live tracker: When and where to watch ATLAS as it approaches Sun? Latest update on location, date, time

Microsoft further explained that the trigger was traced back to a faulty tenant configuration deployment process. The company acknowledged that its protection mechanisms, which are in place to validate and block any erroneous deployments, failed due to a software defect. It allowed the deployment process to bypass the safety validations that are in place.

Outage tracking platform Downdetector started tracking problems with Azure services at 9:17pm IST, and the complaints peaked at 9:47pm IST, with more than 16,000 reports. Issues were reported with both server connections and domains. According to Microsoft's Azure Status history, the service outage was caused due to configuration error which led to service failure across multiple regions. The company revealed that it deployed a rollback to a stable configuration which gradually led to service restoration after several hours.

Microsoft Azure outage: How did the company resolve it?

After the outage was reported, Microsoft said it immediately stopped all future configuration changes to prevent the faulty system from spreading. The company then restored its previous stable configuration across its global network and to recover services, engineers reloaded configurations on several servers and gradually balanced traffic to avoid overload once normal operations resumed.

ALSO READ: As US government shutdown enters fourth week, 42 million Americans brace for cruelest hit from November as hunger crisis looms

For now, customers cannot make configuration changes to Azure Front Door (AFD). Microsoft said it will notify users once this restriction is lifted. Although the main issue has been fixed, some users may still face minor problems. The company added that it has strengthened safeguards and introduced extra validation and rollback controls to avoid similar outages in the future. Microsoft will also conduct an internal review to understand the cause and will share its findings with affected customers within 14 days as part of a Post Incident Review (PIR).