LIVE

Microsoft Traces Global 365 Outage to Dormant July Code Defect

🏢 Big Tech 2 min read 👁 10

Microsoft revealed that a latent software bug deployed in July caused the recent global Microsoft 365 outage, which was triggered by a combination of high traffic load and reduced server capacity.

Microsoft Traces Global 365 Outage to Dormant July Code Defect🏢Big Tech

Photo: thenextweb.com

Key points

  • July update defect caused lock contention in internal Windows processes
  • Standard load testing missed the bug because it was run on weaker hardware
  • Over 80 percent of affected servers became unresponsive at the peak of the outage

Microsoft has traced a major global disruption affecting Microsoft 365 services to a network gateway server update introduced back in July. According to a preliminary post-incident report shared by the company, a hidden code defect remained dormant for over three months before high traffic volume and reduced server capacity caused it to fail.

Executive Vice President Charles Lamanna explained that the July update created lock contention within an internal Windows process under specific load conditions, completely exhausting server CPU and memory. Pre-release testing failed to catch the issue because trials utilized weaker hardware with fewer cores, whereas the flaw manifested more severely on newer, multi-core machines.

The situation escalated when traffic failed over to gateways supporting Exchange Online, compounding a prior capacity drop that had removed nearly 14 percent of the system's servers from service. As individual servers crashed, traffic shifted to remaining healthy units, which quickly succumbed to the same bug and left over 80 percent of servers unresponsive at its peak.

More than 1,000 engineers and staff participated in emergency remediation calls led by Lamanna and cloud chief Scott Guthrie. Microsoft confirmed the incident was unrelated to any cyberattack or artificial intelligence agents, issuing an apology to affected customers, governments, and businesses spanning 74 countries and territories.

What to watch next: Microsoft has stated it will publish its final, comprehensive post-incident report on November 20.

Source thenextweb.com — thenextweb.com/news/microsoft-365-outage-july-defect-post-incident-repo… ↗

Contact the newsroom

Got a tip, a proposal or a partnership question? Write to us and we will reply shortly.