What caused the outage
According to Microsoft, the first cause was a latent defect introduced during a July 2026 update to Microsoft 365 networking gateway servers. The defect made servers become overwhelmed and unresponsive under certain load conditions, but it went undetected for months because it did not cause problems under normal load during testing.
The second cause was a surge in server traffic. Microsoft maintains two independent network gateway systems for Microsoft 365. Fifteen hours before the outage, Teams failed over from the alternative networking gateway to the primary one, which supports Exchange Online. That switch set off the latent defect.
The third cause was reduced server capacity. Nearly 14 percent of the server capacity for the networking gateway was out of service due to an unrelated issue from the previous day.
Taken together, the increased load and reduced server capacity caused the network gateway to encounter the latent bug. Requests built up until servers stopped responding, during the peak window of traffic in the United States.