4-Month Old Software Bug Crashed Microsoft Teams, Outlook For Millions Of Users


Mohul Ghosh

Mohul Ghosh

Nov 17, 2026


Microsoft has identified a software bug introduced in July 2026 as the underlying cause of its global outage on November 12 and 13, which disrupted Outlook, Exchange Online, Teams and several other Microsoft 365 services.

4-Month Old Software Bug Crashed Microsoft Teams, Outlook For Millions Of Users

In a preliminary incident report released on November 16, the company explained how three separate technical problems combined to overwhelm its networking infrastructure, leaving servers unresponsive and disrupting services used by millions of people worldwide.

The outage lasted approximately 24 hours and affected businesses, government departments, hospitals, schools and other essential services across multiple countries.

A Software Bug That Remained Undetected for Four Months

According to Charles Lamanna, Microsoft’s Executive Vice President of Copilot, Agents and Platform, the primary problem was a latent software defect introduced through a code change deployed in July.

The bug affected Microsoft’s networking gateway servers, which manage connections between internal systems and Microsoft 365 services.

Although the change had been deployed globally over several months, it did not cause noticeable problems until November.

Microsoft said its testing processes had failed to identify the defect because the conditions that triggered it were not adequately reproduced during testing.

When exposed to particular traffic patterns, the affected servers became overwhelmed and stopped responding.

Three Technical Problems Combined to Trigger the Outage

Microsoft identified three factors that collectively caused the disruption.

First, the dormant software bug made networking gateway servers vulnerable to becoming unresponsive under certain operating conditions.

Second, a routine network failover shifted Microsoft Teams traffic from an alternative gateway to the primary gateway approximately 15 hours before the outage. This increased the load on the primary system, which also supported Exchange Online.

Third, nearly 14% of the gateway server capacity was already unavailable because of an unrelated issue from the previous day.

Individually, none of these problems was expected to cause a widespread disruption. However, their combination exposed the software defect and overwhelmed the remaining infrastructure.

Microsoft said requests began accumulating faster than the servers could process them, eventually causing widespread failures.

Why Microsoft Took Nearly 24 Hours to Restore Services

The recovery process proved more complicated than initially expected.

When engineers restarted affected servers, they were immediately overwhelmed by the backlog of waiting requests and became unresponsive again.

More than 80% of the affected networking gateway servers were reportedly unresponsive at the worst point of the incident.

Microsoft’s automated recovery mechanisms were not designed to handle such a widespread failure. The company also could not simply roll back the software change because the underlying defect had existed for several months.

Engineers therefore had to apply targeted fixes, restore server capacity and gradually redirect traffic to functioning infrastructure.

Hospitals, Schools and Government Services Also Affected

The outage demonstrated how heavily organisations depend on Microsoft’s cloud services for everyday operations.

Hospitals in the UK reportedly switched to paper records, while some schools lost access to communication systems used to contact parents. Police departments and government agencies also reported disruptions.

In India, airlines IndiGo and Akasa Air reported problems with their email support services.

Microsoft eventually confirmed that services had been restored to affected customers and regions by November 14.

Microsoft Promises a Detailed Investigation Report

Microsoft has apologised for the disruption and confirmed that the incident was not caused by a cyberattack or artificial intelligence agents.

The company is expected to publish a final incident report with additional technical details and corrective measures.

The outage has renewed concerns about the concentration of critical digital infrastructure among a small number of technology companies. For businesses and public institutions, it also highlights the importance of backup systems and alternative communication channels when cloud services become unavailable.

Summary

Microsoft has traced its November 12-13 global outage to a software bug introduced in July 2026. A network traffic shift and nearly 14% reduction in available server capacity combined to trigger the failure, leaving more than 80% of affected gateway servers unresponsive. The disruption affected Outlook, Teams and other Microsoft 365 services worldwide before recovery was completed on November 14.


Mohul Ghosh
Mohul Ghosh
  • 7181 Posts

Subscribe Now!

Get latest news and views related to startups, tech and business

You Might Also Like

Recent Posts

Related Videos

   

Subscribe Now!

Get latest news and views related to startups, tech and business

who's online