- Microsoft's July software defect caused a global outage on November 12 for Microsoft 365 services.
- The defect led to server unresponsiveness due to lock contention under specific load conditions.
- A failover to the primary gateway and reduced server capacity increased load and traffic strain.
Microsoft has said a software defect rolled out in July, combined with a spike in traffic and reduced server capacity, caused the global outage that hit Outlook and other Microsoft 365 services on November 12.
Charles Lamanna, executive vice president of Copilot, Agents and Platform at Microsoft, laid out the cause in a post on X. He said the three problems together brought down the networking gateway that sits in front of several Microsoft 365 services.
According to Microsoft, the defect caused servers to become unresponsive under certain load conditions, due to lock contention in an internal process. It was part of a fix for the company's Microsoft 365 networking gateway servers, which began rolling out in July and was deployed worldwide over several weeks. The company said the flaw caused no noticeable problems for more than three months and was not caught during routine load testing.
Also Read | Layoffs Are Rising In Tech, But These Skills Are Helping People Unlock Better Pay
ALSO READ | Microsoft 365 Users Targeted By Fake Outage Notifications In Phishing Campaign
Microsoft said it runs two independent gateway systems to limit disruptions. About 15 hours before the outage, Teams moved from the alternative gateway to the primary one as part of regular failover operations. This raised the load on the primary gateway and changed its traffic patterns.
At the same time, roughly 14 percent of the gateway's server capacity was unavailable because of an unrelated issue from the previous day, the company said.
Requests then began to build up on the affected servers until they stopped responding. Microsoft said its traffic management systems redirected users to other servers, which added to the strain. At the height of the outage, more than 80 percent of the gateway servers were unresponsive.
More details on the root cause can be found in the Microsoft 365 Admin center, and an abridged version can be found below. We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations. The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services. First, a latent defect caused servers to become overwhelmed and unresponsive under certain load conditions. This was due to lock contention inside an internal process which caused the machine to become unavailable. This defect was the result of a fix that was prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments. The initial change in behavior first started deployment in July of this year. The update went through safe deployment and saturated globally over several weeks, during which time no issues were observed. For more than three months, the change was deployed worldwide without impact. Our normal load testing did not detect the latent issue because the different traffic and SKU mix used in our test labs. The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on our weaker hardware SKUs with fewer cores. Second, a surge in load increased the likelihood for the networking gateways to encounter the contention. Within Microsoft 365, we maintain two independent and heterogenous network gateway systems designed for isolation and high availability. This allows many Microsoft 365 services to fail to/from them during outages or disruptions. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary' gateway that also supports Exchange Online. This increased the load on the networking gateway and changed its traffic patterns. This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts. Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day. This server capacity was on track to be returned to active service through routine maintenance and health processes. The service had sufficient capacity headroom, so the reduction in server capacity had no impact on its own. Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States. When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints. This happens often and is critical to avoiding any interruption due to hardware, software, or network defects and is normally what makes the service resilient. However, the redirected traffic increased the likelihood for the same problem to occur on the remaining endpoints. This caused a cascading failure from server to server as the same amount of load was spread across fewer servers. In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive. Normally, the network gateway is composed of thousands of ‘capacity units' which represent shards of capacity, hardware, and networking infrastructure. These ‘capacity units' are then organized into regions. In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure. This is what allowed the impact to spread across our network gateway infrastructure globally. Several services like Teams, OneDrive, SharePoint, and Office apps failed out of the faulty network gateway infrastructure. That is why those services were restored earlier, with Teams chats and meetings functioning without issue for most of the outage. But not all services, like Exchange Online, can fail out of this network gateway. Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again. Our normally automated recovery processes were not designed to restore service from this broad unresponsive state. Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change. After engineers confirmed the defect as the cause, we developed an update that returned the code path to the previously known good state. To effectively apply this fix, and to slowly bring the service online again, we took groups of servers out of service, applied the change, and restarted them before returning them to service. This process was carefully applied to large quantities of infrastructure at a time (e.g. 50%+ of a region). The final Post-Incident Review (PIR) will provide more details later this week.
— Charles Lamanna (@clamanna) November 16, 2026
ALSO READ | Microsoft Outage: Services Partly Restored As Microsoft Restarts Affected Infrastructure
The gateway is divided into thousands of capacity units organised by region to keep failures contained. Microsoft said a separate issue stopped those safeguards from working, allowing the problem to spread globally.
Outlook Slowest To Recover
Teams, OneDrive, SharePoint and Office apps were able to switch away from the failing gateway. Exchange Online, which powers Outlook email, could not, Microsoft said, which made restoring mailboxes harder. Servers that were brought back were also overwhelmed by queued requests and went down again.
Fix Rolled Out In Stages
Once the defect was identified, engineers returned the affected code to its earlier working state. Microsoft said it took servers out of service in groups, applied the update, restarted them and returned them gradually while monitoring stability.
Lamanna said the company's final post-incident review, with further details, is expected later this week.
ALSO READ | Microsoft Outage Disrupts Outlook, Teams, Copilot: Seven Things You Should Do Right Now
Essential Business Intelligence, Sharp Market Insights, Practical Personal Finance Advice, Daily Fuel, Gold and Silver Prices and Latest Stories — On NDTV Profit.