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.
Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
3 events from the most recent confirmed update back to the earliest known activity.
Microsoft restores Azure Front Door using last known good configuration
Microsoft said it restored Azure Front Door by deploying a last known good configuration following the outage. The company then gradually recovered nodes and rebalanced traffic to avoid instability and overload as dependent services came back online.
Microsoft configuration change triggers Azure and Microsoft 365 outage
Around noon on October 29, 2025, Microsoft suffered an outage affecting Azure and Microsoft 365 after an inadvertent configuration change caused latencies, timeouts, and errors. Impacted services included Azure Front Door, App Service, Azure SQL Database, Azure Portal, Microsoft Entra ID, and Microsoft Sentinel.
AWS DNS misconfiguration causes major outage in Northern Virginia
Amazon Web Services experienced a major outage attributed to a DNS misconfiguration that affected DynamoDB API endpoint resolution in the Northern Virginia region. The disruption impacted AWS services and numerous customers, including UK banks, government websites, and consumer services such as Disney+, Venmo, and Signal.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
2 references tracked. Mallory keeps watching after this page renders.
See the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Related stories
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
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.
Mar 21, 2026
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.
Mar 21, 2026
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.
Mar 21, 2026