Update: Microsoft blames a July bug for last week's outage, with 80% of servers down at the worst point
Executive Charles Lamanna says a hidden flaw, a Teams traffic shift and 14% of capacity already offline overwhelmed the Microsoft 365 gateway on Nov. 12.
Microsoft has now explained why Outlook and other Microsoft 365 tools failed worldwide on Nov. 12. In a post on X, executive Charles Lamanna said a software bug introduced in July went undetected until heavier traffic and reduced server capacity set off a chain reaction during peak U.S. business hours, Fox Business reports. ABC News also reported that Microsoft identified the issues. This updates our Nov. 13 report, which noted that Microsoft had pointed only to a capacity upgrade.
Three things stacked up
Per Fox Business's account of Lamanna's post, three factors overwhelmed the network gateway that handles traffic for many Microsoft 365 services:
- A latent defect. It came from a fix built for Microsoft 365 gateway servers, which had run worldwide for more than three months without trouble. Lamanna said neither the defect nor that fix applies to broader Windows deployments.
- More demand. Teams traffic shifted to a system that also supports email.
- Less capacity. Nearly 14% of that system's server capacity was already offline because of a separate issue.
As servers stopped responding, traffic was automatically routed to the ones still working, which overwhelmed them too. "At its lowest, more than 80% of servers were unresponsive," Lamanna wrote.
Why testing missed it, and why recovery was slow
Microsoft's labs did not reflect the mix of traffic and hardware that triggered the bug. It was worse on newer, more powerful machines, while testing leaned toward weaker hardware. A separate problem stopped safeguards from containing the failure to sections of the network, so it spread globally.
Recovery dragged because servers coming back were immediately swamped by waiting traffic and failed again. Lamanna said the automated recovery systems were not built for a breakdown this wide, and the months-old bug could not be quickly undone with normal rollback tools. Engineers applied a fix and restarted groups of servers before returning them gradually.
Who was spared, who was not
Teams, OneDrive, SharePoint and Office apps could switch away from the faulty infrastructure and recovered earlier. Exchange Online, which runs email, could not, which is why email stayed down longest. Teams chats and meetings worked normally for most of the outage, Lamanna said. He had already said on Nov. 13 that it was not a cyberattack or caused by AI tooling.
For a small business the lesson is about dependency, not blame: one vendor's email gateway took out calendars, invites and customer replies at once. Our Main Street piece covers the phone-and-text fallback for anything with a deadline or a dollar amount.
The stock
Microsoft closed Monday at $517.99, 6.8% below its Nov. 4 peak in our chart data, in a session when the Nasdaq Composite fell 2.49%. We cannot attribute that gap to the outage.
Sources: Fox Business, quoting Microsoft's Charles Lamanna on X (we read Fox's account, not the post itself); ABC News; price data via Yahoo Finance. This is market information, not investment advice.
Want your business to be the answer?
Get a full package of articles about your business, built so customers, Google and AI assistants can find you.
New ebook from The Company ChronicleHow to Research Like a Wall Street AnalystFind original sources, analyze trends, and build your own insights. 36 pages with worksheets.Get the ebook · $29Instant PDF download

