Microsoft blames its Microsoft 365 outage on a dormant July update defect

What happened
When Teams traffic surged and capacity dropped, the Microsoft 365 outage spread server to server. Microsoft has traced last week’s global Microsoft 365 outage to a July update for its network gateway servers. Microsoft is a software and software development company based in Redmond, and its products and services include Microsoft Windows and Microsoft Servers.
The bug lay dormant for more than three months before a surge in load and a drop in capacity set it off, according to the company’s preliminary post-incident report. Microsoft’s preliminary report says its load tests ran on weaker hardware, so a lock contention bug went unseen.
Microsoft published the report to customers in the Microsoft 365 admin centre on 15 November, The Register reported .
Charles Lamanna, Microsoft’s executive vice president for Copilot, agents and platform, posted an abridged version on X on Monday, ZDNET reported . “A latent defect caused servers to become overwhelmed and unresponsive under certain load conditions,” Lamanna wrote.
Three things at once The July update was built specifically for the Microsoft 365 network gateway servers. It passed load testing and ran worldwide without problems, Microsoft said.
But the defect caused lock contention inside an internal Windows process, which exhausted a server’s CPU (the general-purpose processor at the centre of a computer) and memory. Testing missed it, because the load tests focused on weaker hardware with fewer cores, according to the report.