Microsoft Official Reveals Cause of Massive Outage

By Jack Phillips
Jack Phillips
Jack Phillips
Breaking News Reporter
Jack Phillips is a breaking news reporter who covers a range of topics, including politics, U.S., and health news. A father of two, Jack grew up in California's Central Valley. Follow him on X: https://twitter.com/jackphillips5
November 18, 2026Updated: November 18, 2026

A Microsoft official has provided more details on why its 365 and Outlook suites were down for more than 24 hours last week, coming in the midst of fears about cyberattacks against U.S. government agencies, banks, and infrastructure.

Charles Lamanna, the executive vice president of Microsoft’s Copilot, Agents and Platform, said in an X post on Nov. 16 that “a latent defect caused servers to become overwhelmed and unresponsive under certain load conditions,” leading to the outage that started on Nov. 12.

“This was due to lock contention inside an internal process which caused the machine to become unavailable,” he stated in a lengthy post. “This defect was the result of a fix that was prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments.”

An initial change in the system’s behavior occurred during the fix’s deployment in July, he said, adding that an update was sent out over a several-week period in which no problems were observed.

“For more than three months,” Lamanna wrote, “the change was deployed worldwide without impact.”

Microsoft said on Nov. 14 that its services were fully restored after users reported outages with Outlook, Teams, and the AI assistant Copilot. The outage impacted court systems, healthcare systems, airlines, and a number of businesses.

Another issue Lamanna highlighted in the post was that around 15 hours before the 365 outage, the system supporting Microsoft’s Teams service experienced problems and automatically rerouted traffic to the system that also supports Outlook, putting a strain on that system.

“Third, at the same time, nearly 14 percent of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day,” he added. “This server capacity was on track to be returned to active service through routine maintenance and health processes. The service had sufficient capacity headroom, so the reduction in server capacity had no impact on its own.”

With those three problems combined, it increased the load on Microsoft’s servers. This caused its network gateway, a hardware device or software application that acts as an exit or entry point between networks, to be affected by the bug seen in July.

“This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States,”Lamanna said.

The reason why recovery took longer than expected was due to Microsoft’s servers being “immediately overwhelmed by waiting traffic,” causing them to become unresponsive, he wrote.

“Our normally automated recovery processes were not designed to restore service from this broad unresponsive state,” he stated. “Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change.”

The outage occurred before several other heavily used services went down, including an airport communications system operated by the Federal Aviation Administration, multiple major U.S. banks, an internal National Security Agency system, and more in recent days. Apple products had sign-in issues on Nov. 10.

On Nov. 18, Jay Clayton, the Trump administration’s director of national intelligence, told lawmakers in a congressional hearing that the outages were not due to cyberattacks.

“Based on what we know today, after a great deal of diligence, these are separate service outages associated with maintenance and technical changes. They are not a coordinated or state-sponsored attack,” Clayton said at a House Homeland Security Committee hearing on Wednesday morning.

It came as Google, the FBI, and the U.S. Cybersecurity and Infrastructure Security Agency (CISA) have issued warnings on AI-driven attacks and related security risks in recent days.