Business

Microsoft Blames Software Flaw, Traffic Surge and Reduced Capacity for Global Microsoft 365 Outage

NEW DELHI–Microsoft has identified three major factors behind its November 12 global Microsoft 365 outage, revealing that a previously undetected software defect, a sudden increase in network traffic and reduced server capacity combined to disrupt services worldwide.

The outage affected several widely used Microsoft 365 applications, including Teams, OneDrive, SharePoint and Office, interrupting access for businesses and individual users.

In a statement posted on X on Monday, Microsoft’s Executive Vice President for Copilot, Agents and Platform apologized to customers and shared preliminary findings from the company’s investigation.

According to Microsoft, the disruption originated in a networking system responsible for directing traffic to several Microsoft 365 services.

An underlying software defect caused servers to become overloaded and stop responding when certain conditions occurred simultaneously.

The problematic code had been deployed in July and operated across Microsoft’s global infrastructure for more than three months without triggering a major incident.

Microsoft said the flaw escaped detection because its testing environments used different hardware configurations and traffic patterns than those encountered in production systems.

The situation deteriorated when Microsoft transferred Teams traffic from a backup system to its primary infrastructure approximately 15 hours before the outage.

That transition significantly increased the volume of requests handled by the affected networking system.

At the same time, an unrelated technical problem from the previous day had left nearly 14% of server capacity unavailable.

Microsoft said neither the increased traffic nor the reduced capacity would have independently caused the disruption. However, the combination exposed the dormant software flaw.

As demand increased during peak usage hours in the United States, requests began accumulating faster than the affected servers could process them, eventually causing the systems to stop responding.

Microsoft’s automated recovery mechanisms initially attempted to redirect traffic away from failing servers and toward healthy infrastructure.

However, the additional traffic placed more pressure on operational servers, increasing the likelihood that they would encounter the same software defect.

The result was a cascading failure that rapidly spread throughout the network.

At the height of the disruption, more than 80% of servers within the affected infrastructure had stopped responding, according to the company.

Microsoft also identified a separate problem involving internal safeguards designed to prevent technical failures from spreading between geographic regions.

Those protections failed to operate as intended, allowing what might otherwise have remained a localized incident to develop into a global outage.

Restoring service proved particularly challenging because servers that restarted were immediately overwhelmed by accumulated requests and failed again.

The company acknowledged that its existing automated recovery systems were not designed to manage an infrastructure failure of this magnitude.

Engineers eventually isolated the defective code and developed a software update that allowed the affected systems to recover.

Microsoft said the investigation remains ongoing and that it plans to publish a comprehensive review later this week detailing the technical causes, lessons learned and corrective measures intended to prevent similar disruptions.

The incident highlighted the potential consequences of interconnected cloud infrastructure failures, particularly when multiple technical issues occur simultaneously across services used by businesses worldwide. (Source: IANS)

Related Articles

Back to top button
Close

Adblock Detected

Please consider supporting us by disabling your ad blocker