Microsoft 365 outage traced to a bug dormant since July
A near-day-long failure of Outlook, Teams and Copilot across more than 70 countries came from a months-old software defect, and customers can now claim service credits.
By Hushread Stories, from 148 outlets · First published 18 Nov 2026 · Chapter 3 of 4
Earlier: Microsoft blames a bug dormant since July for worldwide Outlook and 365 outage
In brief
- Outlook, Teams, Copilot and other Microsoft 365 services failed worldwide starting November 12, 2026, with reports from 72 countries.
- Microsoft's preliminary report says a software bug introduced in July stayed dormant for months before a traffic surge triggered it.
- At the worst point, more than 80% of networking gateway servers in front of many Microsoft 365 services were unresponsive.
- Microsoft ruled out a cyberattack, though criminals later sent phishing emails referencing the outage to steal credentials.
- Customers can claim a 50% credit on subscription price until December 31, 2026, but broader productivity compensation looks unlikely.
Timeline · 16 moments
The Conversation questions whether seven tech incidents are linked
The Conversation ↗Nadella calls Outlook outage a perfect storm; shares fall nearly 9%
CNBC Technology ↗Report explains why redundancy safeguards failed during the outage
SlashGear ↗Analysis finds broader tech outage wave not driven by hackers alone
Technology – New Scientist ↗Officials tell Congress outages linked to rushed patching after AI findings
Lifehacker Tech ↗Outage series prompts questions about a common cause across institutions
Reason ↗Outages across US services spark connection questions
Mashable ↗Hackers exploit outage for credential phishing
Computerworld ↗Microsoft admits over 80% of servers failed
Business Line - Home ↗Compensation for lost productivity seen as unlikely
ABC ↗Update 19 Nov 2026, 7:44 am UTC
The story has widened from the outage itself to the debate over whether a run of tech failures is linked. CNBC and The Indian Express carried Satya Nadella's description of the Outlook outage as a "perfect storm," and The Conversation looked at seven major tech incidents in one week and asked whether they are really unconnected. The core facts of the Microsoft 365 outage and its July bug are unchanged, so the headline still holds, but the framing now includes this wider question.
Update 19 Nov 2026, 1:36 am UTC
New coverage confirms the root cause is a software bug introduced in July that stayed dormant until a traffic surge triggered it, and New Scientist argues the broader run of tech outages that week was not simply the work of hackers. SlashGear reports that the built-in safeguards meant to keep Microsoft 365 running through partial infrastructure failures did not hold on November 12. The headline and key points still stand, so this update adds context to the existing account rather than replacing it.
Update 18 Nov 2026, 7:27 pm UTC
The new coverage widens the story beyond the Microsoft 365 outage itself. Reason and Fortune describe a run of outages across U.S. institutions in the same week, including an FAA ground stop the day after the Microsoft failure. Lifehacker Tech reports that Wall Street executives and the NSA told Congress the outages stemmed from companies rushing to patch security flaws found by AI models, not from hackers. The Microsoft account itself is unchanged, so the piece's core facts still hold.
How it started
On Thursday, November 12, 2026, Microsoft began reporting problems with Outlook, Teams, Microsoft 365 and Azure. The Verge described a normal morning at Microsoft's campus, with staff arriving for a regular day of emails and meetings, and then, barely an hour later, one of the company's worst outages in history taking shape.
By the next morning, Fortune reported, more than 43,000 problem reports had come in from 72 countries. Users could not reach email and other workplace tools, and the disruption ran for close to 24 hours at its core, though it stretched across more than one day.
How it unfolded
Microsoft said it was prioritising government and safety services as it worked to restore access. Affected users included lawmakers, the NHS, schools and police forces. On November 13 the company said it had made encouraging progress and ruled out a cyberattack, and it later said services were fully restored by November 14.
The cause came into focus on Monday, November 16, when Microsoft issued a preliminary post-incident report. Bloomberg reported that the bug had been lurking undetected in the company's data centres since July. BleepingComputer said it was introduced in a July update and set off a cascading failure that left more than 80% of the networking gateway servers unresponsive.
Ars Technica described it as three small failures combining. A hidden defect in the cloud gateway, dormant since July, met a surge in load and a drop in capacity. GeekWire added that Microsoft's own safety systems, including automated traffic rerouting, helped turn the flaw into a global outage, and that the company blamed "thundering herds" of retrying traffic. Computerworld noted the report also pointed to gaps in testing that failed to catch the bug.
The executive vice president of Copilot, writing on social media, laid out the three factors behind the failure, Business Line reported, and admitted the scale of the server failure at its peak.
Criminals moved quickly. SecurityWeek reported phishing emails posing as Microsoft 365 service notices that referenced the real outage and threatened to delete held messages, and Computerworld said attackers were using the disruption to run credential phishing.
Where it stands
Services are back, and attention has turned to accountability. Tech reported that affected businesses can claim a credit of 50% of their subscription price, with a deadline of December 31, 2026. ABC took a more cautious view, saying that Microsoft is unlikely to compensate for lost productivity and that customers should not expect a large cash payout.
The outage also fed a wider debate. Several outlets, including USA TODAY and CNN, linked it to other failures that week, including a grounded US air traffic system and a bank outage. Mashable laid out the sequence. Commentators such as The Conversation and The Hindu argued that concentrating so much digital infrastructure in a few companies is dangerous. Bloomberg Opinion, via CNA, questioned the company's AI-focused layoffs. The Independent reported that President Donald Trump brushed off the series of outages.
What to watch
The report so far is preliminary, so a fuller post-incident account from Microsoft may add detail on why testing missed the July bug. Watch also whether pressure grows for compensation beyond the 50% credit, and whether regulators take up the concentration questions raised by commentators. Phishing that exploits the outage may also continue.


