New Delhi, November 16, 2026 (Yes Punjab News)
Microsoft has attributed its recent global Microsoft 365 outage to three factors: a hidden software flaw, an unusually high volume of traffic and reduced server capacity. At the peak of the disruption, more than 80 per cent of the affected servers stopped responding, the company said on Monday.
The outage on November 12 disrupted several services, including Teams, OneDrive, SharePoint and Office applications.
In a post on X, Microsoft’s Executive Vice President for Copilot, Agents and Platform apologised to customers and shared the initial findings of the investigation.
According to the company, the disruption originated in a networking system that sits in front of several Microsoft 365 services. A hidden software flaw caused servers to become overloaded and stop responding under certain conditions.
The code change associated with the flaw had first been rolled out in July and had been operating globally for more than three months without problems. Microsoft said the defect went undetected because its testing systems used traffic patterns and hardware configurations different from those in real-world operations.
The situation worsened after Teams traffic was shifted from a backup system to the main system around 15 hours before the outage, resulting in a sharp increase in traffic. At the same time, nearly 14 per cent of server capacity was unavailable because of an unrelated issue from the previous day.
Microsoft said neither factor alone would have caused the outage. However, their combination exposed the software flaw, leading to a build-up of requests until servers stopped responding during peak traffic hours in the US.
The company’s automated systems initially attempted to redirect users to healthy servers, but the additional traffic increased the likelihood of similar failures spreading to other parts of the network.
A separate issue also prevented Microsoft’s internal safety systems, designed to contain failures within individual regions, from functioning properly. This allowed the disruption to spread globally.
Recovery proved difficult because servers returning online were immediately hit by accumulated traffic and stopped responding again. Microsoft’s existing automated recovery systems were not designed to handle a failure of this scale.
Engineers eventually identified the faulty code and developed an update that restored normal operations.
Microsoft said it would publish a detailed review of the incident, including further findings and corrective measures, later this week.



























