A combination of a hidden software defect, increased network traffic and reduced server capacity caused the global Microsoft 365 disruption on November 12, Microsoft has confirmed. The issues triggered a chain reaction across its networking infrastructure, leaving several services unavailable and making recovery difficult.
Charles Lamanna, Executive Vice President of Copilot, Agents and Platform at Microsoft, explained the causes in a post on X. He said the incident affected the networking gateway used by several Microsoft 365 services.
3 factors behind the outage
The first issue was a software defect linked to lock contention in an internal process. Under certain workloads, it caused servers to become overwhelmed and stop responding. The faulty code came from a fix developed for Microsoft 365 networking gateway servers. Its rollout began in July and continued globally over several weeks. It remained undetected for more than 3 months and was not identified during routine load testing.
The second factor was a change in network traffic. Microsoft operates 2 independent gateway systems to improve service availability. Around 15 hours before the outage, Teams moved from the alternative gateway to the primary one as part of a routine failover operation. This increased traffic on the primary gateway.
At the same time, nearly 14% of its server capacity was unavailable because of an unrelated issue from the previous day. The increased load, reduced capacity and software defect caused requests to build up until servers stopped responding.
Microsoft’s traffic management systems then redirected users to healthy endpoints. However, this placed additional pressure on the remaining servers. At the worst point, more than 80% of the gateway servers were unresponsive. The infrastructure’s isolation safeguards, designed to contain failures across thousands of capacity units and regions, also failed to prevent the disruption from spreading globally.
Why Outlook recovery took longer
Teams, OneDrive, SharePoint and Office apps were able to move away from the faulty gateway infrastructure. Exchange Online, which powers Outlook, could not use the same failover option, making mailbox recovery more difficult.
Microsoft also faced problems restarting affected servers because they were overwhelmed by accumulated requests.
After identifying the defect, engineers developed an update to restore the affected code to its previous working state. They updated servers in groups, restarted them and gradually returned them to service while monitoring stability.
Lamanna said Microsoft’s final Post-Incident Review (PIR), expected later this week, will provide further details.
Also read: Viksit Workforce for a Viksit Bharat
Do Follow: The Mainstream LinkedIn | The Mainstream Facebook | The Mainstream Youtube | The Mainstream Twitter
About us:
The Mainstream is a premier platform delivering the latest updates and informed perspectives across the technology business and cyber landscape. Built on research-driven, thought leadership and original intellectual property, The Mainstream also curates summits & conferences that convene decision makers to explore how technology reshapes industries and leadership. With a growing presence in India and globally across the Middle East, Africa, ASEAN, the USA, the UK and Australia, The Mainstream carries a vision to bring the latest happenings and insights to 8.2 billion people and to place technology at the centre of conversation for leaders navigating the future.


