Field report NE-56 / J1 · sheet /operations

Operations & RestructuringFiled from the territory

Microsoft pins global outage to July bug after three-day disruption

Microsoft linked a three-day, 70-country outage to a July defect, amplified by a traffic surge 15 hours earlier and 14% depleted capacity, with losses up to $700 million.

Grid
NE-56 / J1
Surveyed
November 16, 2026
Reading
2 min read
Correspondent
Amara Osei
Microsoft explains ‘root cause’ of global outage four days after fiasco
Fig. NE-56 / J1Microsoft explains ‘root cause’ of global outage four days after fiasco — Bru-nO / pixabay

Field notes

  1. The Thursday-to-Saturday outage lasted three days and ranked among the longest in Microsoft history.
  2. More than 70 countries were affected, with estimated losses of up to $700 million.
  3. Outlook and Teams, used by more than 400 million people, were among the affected platforms.
  4. Traffic load rose roughly 15 hours before the outage, while server capacity was nearly 14% depleted.
  5. Microsoft traced the failure to a July latent defect that the company believed had been resolved.

Microsoft's global outage lasted from Thursday through Saturday, affected more than 70 countries and generated estimated losses of up to $700 million, according to analysts cited by Business Chief.

Charles Lamanna, Microsoft's executive vice president of Copilot, Agents and Platform, said on Monday that the company had identified the root cause. Lamanna cited a July latent bug (an underlying software defect) that Microsoft had found and believed it had resolved.

“Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July,” Lamanna said. “This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States.”

What compounded the July defect?

Lamanna identified two technical server issues that left the system vulnerable to the defect but did not specify their nature. Microsoft had begun experiencing technical difficulties on Wednesday, before the Thursday-to-Saturday disruption began.

How did traffic load and reduced capacity combine?

A failover (the transfer of network traffic to a standby system after a primary component fails) increased the load roughly 15 hours before the outage. Teams switched from an alternative networking gateway to the primary gateway, which also supports Exchange Online; Lamanna described the change as part of normal operations.

Microsoft entered the outage with server capacity nearly 14% depleted, following an unrelated problem the company had been working to address the previous day. In Lamanna's account, the extra load and reduced capacity exposed the primary gateway to the July defect.

The switch and the capacity shortfall were separate developments, but Lamanna linked both to the gateway failure. Request buildup then occurred during the peak of United States traffic, turning constrained capacity into a service interruption.

Which factors did Microsoft identify?

Microsoft's account identifies three contributing conditions:

  • A July latent defect that the company found and believed it had resolved.
  • A traffic surge roughly 15 hours before the outage, following a normal failover to the primary gateway.
  • Nearly 14% depleted server capacity after an unrelated problem Microsoft had been addressing the previous day.

What was the scale of the disruption?

The disruption reached Outlook and Teams, which Microsoft says are used by more than 400 million people. The Thursday-to-Saturday duration made it one of the longest outages in Microsoft history.

Lamanna added: “We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations.”

The 70-country reach and the estimated $700 million loss ceiling quantified the operational and financial exposure. Lamanna's explanation places the immediate trigger in the July defect, with traffic demand and constrained capacity determining the scale of the failure.

via washingtonexaminer.com (Source)

Share this article:

More from Amara Osei

Amara Osei

Show full bio

Market editor covering people, launches and day-to-day practice in corporate strategy and chief-executive leadership at CEO Frontier.

449 articles

Filed under

Adjacent sheets

« Previous articleNext article »

End of sheetNE-56 / J1 · November 16, 2026