Submission + - Microsoft 365 Outage Caused By Windows Server Bug Introduced In July (wccftech.com)
Under certain workloads, an internal Windows process experienced lock contention, exhausting CPU and memory resources and eventually rendering servers unresponsive. The defect remained dormant for more than three months, escaping Microsoft's testing because its laboratories primarily used less powerful hardware with fewer CPU cores, where the issue was less likely to emerge.
The second contributing factor involved Microsoft Teams. Approximately 15 hours before the outage, Teams traffic was automatically redirected from an alternative networking gateway to the primary gateway shared with Exchange Online. Although such failovers are routine, this increased the workload on the affected infrastructure.
Finally, approximately 14% of the networking gateway's server capacity was already unavailable due to an unrelated issue from the previous day.
The combination proved disastrous.