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

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


Microsoft has traced the worldwide Microsoft 365 outage on November 12–13, 2026, to a hidden Windows defect that overwhelmed servers handling cloud connections.

Its preliminary incident report, dated November 15, describes how a software change, shifted traffic, and reduced server capacity combined to cause widespread failures. Exchange Online suffered the greatest impact.

The disruption lasted from 4:20 PM UTC on November 12 until 4:10 PM UTC on November 13. Most users could not reach Exchange Online mailboxes through Outlook or other clients, while many faced delayed emails

As covered in Cybersecuritynews.com’s initial Microsoft 365 outage report, the incident also affected other Microsoft cloud services.

Hidden Windows Bug Triggered Failures

The defect came from a fix prepared specifically for Microsoft 365 networking gateway servers. Deployment began in July, and the change ran globally for more than three months without visible problems. Microsoft says neither the defect nor that fix applies to general Windows deployments, separating this incident from a Windows desktop issue.

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.

Connection requests piled up until servers stopped responding. Microsoft’s tests missed the issue because they focused on weaker machines, while the fault became worse on newer hardware with more cores.

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 because of an unrelated issue. Microsoft says the remaining capacity was sufficient on its own, but the combined conditions triggered the defect.

Automatic Recovery Made Things Worse

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. Microsoft-hosted incident discussions also recorded unavailable servers placing extra load on remaining infrastructure.

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, matching Cybersecuritynews.com’s coverage of unsuccessful recovery efforts. Teams, SharePoint, and OneDrive could move eligible traffic away, but Exchange Online could not fully switch paths at its operating scale.

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 so queued messages would not be returned as undeliverable.

The report remains preliminary, with repair details due November 20. For administrators, incidents EX1550543 and MO1550821 identify the disruption in service health records. Microsoft’s published guidance said tenant or device configuration changes were unnecessary. The failure was within Microsoft’s cloud infrastructure, not customer Windows systems.

Give your SOC the alert context to stops incidents quickly. Integrate Threat Intel from 16K SOCs.

The post Microsoft Reveals How a Hidden Windows Bug Took Down Microsoft 365 Services Worldwide appeared first on Cyber Security News.