Skip to main content
Microsoft Reveals How a Hidden Windows Bug Took Down Microsoft 365 Services Worldwide - CyberSecurityNews

Microsoft Reveals How a Hidden Windows Bug Took Down Microsoft 365 Services Worldwide - CyberSecurityNews

Infosec News
16 lis 2026, 16:02Google News Cybersec
Oryginał
2 min read

Microsoft has traced the worldwide Microsoft 365 outage on November 12-13 to a hidden Windows bug that overwhelmed servers handling cloud connections.

The company's preliminary incident report, dated November 15, describes how a software change shifted traffic and reduced server capacity, which combined to cause widespread failures. Exchange Online suffered the greatest impact during the disruption that lasted from 4:20 PM UTC on November 12 until 4:10 PM UTC on November 13.

Most users could not access Exchange Online mailboxes through Outlook or other clients, while many experienced delayed emails. The incident also affected other Microsoft cloud services including Teams, SharePoint, and OneDrive.

Root Cause Identified

The defect originated from a fix prepared specifically for Microsoft 365 networking gateway servers. Deployment began in July and ran globally for over three months without visible problems. Microsoft clarified that neither the defect nor the fix applies to general Windows deployments.

Inside an internal Windows process, competing tasks were waiting for access to shared resources—a problem called lock contention. Under certain traffic conditions, this exhausted processor and memory capacity. Microsoft's tests missed the issue because they focused on weaker machines, while the fault manifested on newer hardware with more cores.

Cascading Failure

Two conditions exposed the bug. Around fifteen hours before the outage, Teams traffic moved from an alternative gateway to the primary gateway shared with Exchange Online. Meanwhile, nearly 14% of gateway server capacity was unavailable due to an unrelated issue.

When servers failed, automated systems moved connections to healthy endpoints. That extra work triggered the same fault elsewhere, spreading failures across regions in less than two hours.

More than 80% of servers became unresponsive at the worst point. A separate failure in the boundaries designed to contain faults allowed the outage to spread globally. Restarted servers quickly failed again when waiting traffic returned.

Recovery and Next Steps

Engineers developed an update that returned Windows connection handling to its earlier working state. They removed large server groups from service, applied the change, restarted them, and restored traffic gradually. Microsoft also added capacity and extended the email delivery window.

The report remains preliminary, with repair details due November 20. For administrators, incidents EX1550543 and MO1550821 identify the disruption in service health records. Microsoft confirmed the failure was within their cloud infrastructure, not customer Windows systems.

Z.ai
Article written by AI
Z.ai GLM-4.5-FlashFree
Free AI articles150 of 150
No limit after signing in with Telegram