Outlook, Teams, and Microsoft 365 customers experienced a long-lasting outage last week, spanning both Thursday and Friday, leaving millions around the world without access to email and causing business systems to struggle. Outages are typically a few hours long, but last week’s was notable for its length and the breadth of systems taken offline.
Microsoft’s executive for Copilot, Agents, and Platform, Charles Lamanna, shared the first stage of its breakdown of the incident in a post on X. He said it was due to “three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services.”
The first factor stemmed from a defect introduced in July as part of a fix for Microsoft 365 networking gateway servers. Microsoft says the software, including this hidden defect, was “saturated globally over several weeks” without any impact.
“Our normal load testing did not detect the latent issue because [of] the different traffic and SKU mix used in our test labs,” says Lamanna. He explains that the issue is “worsened on machines with more cores and newer hardware” while Microsoft’s own load testing focuses on “weaker hardware SKUs with fewer cores.”
This Tweet is currently unavailable. It might be loading or has been removed.
The second factor was a surge in load on its networking gateways, linked to a minor issue with Microsoft Teams on Wednesday, Nov. 11. That problem prompted Teams to switch to an alternative networking gateway, increasing load and changing overall traffic patterns. Lamanna said, “This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts”
The third factor is what Lamanna calls an “unrelated issue from the previous day,” in which 14% of Microsoft’s server capacity for its networking gateway was left out of service. The second and third factors combined meant that the networking gateway encountered the defect first introduced in July.
This led to a buildup of requests and ultimately causing servers to stop responding, all during what Microsoft calls the “peak window of traffic in the United States.” Microsoft’s automated systems then rerouted requests, which led to the defect recurring across its network and eventually affecting more than 80% of its servers.
Recommended by Our Editors
“Our normally automated recovery processes were not designed to restore service from this broad unresponsive state,” Lamanna said.
To solve the problems, engineers developed a fix and took each server offline to apply it. Engineers then carefully reactivated each server, resulting in long wait times and therefore a lack of service for Microsoft customers.
The thread says Microsoft plans to share a full post-incident review later this week, although an exact timeframe isn’t yet available. Lamanna said, “We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations.”
About Our Expert

Experience
I’ve been a journalist for over a decade after getting my start in tech reporting back in 2013. I joined PCMag in 2025, where I cover the latest developments across the tech sphere, writing about the gadgets and services you use every day. Be sure to send me any tips you think PCMag would be interested in.

Leave a Reply