Three failures combined to trigger Microsoft 365 outage

A software defect, a Teams traffic surge and reduced server capacity converged to bring Microsoft 365 offline for about 24 hours across two business days, Microsoft said. The company described the combination as a “perfect storm” and said none of the three issues alone would have caused an outage of that scale.

Today, 21:30
81 0
Three failures combined to trigger Microsoft 365 outage

Microsoft Executive Vice President of Copilot, Agents, and Platform Charles Lamanna said a “latent defect” made networking gateway servers unresponsive under certain load conditions. The defect entered Microsoft’s systems in a July 2026 update intended to fix the gateway servers. It went undetected for months and did not cause problems under normal loads during testing, Lamanna said.

The defect was activated after Microsoft Teams failed over from an alternative network gateway to the primary gateway, which supports Exchange Online. That switch happened 15 hours before the outage and increased traffic on the primary system, according to Lamanna.

At the same time, nearly 14 percent of the networking gateway’s server capacity was unavailable because of an unrelated issue from the previous day. Microsoft said the remaining capacity would normally have been enough to keep the service running. Together, the added load and reduced capacity triggered the defect during peak U.S. traffic, causing requests to build up until servers stopped responding.

Recovery took longer because waiting traffic overwhelmed servers as they came back online. Microsoft could not simply roll back the code, since the defect had been introduced in July, and instead had to develop a patch to restore the code to its previous “good state.” The company has apologized. Affected businesses can file claims for credits, and enterprise customers can find more information in the Microsoft 365 Admin Center.

Share

Comments (0)

Leave a comment

No comments yet. Be the first!