Microsoft executive Charles Lamanna breaks down and identifies all of the key reasons behind the recent global outage.

Charles Lamanna took the time to explain the Microsoft 365 global outage that occurred on November 12, 2026. Through an X post, the executive vice president of Copilot, Agents, and Platform apologized to customers and said:
“We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations. The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services.”
Lamanna oversees Office, Teams, SharePoint, and Copilot and reports to CEO Satya Nadella. He previously ran Power Platform and Dynamics 365 after Microsoft bought his startup, MetricsHub. In his lengthy explanation, Lamanna specified the three key reasons behind the outage as a latent defect, extra load, and lost server capacity.
Read More: “No Point in Rushing It”: Internet Reacts as IShowSpeed Announces He Won’t Be Doing a Marathon Stream for GTA 6 Because He Doesn’t Want to Rush Through the Game
Charles Lamanna Explains the Root Causes and Key Lessons From the Microsoft 365 Global Outage
The first factor was a latent defect from July. Lock contention inside an internal process left servers unable to respond under certain loads. The fix was built only for Microsoft 365 gateway servers, not broader Windows deployments. The change ran worldwide for more than three months without impact. The second factor was a surge in load. About 15 hours before the outage, Teams failed over to the primary gateway. That system also handles Exchange Online traffic. The switch raised load and changed traffic patterns.
Lastly, Lamanna mentioned the third reason was lost capacity. Nearly 14% of gateway server capacity was offline after an unrelated issue. Alone, it caused no problem, because capacity headroom remained. Together, the extra load and lost capacity triggered the July bug. Requests piled up until servers stopped responding during the U.S. peak traffic window. Rerouted traffic then overwhelmed healthy endpoints across the fleet. Within two hours, more than 80% of servers were unresponsive.
The disruption spanned two workdays, with services recovering gradually. Restarted servers were swamped by waiting traffic and failed. Months-old code also defeated normal rollback and feature flag tools, exposing a recovery gap. Online claims of a cyberattack gained traction before Microsoft ruled one out. Lamanna also apologized for the inconvenience and said a final Post-Incident Review will follow later this week.
Also Read: “How They Have Spent the Billions of Dollars Already Authorized”: Buttigieg Says Trump Govt Owes Americans “An Honest Accounting”

I’m Abhishek Sharma, an author at TigerJek.com. I enjoy exploring games, testing different strategies, and turning what I learn into clear, useful guides. My goal is to help players understand the game better and improve without the usual confusion.




