Microsoft says months-old bug caused global Microsoft 365 outage
Microsoft has identified a software bug from July as the cause of a significant global outage of Microsoft 365 services that lasted nearly 24 hours.

A months-old software bug introduced in July triggered a worldwide outage of Microsoft 365 services on November 12, affecting applications like Outlook, Exchange Online, and Teams, according to Microsoft. The incident caused more than 80% of its networking gateway servers to become unresponsive, disrupting essential business communications for users globally.
The outage began at 11:20 AM ET on November 12 and lasted until 11:10 AM ET the following day. Microsoft reported that the incident stemmed from a combination of three factors: a previously undetected software bug, a surge in traffic after a Microsoft Teams failover, and a reduction in server capacity due to an unrelated issue. This cascading failure left users unable to access their emails and resulted in significant delays in message delivery, affecting businesses and organizations that rely on these services for daily operations.
Microsoft explained that the software bug was part of an update for its networking gateway servers, which had been deployed without incident for over three months. However, the bug could overwhelm the servers under specific traffic conditions, causing them to stop responding. The company indicated that its testing did not reveal the issue because it used less powerful hardware than what is typically deployed in production environments. The bug was exacerbated by the fact that Microsoft’s load testing focused on weaker hardware configurations, failing to replicate the conditions that would trigger the issue on more robust systems.
The failure was compounded when Microsoft Teams experienced a separate outage earlier that day, although it remains unclear if the two incidents are directly related. Approximately 15 hours before the major outage, Teams switched to the networking infrastructure used by Exchange Online, which significantly increased traffic on those servers. At the same time, nearly 14% of the gateway's server capacity was offline due to an unrelated problem, which the company stated was manageable under normal conditions. However, this combination of increased traffic and diminished capacity set the stage for the software bug to be triggered.
As servers began to fail, Microsoft's systems attempted to redirect users to other available servers. Unfortunately, these servers also became overwhelmed by the additional traffic, leading to a broader failure. Within two hours, the previously unknown defect affected a significant portion of the server fleet, leaving more than 80% unresponsive. Microsoft noted that safeguards designed to prevent regional problems from spreading failed, allowing the outage to escalate globally. While some services, such as Teams and OneDrive, could switch to alternative infrastructure and recover sooner, Exchange Online was unable to do so, leaving users unable to access their mailboxes during the outage.
Recovery proved challenging, as attempts to restart the affected servers quickly led to them being overwhelmed again by backed-up traffic. After identifying the bug, Microsoft engineers developed and deployed a fix across the impacted servers, allowing services to stabilize by the end of the day on November 13. Microsoft has since increased capacity, enhanced monitoring, and implemented safeguards to prevent similar cascading failures in the future. An investigation is ongoing, with a final post-incident report expected shortly.
- It is not yet known how many users were directly affected by the outage or the full extent of the impact on businesses.
- The relationship between the earlier Teams outage and the subsequent Microsoft 365 outage remains unclear.
- Details about the unrelated issue that took a portion of the server capacity offline have not been disclosed.