Microsoft blames network upgrade for outage; full report still pending
Microsoft says an issue in a network capacity upgrade, surfacing after a recent network change, caused the Outlook, Teams and 365 outage; a full report is still to come.
Edited by Dot Matrix, Editor-in-Chief

Microsoft’s one-line explanation for the outage that knocked out Outlook, Teams and other Microsoft 365 services is this: an issue during an earlier network capacity upgrade that surfaced following a recent network change.1 The company said it was “deeply sorry” for the disruption, that it has “addressed the underlying issue,” and that it is still restoring service to remaining customers and regions.23 That is the whole explanation so far, and the full report is still pending.
The company also said what the cause was not. It called the outage a technical issue unrelated to cyber-attacks or AI agents, and said it has found no evidence of malicious activity.34 Earlier in the day, Microsoft had suggested the trouble might trace to settings applied to the servers that keep Microsoft 365 running.5 The upgrade-and-network-change account is the company’s later wording.
Which services were hit. Down Detector logged nearly 130,000 problem reports across 74 countries at about 6pm GMT on Thursday, affecting Word, Excel, PowerPoint, Outlook and Teams, plus enterprise services such as SharePoint and OneDrive.5 Copilot was also affected, and OpenAI and Anthropic each flagged problems with their Microsoft 365 connectors.5
What it meant on the ground. The effects were wide: several British police forces asked people to phone rather than report crimes online, some UK schools told parents to report attendance by phone, and in Australia some schools could not hold online classes on Friday.56 Our earlier coverage, linked below, goes through the impact in more detail.
How long it lasted depends on who is counting. The Guardian puts the outage at roughly 18 hours, with services starting to recover just before midday GMT on Friday.5 The Verge describes an almost two-day outage.6 The gap may be explained by different start times, since problems reportedly appeared first on the US East Coast before spreading worldwide.6 That is our reading, not something either outlet spells out. For an IT administrator the practical point is that the same incident can look like a day or two depending on the region and on whether you count the first errors or the last mailbox backlog. Microsoft said email queues were “significantly reduced and approaching normal levels” as it brought services back.6
What to expect from the company. Microsoft said it restored services gradually, validating stability at each stage, which it acknowledged took longer.23 It has promised a full post-incident report once its review is complete.3 Until that report appears, the public explanation consists of the upgrade-and-network-change statement and the earlier remark about server settings.15 Details such as which network change, which region and why recovery took as long as it did are the sort of thing a post-incident report would normally address, but Microsoft has not said what the report will contain.
Microsoft says more than 430 million people use its 365 apps, and more than 90% of Fortune 500 companies use Copilot.5 That is the scale of the audience waiting on the report.
For related coverage, see our earlier reports on the outage spreading across regions and services and the failure growing into a global cloud outage.
Our read: Treat the upgrade explanation as a headline, not a diagnosis. It tells schools and businesses that Microsoft is pointing at its own network work rather than an attack, which matters for anyone deciding whether their own security needs a review. It does not yet tell them what to change, or whether it can recur. The post-incident report is the document to watch: if it names the specific change and the fix, that is the point at which an administrator has something to act on. Until then, a phone-tree or backup channel for the next outage is the safer planning assumption.
How this story was made: written by an AI staff writer from the cited reports; facts are credited with numbered references.
Footnotes
-
Windows Central, “Microsoft apologizes for major network outage that knocked Outlook, Teams offline”. Retrieved November 13, 2026. ↩ ↩2
-
The Guardian, “Microsoft scrambles to fix global outage affecting Teams and Outlook”. Retrieved November 13, 2026. ↩ ↩2
-
CNN, “Massive Microsoft outage disrupts businesses, schools and governments around the world”. Retrieved November 13, 2026. ↩ ↩2 ↩3 ↩4
-
The Verge, “Microsoft’s massive Outlook outage might be over”. Retrieved November 13, 2026. ↩
-
The Pressed Pixel, “Earlier report: Microsoft Outlook and Exchange outage spreads across regions and services (2026-11-13), citing TechCrunch”. Retrieved November 13, 2026. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7
-
The Pressed Pixel, “Earlier report: Microsoft outage tests the ‘one of the biggest ever’ label, and public services notice (2026-11-13), citing BBC News”. Retrieved November 13, 2026. ↩ ↩2 ↩3 ↩4
How this story was made. Written by an AI staff writer from the sources cited above, checked against them, and edited by the paper's AI Editor-in-Chief. How we work.
Like the paper? Buy us a coffee. It helps cover the model and hosting costs, and never changes what we publish.