Microsoft 365 outage hits Outlook and Teams as servers become unexpectedly unavailable

An inbox that will not open. A Teams meeting that never connects. If you searched “Microsoft outage today” on 12 November, you were far from alone.

A Microsoft 365 outage is disrupting Outlook email, Teams, SharePoint, Microsoft 365 Copilot and Microsoft Defender XDR, according to Microsoft’s status page as quoted by Engadget. As of 09:03 UTC on 13 November, Microsoft still listed the problem as active. It reports early signs of recovery, but no root cause and no time for a full fix.

Microsoft 365 is where much of the world’s office work happens: email, meetings, shared files and AI help. When it stops, a lot of work stops with it. TechCrunch also notes this follows a days-long Microsoft 365 outage in September 2026, which Microsoft blamed on a “core authentication configuration”.

How the Microsoft 365 outage spread from email to ‘any region’

Microsoft’s service health records date the first incident, EX1550543, from 16:17 UTC. Microsoft’s wording: users “may be unable to connect to their mailboxes in Exchange Online through multiple connection methods”. At first, Microsoft pointed to the Americas.

At 18:26 UTC, a wider incident, MO1550821, opened: users “may be unable to connect to multiple Microsoft 365 services”. By about 18:53 UTC, Microsoft said the problem “may affect Microsoft 365 service connectivity for users in any region”, ABC News and Tom’s Guide reported.

Outlook reports on Downdetector peaked at about 130,000 in the US around 18:30 UTC, Euronews and Fox Business reported; these are user complaints, not official figures. Even Microsoft’s status page struggled to load for a while, Engadget and Tom’s Guide said.

Servers dropping out, not a flood of traffic

At about 19:36 UTC, Microsoft paused all deployments and configuration changes. Minutes later came the clearest explanation so far: the heavy load was not caused by more traffic, but by “a number of servers being unexpectedly unavailable”, which strained the rest. By 20:00 UTC it had restarted all affected servers and was testing a fix for servers failing automated health checks.

Restarting was not enough. At 23:59 UTC, Microsoft said restored servers could stop responding once traffic returned, so it limited some traffic and rebuilt some servers with an earlier configuration.

By 08:06 UTC on 13 November, Microsoft said a patch to an “upstream authentication/routing configuration component” was making servers more stable where applied. It is widening the patch step by step, starting with regions in peak business hours. At 09:03 UTC it saw early signs of stabilisation, though capacity was not yet normal, and said it would hold delayed email for up to 48 hours.

Microsoft says it is “not aware of any malicious activity” behind the outage, and will publish a Post-Incident Report with the root cause once service is restored. IT Pro reported on Friday morning that disruption continued.

What we don’t know is why those servers dropped out. Pausing changes and rolling back settings suggest engineers are ruling out recent changes; that alone does not show one caused this.

If Outlook or Teams is down for you, what to do while you wait

So, is Outlook down? For many people, yes: as of 09:03 UTC on 13 November the problem was still active. A few calm steps help, wherever you are:

• Check the Microsoft 365 outage status first. Anyone can use status.cloud.microsoft. IT admins can open Service health in the Microsoft 365 admin centre and follow EX1550543 and MO1550821.
• Don’t keep resetting your password. Microsoft describes a service problem, not a problem with your account.
• Use what is already on your device. Outlook on a desktop or phone may still show email downloaded earlier. Save work locally, as shared files may not sync.
• Switch channels for anything urgent. Call, send a text, or move the meeting.
• Expect late mail once service returns, and check your Outbox.
• Be careful with “fix” emails. Outages can attract scam emails. Don’t sign in through a link that claims to restore your account.

A quick, open response, but the cause is still the real test

There is a fair case for Microsoft. It posted frequent, specific updates, ruled out a traffic surge, and paused all changes.

The other side matters too. The status page itself struggled when people needed it most. And a second large disruption in a few months will make IT teams ask how much depends on one provider.

On balance, the response so far looks steady. The real measure will be the explanation: what made the servers fail, and what Microsoft will change.

Separately, Microsoft has confirmed the Windows 11 update KB5132061 may fail to install on some PCs, BleepingComputer and BetaNews report; our November 2026 Patch Tuesday story has more.

For now, keep an eye on the status page. The all-clear will matter first; the root cause will matter for much longer.