Microsoft Azure and Microsoft 365 Global Outage Due to DNS Issues
Microsoft experienced a widespread outage impacting Azure, Microsoft 365, and related services, affecting customers and organizations worldwide. The disruption began around 16:00 UTC and was attributed to DNS issues, resulting in degraded availability for services such as Azure Front Door, the Azure Portal, Intune, Exchange admin center, and authentication services. Major companies and sectors, including payroll providers, healthcare organizations, and the Dutch railway system, reported significant operational impacts, with users unable to log in or access critical business platforms. Microsoft acknowledged the outage, provided mitigation advice such as using programmatic access methods and failover strategies, but did not immediately offer an estimated time for resolution.
The outage's effects were felt across a broad spectrum of industries, with reports of internal workflow disruptions and delays in essential services like payroll processing. Microsoft advised customers to consider implementing failover strategies using Azure Traffic Manager and to monitor the Azure status page for updates. The incident highlighted the critical dependency of global businesses on Microsoft's cloud infrastructure and the cascading impact of DNS-related failures on authentication and service availability.
Timeline
Oct 30, 2025
Lingering intermittent issues continue into October 30
After the main outage was declared over, some users and services continued to experience residual or intermittent problems into 2025-10-30. Follow-up reporting noted that while the major disruption had ended, not all effects had fully cleared immediately.
Oct 29, 2025
Most Microsoft services gradually recover, with full recovery expected later that evening
Late on 2025-10-29, Microsoft said service health was improving and estimated recovery by 23:20 UTC. Most affected Azure and Microsoft 365 services were gradually restored by the end of the day, though some instability remained.
Oct 29, 2025
Microsoft says rollback completed and recovery is underway
By about 5:30 p.m. ET on 2025-10-29, Microsoft reported that rollback deployment had completed. The company said it was recovering nodes and rerouting traffic, while warning users to expect intermittent failures during restoration.
Oct 29, 2025
Outage causes downstream disruptions for third parties and customer websites
As the incident unfolded on 2025-10-29, organizations and services dependent on Microsoft infrastructure reported knock-on effects, including issues affecting Alaska Airlines, Vodafone UK, Heathrow Airport, and Azure-hosted customer websites. Reports also described broader internet-facing disruption involving services such as Zoom, Starbucks, and Capital One.
Oct 29, 2025
Microsoft identifies suspected configuration change and starts rollback
During the outage on 2025-10-29, Microsoft said it suspected an inadvertent configuration change had triggered the incident. The company blocked further customer configuration changes and began rolling back to a last known good configuration while rerouting traffic and recovering nodes.
Oct 29, 2025
Microsoft outage begins, disrupting Azure Front Door and DNS-dependent services
On 2025-10-29, a global Microsoft outage began around 11:40 a.m. to noon ET, affecting Azure Front Door availability and causing DNS-related failures. The disruption impacted Azure-hosted applications and major Microsoft services including Microsoft 365, Teams, Entra, Xbox Live, Minecraft, Outlook, and LinkedIn.
See the full picture in Mallory
Mallory subscribers get deeper analysis on every story, including:
Who’s affected and how
Deep-dive technical analysis
Actionable next steps for your team
IPs, domains, hashes, and more
Ask questions and take action on every story
Filter by topic, classification, timeframe
Get matching stories delivered automatically
Related Entities
Organizations
Sources
4 more from sources like zdnet zero day, hackread and bleeping computer
Related Stories
Microsoft Azure Outage Caused by Configuration Error
Microsoft Azure and 365 services experienced a significant outage due to an inadvertent configuration change, resulting in widespread latencies, timeouts, and errors for users. The disruption affected a broad range of Azure services, including App Service, Azure Active Directory B2C, Azure Communication Services, Azure Databricks, Azure Healthcare APIs, Azure Maps, Azure Portal, Azure SQL Database, Container Registry, Media Services, Microsoft Defender External Attack Surface Management, Microsoft Entra ID, Microsoft Purview, Microsoft Sentinel, Video Indexer, and Virtual Desktop. Microsoft responded by deploying its last known good configuration and began recovering nodes and re-routing traffic through healthy nodes, though some users continued to experience intermittent failures during the recovery process. The outage occurred just hours before Microsoft's quarterly earnings call and followed a similar cloud DNS error that had disrupted AWS users the previous week. Microsoft communicated the incident and recovery status via its Azure Status page, stating that full recovery was expected by the evening. The incident highlights the operational risks associated with cloud infrastructure and the potential for configuration errors to cause widespread service disruptions across critical business applications.
1 months ago
Microsoft 365 and Teams Outages Due to Infrastructure Issues
Microsoft Teams experienced widespread outages, with users across the United States, Europe, and other regions reporting delays in sending messages and problems with other service functions. Microsoft acknowledged the issue publicly, stating that they were investigating the cause and observing signs of recovery, but did not initially provide a root cause or timeline for full restoration. The outage disrupted communication for many organizations relying on Teams for collaboration and messaging. Separately, a significant outage affected Microsoft 365 services—including Teams, Outlook, OneDrive, and the Copilot AI assistant—in Japan and China. This disruption was traced to a critical routing misconfiguration in Microsoft's infrastructure, which isolated healthy systems and led to intermittent login failures, degraded performance, and app loading errors. Microsoft confirmed that the incident was not the result of a cyberattack and reported that engineers had rebalanced traffic to restore service, with no data loss or security breaches identified. The outages caused notable business disruption in the affected regions, particularly for organizations dependent on Microsoft’s cloud ecosystem for daily operations.
1 months ago
Microsoft cloud service disruptions affecting Microsoft 365, Exchange Online, and Windows Update/Store
Microsoft reported multiple **service-impacting incidents** across its cloud ecosystem. Administrators in **North America and Canada** experienced an outage and degraded performance in the **Microsoft 365 admin center**, with some users also unable to access the *M365 app* or raise support tickets; Microsoft said it was analyzing telemetry, usage patterns, and **CPU utilization**, and reviewing user-provided **HAR files** to isolate the root cause. Separately, **Exchange Online** quarantined legitimate messages after an updated **URL rule** incorrectly marked some URLs as phishing, disrupting email flow for affected customers while Microsoft worked to release quarantined mail and unblock legitimate URLs. In another disruption, Microsoft attributed **Windows Update** and **Microsoft Store** failures/timeouts (notably impacting Windows 11 users) to a **utility power interruption** at a **West US datacenter**, which cascaded into issues with **Azure storage clusters** supporting content delivery; backup power engaged and power was later stabilized, but service recovery required additional remediation beyond restoring electricity.
1 months ago