Stocks

Microsoft Traces Global Outlook Outage to July Software Bug

Microsoft says a dormant July bug, heavier traffic and reduced gateway capacity caused the November 12 outage, exposing reliability risks in its cloud subscription business.

By Sophia Reynolds Edited by Oleg Petrenko Published: Updated:
Microsoft Traces Global Outlook Outage to July Software Bug
Microsoft says a July software bug helped trigger the November 12 Outlook outage when heavier traffic hit reduced gateway capacity. Its Lisbon office is pictured in a company file photo. Photo: Microsoft

Key Notes

  • Microsoft traced the November 12 outage to a July software bug in its Microsoft 365 gateways.
  • More than 80% of affected gateway servers stopped responding at the worst point.
  • Microsoft 365 cloud generated about 30% of company revenue in the latest reported quarter.

Microsoft (NASDAQ: MSFT) has traced last week’s global Outlook outage to a software defect introduced in July, explaining how heavier traffic and a temporary loss of capacity overwhelmed the gateways serving its cloud applications.

At the worst point, more than 80% of those gateway servers were unresponsive. That figure concerns the affected Microsoft 365 infrastructure, not Microsoft’s entire server estate. The company’s preliminary report records active customer impact from 16:20 UTC on November 12 to 16:10 UTC on November 13, just under 24 hours.

Why the Gateways Failed

In a public explanation, executive Charles Lamanna said the defect had gone undetected for more than three months. Microsoft’s tests emphasized weaker servers, while the problem worsened on newer machines with more processor cores.

Teams had switched to the gateway shared with Exchange Online about 15 hours before the outage. That increased traffic just as almost 14% of gateway capacity was unavailable because of an unrelated issue.

The gateway had enough spare capacity to withstand that shortfall alone. The combined changes triggered the bug, and automated rerouting then spread the overload to healthy servers. Infrastructure safeguards also failed to contain the cascade.

Why Outlook Took Longer to Recover

Teams, OneDrive, SharePoint and Office applications could switch gateways. Exchange Online could not do so at the required scale, and waiting requests kept overwhelming newly restarted servers.

Engineers restored the affected code to its earlier working state, then patched and restarted groups of servers before bringing them back gradually. The defect was specific to this Microsoft 365 infrastructure and did not apply to general Windows installations.

What It Means for Microsoft Stock

The outage interrupted a substantial subscription business. Microsoft reported $27.8 billion in Microsoft 365 cloud revenue for the quarter ended September 30, about 30% of its $92.3 billion total, according to its earnings release. Its broader cloud business continues to drive the growth story behind MSFT.

The disruption reached banks and government agencies as well as ordinary corporate inboxes. Neither the preliminary report nor executive Charles Lamanna’s public explanation estimates a revenue or earnings hit.

Microsoft expects to publish a fuller incident review later this week. For customers buying reliability alongside software, that report needs to explain how the company will catch similar defects before they reach production and keep a local failure from spreading worldwide.

Big Tech & Innovation, Business, News, Stocks