On this page
Quick answer. A worldwide Microsoft 365 outage that began on 12 November disrupted Outlook, parts of Teams and Copilot. Microsoft blames servers that unexpectedly became unavailable, says there is no sign of a cyber attack, and has not yet given a time for full recovery.
What happened
Microsoft 365 went down for a large share of its users on Thursday, 12 November. Microsoft's own incident record says the main outage began at 1:26 pm Eastern time, according to BleepingComputer. Outlook took the worst of it. About 130,000 users had reported Outlook problems on Downdetector by that point, CNBC reported.
It wasn't only email. Microsoft's advisory listed Exchange Online, Teams, SharePoint Online, Microsoft 365 Copilot and Defender XDR among the affected services. Users in any region could be hit, even though the first reports came from the Americas.
As of Friday morning India time, the fix was still rolling out. Australia's ABC said in its live coverage that Microsoft had narrowed in on the problem but had given no time for full restoration.
Confirmed vs not confirmed
Confirmed by Microsoft: the cause is not a spike in traffic. In its words, the load came from "a number of servers being unexpectedly unavailable; straining the remaining infrastructure." Microsoft says it paused all deployments, moved traffic away from the affected systems and started restarting servers. It later validated a different server health check method that brought some servers back, and said it is reverting a recent network configuration change that lines up with the start of the outage.
Also confirmed: a Microsoft spokesperson said in a message to Australia's ABC that there is "no indication" of a cyber attack. Australia's Home Affairs Minister, Tony Burke, said after a briefing that officials did not believe it was a cyber event.
Not confirmed: the root cause. Some commentators floated an attack or a bad network update. Microsoft is still investigating, and Fox Business notes the company said its early fixes did not bring the relief it expected. A separate Teams outage earlier that day, in North and South America, was resolved, and Microsoft hasn't said whether the two are linked.
Amazon also stepped in to say AWS was "operating normally", after some reports wrongly tied the problem to it.
What it means for you
If your email is on Microsoft 365, the outage is on Microsoft's side. Reinstalling Outlook or changing your local email settings is unlikely to fix it. Per Microsoft's service list, Teams chat and online meetings stayed largely usable, and files stored straight in SharePoint stayed reachable. Things that lean on Exchange Online, like calendars, meeting scheduling, Copilot's access to your email and Planner tasks, may fail.
Expect a slow return. Microsoft has warned users may see a gradual recovery as their apps reconnect, so some apps will come back before others. For admins, TechRepublic's guidance is sensible: avoid unnecessary configuration changes while this is going on, then check that users can reconnect once Microsoft says it is fixed.
The bigger point is dependency. When one vendor runs your email, calendar, files and AI assistant, a fault in one shared piece can stop a whole working day. That isn't new, but each outage like this makes it harder to ignore.
What to watch
The Microsoft 365 Status account on X and the admin centre (incidents EX1550543 and MO1550821) for the all-clear. After that, Microsoft's post-incident review, which should say what actually caused the server failures and whether the configuration changes it is reverting played a part.
My take
Keep a plan B for the day your main tool fails: a phone tree, a second chat channel, and a shared doc of key contacts that doesn't live inside the same suite. For a small team, an hour spent on that now costs less than one lost morning like this one.
Frequently asked questions
Is Microsoft Outlook down right now?
Outlook was disrupted worldwide from 12 November as part of a wider Microsoft 365 outage. Microsoft said it was returning servers to service and observing limited recovery, but as of Friday morning India time it had not given a time for full restoration. Check the Microsoft 365 Status account or your admin centre for the latest.
What caused the Microsoft 365 outage?
Microsoft says the elevated load was not caused by more traffic but by a number of servers becoming unexpectedly unavailable, which strained the rest. It is testing a different health check method and reverting a recent network configuration change that matches the start of the problem. The final root cause has not been published.
Was the Microsoft outage a cyber attack?
Microsoft said there was no indication of a cyber attack, and Australia's Home Affairs Minister said officials did not believe it was a cyber event. Some commentators suggested an attack early on, but no official source has supported that. Microsoft's own explanation points to failing servers, and it is investigating recent configuration changes.
Which Microsoft services were affected?
Microsoft listed Exchange Online, Teams, SharePoint Online, Microsoft 365 Copilot and Defender XDR, plus features that depend on email such as calendars, Planner and To Do. Teams chat and online meetings stayed largely usable, and files stored directly in SharePoint Online remained reachable, according to Microsoft's service list.
Sources
- Is Outlook down? Widespread outage hits Microsoft apps, nbcnews.com
- Massive Microsoft 365 outage disrupts Outlook, Teams, Copilot worldwide, bleepingcomputer.com
- Widespread Microsoft outage takes down Outlook and other 365 services, CNBC
- Microsoft 365 hit by multi-region connectivity outage, Fox Business
- Microsoft Outlook Down: Over 130,000 Outage Reports as Email, Teams Disrupted, techrepublic.com
- Microsoft outage affects 130,000 users as server failures spread, interestingengineering.com
- Live: Microsoft outage affects users worldwide, impacting Teams, Outlook and Copilot, abc.net.au
Tech news, checked twice, in your inbox.
One calm email when a story is worth your time. Unsubscribe in one click.



