Microsoft blames a bug dormant since July for worldwide Outlook and 365 outage
A flaw introduced in a July update lay hidden for months before a traffic surge set off one of Microsoft's worst outages, leaving businesses weighing service credits and wondering how fragile their tools are.
By Hushread Stories, from 143 outlets · First published 18 Nov 2026 · Chapter 2 of 4
Earlier: Microsoft Says Over 80% of Servers Failed During Global Outlook and Teams Outage
In brief
- Outlook, Teams, Copilot and other Microsoft 365 services failed worldwide from November 12, in an outage lasting close to a full day.
- Microsoft says a bug from a July update to its network gateway servers was triggered by traffic and capacity problems.
- At the worst point, more than 80% of the affected gateway servers were unresponsive, Microsoft told customers in its preliminary report.
- Microsoft ruled out a cyberattack, but criminals quickly sent phishing emails that referenced the real outage to steal credentials.
- Eligible businesses can claim service credits of 50% of their subscription price, with a claim deadline reported as December 31, 2026.
Timeline · 9 moments
Analysts debate whether the week's outages are linked
CNN.com - RSS Channel - App International Edition ↗Microsoft admits over 80% of servers were down
Business Line - Home ↗Service credit claims explained for businesses
tech ↗Phishing campaign exploits the outage
SecurityWeek ↗Bug introduced in July identified as root cause
Bloomberg Technology ↗Microsoft publishes preliminary post-incident report
Computerworld ↗Microsoft says services fully restored
Gulf News ↗Outage runs into second day as FAA grounds flights
Mashable ↗Outlook and Microsoft 365 go down worldwide
Fortune ↗How it started
On Thursday, November 12, 2026, Outlook, Microsoft 365, Teams and Azure services began failing for users around the world. The Verge described a normal morning at 9AM, with employees arriving on campus, and then an outage that built within about an hour into one of the company's worst.
By the next morning, Fortune reported, more than 43,000 problem reports had come in from 72 countries. Other coverage put the reach at more than 70 countries.
The damage went well beyond missing email. The Hindu noted the consequences for professional users and entire sectors, and the summary of the story so far includes UK public services such as the NHS, schools and police forces, along with government email.
How it unfolded
Microsoft said early on that it was working to restore access, apologised for the disruption, and ruled out a cyberattack. That last point mattered because the outage soon landed in a week of other failures. Mashable listed the sequence: the Microsoft problems from November 12, an FAA ground stop on November 13 tied to an air traffic control telecommunications issue, and a Chase bank outage blamed on a software problem.
Services were declared fully restored on November 14, after an outage that Gulf News said disrupted Outlook, Teams, OneDrive and other products for more than a day. On Monday, November 16, Microsoft published a preliminary post-incident report. Computerworld said it identified multiple causes, and Ars Technica described three small failures combining to take the service down.
The core finding, according to BleepingComputer and Bloomberg, was a bug introduced in July that sat undetected in Microsoft's data centres. The Next Web reported that it lay dormant for more than three months until a surge in load and a drop in capacity set it off. GeekWire added that Microsoft's own safety systems helped turn the flaw into a global outage, and blamed so-called thundering herds, where automated rerouting piles traffic onto the remaining servers.
The scale was stark. Business Line reported that Microsoft admitted over 80% of the affected servers were down at the peak, and 9to5Mac carried the same figure. Business Line also pointed to testing gaps that let the bug through.
Opportunists moved fast. SecurityWeek reported phishing emails posing as Microsoft 365 service notices that referenced the real incident and threatened to delete held messages, and Computerworld described a credential-phishing campaign exploiting the outage.
Where it stands
Services are back and the explanation is on the table, though the report is preliminary. The conversation has shifted to accountability and money. Gulf News and tech both laid out how affected businesses can claim a credit of 50% of their subscription price, with the French outlet giving a deadline of December 31, 2026. ABC struck a more cautious note, saying Microsoft is unlikely to pay out much for lost productivity.
The outage also fed a wider argument. Several outlets, including The Conversation and The Hindu, argued that dependence on a few giant providers is dangerous. On the question of whether the week's outages were linked, CNN ran an analysis for readers feeling paranoid, and Fast Company said they show corporate America needs to modernise outdated technology. The Independent reported that President Donald Trump brushed off the series of outages in remarks on Tuesday.
What to watch
The preliminary report is not the last word, so a final post-incident report and any changes to Microsoft's testing and capacity safeguards are the obvious next steps.
For customers, the practical question is how many will file for credits before the deadline, and whether regulators or large clients push for stronger guarantees. Phishing built on the outage is also likely to keep circulating while the incident is fresh.


