Microsoft Blames Monster Email Outage On Software Defect Introduced In July Fix
Microsoft says last week's massive Microsoft 365 outage was caused by a software defect introduced in a July update that remained dormant until a Teams failover and a simultaneous 14% reduction in gateway capacity triggered a cascading failure. More than 80% of the affected gateway servers became unresponsive at the outage's worst point, and because the months-old change could not simply be…
Microsoft claims that a recent massive email outage in Microsoft 365 was due to a software defect introduced in a July update. The issue remained dormant until a Teams failover and a 14% reduction in gateway capacity triggered a cascading failure. Over 80% of the affected gateway servers became unresponsive at the worst point, and since the defect could not be simply rolled back, engineers spent around 15 hours developing and deploying a patch to restore the previous code path.
According to Microsoft's preliminary post-incident report, the defect was introduced in July 2026, but the load testing during the update focused on weaker hardware with fewer cores, missing potential issues. The defect caused lock contention inside an internal Windows process, exhausting the machine's resources (CPU & memory). The issue worsened on machines with more cores and newer hardware.
The patch was specifically prepared for Microsoft 365 network gateway servers, and the failure occurred when Teams failed over to the primary gateway supporting Exchange Online, and 14% of server capacity was out of service. This pushed the gateway into the defect, causing a cascading failure scenario where traffic was repeatedly rerouted and overwhelmed the servers.
Written by urgent.news from Slashdot's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.