Microsoft 365 Global Outage: 3 Things That Went Wrong And Left Services Unresponsive (AI-generated) Microsoft has offered a detailed explanation of what had gone wrong with its latest outage last week that disrupted services including Teams, OneDrive, Outlook and SharePoint. The tech giant has revealed that a combination of a software defect, a sudden increase in network traffic and reduced server capacity, had caused the outage. These factors came together to trigger a massive outage. Charles Lamanna, Executive Vice President of Copilot, Agents and Platform at Microsoft, has shared a detailed explanation of the incident. He took to X and said that a previously undetected software system combined with changes in network traffic and reduced server availability, caused Microsoft's networking gateways to become unresponsive. The massive global outage had taken place on November 12, 2026, during peak hours in the United States and India. Lamanna has mentioned three reasons for the outage. He said, “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.” Secondly, he mentioned that a surge in load increased the likelihood for the networking gateways. He added, “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.” Lamanna concluded that nearly 14 per cent of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day. He said, “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.” He added, “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.” Notably, Microsoft has also apologised to customers who faced outage during their business hours. Lamanna said, “We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations." Govind Choudhary is the Chief Copy Editor for Tech at Times Now with over five years of experience in the media industry. He covers consumer technolog... View More