← Back to Blog

Microsoft 365 Is Down Again: What Happened and How to Keep Your Team Talking

Outlook, Teams and Copilot went down Nov 12–13. Here's what caused it, how often it happens, and how to keep your team talking next time.

On Thursday, November 12, a lot of people opened Outlook and got nothing. Teams hung. Copilot stopped answering. For close to a full day, some businesses on Microsoft 365 couldn't reach their own inboxes, and many couldn't even get on a call to talk about it.

If that was you, it wasn't your network, and it wasn't something you misconfigured. Here's what actually happened, why it keeps happening, and a simple plan so the next outage doesn't take your whole team offline with it.

What happened on November 12

The outage lasted about 24 hours, from 16:20 UTC on November 12 to 16:10 UTC on November 13 (8:20 a.m. Thursday to 8:10 a.m. Friday Pacific). According to Microsoft's preliminary post-incident report, the cause was a software defect in its own networking gateway, not a cyberattack. (365Fanatic summary of Microsoft's report)

In plain terms, three things lined up:

  1. A hidden bug. A fix Microsoft had been rolling out to its gateway servers since July contained a defect that only showed up under heavy load.
  2. Extra traffic. Early that morning, Teams automatically failed over to the same gateway Exchange Online uses. That's normal resilience behavior, but it pushed load up all day.
  3. Less capacity. About 14% of the gateway's servers were already offline from an unrelated issue the day before.

At the worst point, more than 80% of the gateway servers stopped responding. Exchange Online took the biggest hit, and most users couldn't reach their mailboxes. Teams, SharePoint, OneDrive, Copilot, Defender, Intune, Power BI and others were also affected. Teams and the file services recovered earlier because they could route around the faulty gateway; email couldn't.

Microsoft fixed it by rolling back the defective code region by region. Global webmail was back to normal at 14:17 UTC on November 13. A final report with the full list of repairs is due November 20.

What this means for you: there was nothing to change on your end. Microsoft said no tenant or device changes were needed.

Why does Microsoft 365 keep going down?

November 12 was at least the sixth notable Microsoft 365 disruption of 2026, and the causes are different almost every time: a bad code fix, a maintenance tool, an outside network provider. That's the real lesson. When everything runs through one giant shared platform, a small fault anywhere can take down email, chat, meetings and files all at once.

Date (2026)What went downHow longCause Microsoft gave
Nov 12–13Outlook/Exchange, Teams, Copilot, SharePoint, OneDrive and more, worldwide~24 hoursSoftware defect in its networking gateway (report summary)
Nov 12 (morning)Teams messaging in North and South America~1 hourResource contention in its infrastructure (BleepingComputer)
Nov 9Outlook on the web in Europe, Middle East and Africa~4.5 hoursNot stated (IsDown)
Jul 23SharePoint, Teams, OneDrive, Admin Center, plus Azure, mainly North America~5 hoursBug in an automated network maintenance system removed IP routes (BleepingComputer)
Jan 22Outlook, Teams, Defender, Purview, North America~8–10 hoursInfrastructure issue in North America (ENow)
Jan 21Microsoft 365 and Teams sign-in, North America~2 hoursThird-party networking issue (IsDown)

None of this means Microsoft is uniquely bad at running a cloud. Every large platform has outages. The risk comes from putting every way your team communicates on one of them.

The real cost: everything fails at once

An email outage on its own is annoying. The trouble comes when email, chat, meetings and calling all share one platform, so they all go down together.

  • Your team can't regroup. The Teams channel where you'd say "Outlook is down, here's the plan" is down too.
  • Customers can't reach you. If your business line runs through Teams Phone, inbound calls stop with everything else.
  • Meetings just vanish. Sales calls, interviews and client check-ins scheduled in Teams don't happen, and nobody can easily send a new link.
  • People improvise. Staff fall back on personal cell numbers and texts, which means no records and no shared context.

None of this needs a complicated fix. It needs one communication channel that doesn't depend on the platform that just went down.

A simple backup plan for the next outage

You can set this up in an afternoon, and it works no matter which provider goes down next.

  1. Pick a backup channel that runs on separate infrastructure. Ideally it's one app for calls, texts and meetings, so a single tool covers the gap.
  2. Get everyone signed in before you need it. A backup nobody has logged into is useless at 9 a.m. on outage day.
  3. Give customers a number that doesn't depend on Microsoft. Add a second business number, then put it on your site and in your email signature.
  4. Keep a standing "outage room" meeting link. Share it now so everyone knows where to go without needing email to find it.
  5. Write a one-paragraph outage playbook. Cover who tells the team, where to meet, and how to tell customers. Pin it somewhere that isn't on Microsoft 365.
  6. Bookmark the status pages. Microsoft's Service Health Status page and the @MSFT365Status account on X tell you quickly whether it's them or you.

Where Phound fits

Phound is a backup channel that covers all three things you lose in a Microsoft outage: calls, messages and meetings. It's built by the team behind FreeConferenceCall.com and runs separately from Microsoft 365, so when Outlook and Teams go dark, Phound keeps working.

  • A real business phone number. Calls, SMS and voicemail with AI transcription, so customers can still reach you.
  • Team chat and texting in one inbox. Somewhere to say "here's the plan" while the usual channel is down.
  • Video meetings for up to 500 people. With recordings and transcripts, for the calls you can't afford to cancel.
  • AI summaries. Anyone who missed the scramble can catch up quickly.
  • Desktop and mobile. Calls hand off between devices, so people can work from their phone if their laptop apps are stuck.

Built to stay up. Phound was available 99.992% of the time in 2026, with 37 minutes of total downtime from January 1 through November 17. Microsoft's November 12 outage alone lasted about 24 hours.

99.992%Phound availability in 2026, with 37 minutes of total downtime from January 1 through November 17.
~24 hoursLength of Microsoft's November 12 outage alone.

You don't have to rip out Microsoft to use it. Plenty of teams keep Microsoft 365 for documents and email and use Phound for conversations, or just keep it ready as the backup. If you're weighing a full switch, see how Phound compares to Microsoft Teams. The Basic plan is free, so you can download Phound today and have it ready.

Try Phound free

Calls, texts and meetings in one app that doesn't depend on Microsoft 365. Phound Basic is free, so you can have the backup ready before the next outage.

Try Phound free →

FAQ

What caused the Microsoft 365 outage on November 12, 2026?

Microsoft's preliminary report blames a hidden software defect in its networking gateway servers. A spike in traffic and reduced server capacity triggered it. It was not a cyberattack.

How long did the Microsoft 365 outage last?

About 24 hours, from 16:20 UTC on November 12 to 16:10 UTC on November 13. Email was hit hardest; Teams and file services recovered sooner.

Is Microsoft Teams down right now?

Check Microsoft's Service Health Status page at status.cloud.microsoft or the @MSFT365Status account on X. If they show an incident, it's not your device or network.

Do I need to change anything after the outage?

No. Microsoft said no tenant or device configuration changes were needed.

What should my team do when Microsoft Teams is down?

Move to a backup channel that runs on separate infrastructure, share a standing meeting link, and make sure customers have a phone number that doesn't depend on Microsoft.

What's a good alternative to Microsoft Teams for calls and meetings?

Phound combines a business phone number, team messaging and video meetings in one app, independent of Microsoft 365. Its Basic plan is free, so teams can keep it ready as a backup.