Microsoft 365’s global outage: What happened, and what should businesses learn?

Last week’s global Microsoft 365 outage left many businesses unable to use Outlook and email for around a day. It wasn’t a cyberattack. This article explains what went wrong and what small and medium-sized businesses should take from it.

What happened?

The disruption began on Thursday 12 November 2026 and continued into Friday 13 November. Microsoft’s preliminary report puts the main impact at roughly 4.20pm on Thursday to 4.10pm on Friday, UK time. Exchange Online, the service behind Microsoft 365 business email, was hit hardest. Teams, SharePoint, OneDrive and Copilot were also affected in places, and not every service was down throughout.

Why did it happen?

According to Microsoft’s preliminary report, this was a technical failure, not a cyberattack. Three things combined:

  • A hidden software fault. It had been in part of Microsoft’s infrastructure since July and only caused problems under particular conditions.
  • A shift in traffic. Around 15 hours earlier, an automatic failover moved Teams traffic onto infrastructure also used by Exchange Online. This is normal practice, but it increased the load.
  • Reduced capacity. Around 14% of the relevant server capacity was already unavailable for an unrelated reason. Microsoft says this wouldn’t have caused an outage on its own.

Together, these overloaded the servers that connect users to Microsoft 365. Work was redirected to other servers, which then struggled too, causing a chain reaction. Recovery took time because restarted servers could be overwhelmed again by users reconnecting.

What should you learn from it?

No cloud service is infallible, and this isn’t just a Microsoft 365 lesson. The same applies to the finance, CRM, phone, payroll and payment systems most businesses now rely on. Microsoft 365 remains an excellent platform and this isn’t a reason to abandon it, but when the problem sits inside a provider’s own infrastructure, your IT support provider can’t restore the service directly. What they can do is help you prepare. Having several apps from one provider also doesn’t mean you have several independent ways of working, because some services share infrastructure.

Three questions every business should ask

  1. Which cloud services does your business depend on, and what happens if one is unavailable for a day? Email is the obvious one, but think about finance, CRM, phones, payroll, payments, files and approvals. Ask whether work would be lost or just delayed, because a postponed task has a very different impact from a lost sale or a missed deadline.
  2. How would you contact staff and customers if a key service, such as email, were down? Name an incident lead and a deputy, agree a way to reach staff that doesn’t rely on the affected service, and keep a short list of critical customers and deadlines stored somewhere else. Bear in mind that a backup email service won’t help if your customers and suppliers are down too.
  3. Do you have a business continuity plan, or just backups? Backups protect your data, but they won’t restore Microsoft’s email service or bring Teams back during an outage.

The right response isn’t to buy a second platform for everything. Understand what you depend on, decide how long you could tolerate an outage, and then either accept the risk, improve your plan, or invest in extra protection.

It’s not just about how reliable your technology is. It’s about how prepared your business is when that technology becomes unavailable.

How Get Support can help

We can review your current setup, assess how your business depends on Microsoft 365 and your other cloud services, and recommend practical improvements. Our white paper, When Microsoft 365 Goes Down, is currently going through final review and will be available soon. It covers backups versus business continuity and practical steps to reduce the impact of future outages.