Microsoft revealed that a software bug introduced in July caused the nearly 24-hour global outage that crippled Microsoft 365 services on November 12 and 13. The disruption began at 11:20 AM ET (4:20 PM UTC) on November 12 and lasted until 11:10 AM ET (4:10 PM UTC) the following day, cutting off access to Outlook, Exchange Online, Teams, and Copilot. [1][2]
According to Microsoft's preliminary post-incident report, the flaw resided in an update for networking gateway servers. It went unnoticed during testing because lab evaluations focused on weaker hardware with fewer cores, whereas the bug worsened on newer machines with more cores. The issue was triggered after Microsoft Teams shifted traffic to Exchange Online's infrastructure roughly 15 hours before the incident, while nearly 14% of gateway capacity was already offline due to an unrelated problem. This surge sparked a cascading failure, leaving more than 80% of servers unresponsive within two hours as automatic traffic rerouting overwhelmed surviving nodes. [1]
Microsoft stabilized operations after deploying a software fix, and the company stated that it has since expanded server capacity, upgraded monitoring, and added protections to prevent similar cascading failures. [1]