AEGLIX News
According to Microsoft's post-incident analysis, a software bug introduced in July triggered a cascading failure that left over 80% of networking gateway servers unresponsive, causing last week's global Microsoft 365 outage. The nearly 24-hour disruption started at 11:20 AM ET on Thursday, November 12, and persisted until 11:10 AM ET the next day, when the company confirmed full service restoration. Earlier that same day, Microsoft Teams suffered a separate outage, though any connection between the two incidents remains undetermined.
The November 12 outage affected Microsoft 365 services globally, including Outlook, Exchange Online, Teams, and Copilot, preventing email access and causing major message delivery delays. Microsoft pinpointed three root causes: a previously unknown software bug, a surge in traffic following a Microsoft Teams failover, and diminished server capacity. The bug originated in a July update for Microsoft 365 networking gateway servers and had been deployed for over three months without incident before activating under specific traffic conditions.
Approximately 15 hours before the outage, Microsoft Teams automatically switched to the networking infrastructure used by Exchange Online, increasing traffic on those servers and triggering the bug. Safeguards meant to stop problems from spreading across regions failed to contain the cascading outages, allowing the disruption to go worldwide. Unlike Teams, OneDrive, and SharePoint, Exchange Online could not switch to alternative infrastructure, leaving users unable to reach their mailboxes.
Microsoft developed a fix and deployed it across affected servers, and confirmed active customer impact ended by 11:10 AM ET on November 13.
Report prepared 2026-11-16 · Based on reporting from BleepingComputer. Source publication date above; subsequent developments may not be reflected.
Sources
Read original source · BleepingComputer (opens in a new tab)