# Microsoft 365 went down: does your business have a plan B?

> The global Microsoft 365 outage leaves one lesson: an SLA does not run your business. What a small business disaster recovery plan (DRP) needs.

URL: https://pgtechcorp.com/en/microsoft-365-went-down-plan-b/
Actualizado: 2026-11-13

---

On Thursday, November 12, Microsoft 365 went down worldwide. For much of the afternoon thousands of companies could not reach their email, Teams or SharePoint. It was not an attack, and it was not a misconfiguration at the company next door: the provider’s own platform stopped responding, and operations stopped with it for everyone who depends on it.

## What happened, according to Microsoft

The incident is tracked as **MO1550821** and began at 1:26 p.m. Eastern (12:26 p.m. in Panama). It hit **Exchange Online, Microsoft Teams, SharePoint Online, Microsoft 365 Copilot and Defender XDR**. Earlier that same day there was a separate Teams incident (TM1550488, 9:45 to 10:53 a.m.) that had already been resolved.

The provider’s explanation is technical but clear: traffic did not go up. What happened is that **several servers became unavailable on their own** and strained the ones still running. Microsoft pointed to a component that processes server health: it was flagging servers as unhealthy and taking them out of service. To recover, the company paused all deployments and configuration changes, moved traffic to other infrastructure and began restarting the affected servers.

The scale showed up on [Downdetector](https://downdetector.com/status/outlook/): nearly **129,000 reports** for Outlook at the 1:09 p.m. ET peak, and about 69,000 still at 3:20 p.m. At the close of this note Microsoft was still returning services to operation and had not confirmed a root cause. There are no public signs of a cyberattack.

## The contract does not give you the day back

When your provider goes down, the SLA does not run your business. The SLA says how fast Microsoft restores *its* platform; it does not say who answers your customer’s call while your email is not going out, or who holds the file that sat in a mailbox you cannot open. A provider can be up 99.9% of the time and still ruin your morning if your whole operation lives inside that platform and nobody defined what to do without it.

That gap is what a **disaster recovery plan (DRP)** covers: the document that states what gets done, in what order and by whom when a service you do not control stops responding.

## The minimum DRP for a small business

You do not need two hundred pages. Five written decisions take you from improvising to responding in order:

- **A backup channel that exists, not one you imagine.** A contingency mailbox on another provider, with the key accounts created and tested, plus a phone list that lives outside the system. If it only exists in the owner’s head, it does not exist.

- **Who tells whom.** One person responsible for the team, another for customers and suppliers, and a base message written in advance. In an outage, silence costs more than the outage.

- **Where critical data lives.** The files billing depends on cannot exist only inside the service that fell over. A copy outside that provider, with the date of the last restore test, is the difference between waiting and working.

- **What still runs without systems.** Decide in advance which tasks continue on paper, phone or a local template: collections, dispatch, front-desk service, deliveries.

- **Test it, and date it.** A DRP that is never tested is an assumption. A twice-a-year exercise, with the time and result written down, is what turns the document into real capacity.

## What to check this week

Use the incident while it is fresh: confirm you can get into your backup mailbox, check that your backups actually restore, write the list of who to notify and verify who holds the keys to critical systems. If in your company that depends on a single person, that is the most urgent risk, and it is not in the cloud.

At PG Tech we build that plan with small businesses: what fails first, what gets restored first and who answers. If you want to review yours, [get in touch](https://pgtechcorp.com/en/contact/) and we will look at it against your real operation.

## Sources

- [Microsoft 365 Status](https://x.com/MSFT365Status) (official incident account)

- [BleepingComputer](https://www.bleepingcomputer.com/news/microsoft/massive-microsoft-365-outage-disrupts-outlook-teams-copilot-worldwide/) (Nov 12, 2026)

- [Downdetector](https://downdetector.com/status/outlook/) (user reports, Nov 12, 2026)

Full name *

Email *

WhatsApp *

PA +507US +1CR +506CO +57MX +52ES +34Other

What do you need? *

Virtual Collaborator

Technical Support

Cybersecurity

Cloud Infrastructure

Partnership

Employment

Other

Monthly company revenue *

Under $2,000

$2,001 to $10,000

$10,001 to $30,000

Over $30,000

Comments

No llenar este campo

Send

A person replies within 24 business hours.
We only use your data to contact you.

Thank you! Your message has been sent. We’ll contact you soon.

---

PG Tech Corporation, Inc. — Obarrio, Ave. Samuel Lewis, PH Marfil, Ciudad de Panama, Panama
Contacto: WhatsApp 6960-6453 · https://pgtechcorp.com
