← Back to blog

DVG Systems Business Continuity

Microsoft 365 Was Down for a Day. Was Your Business Ready?

8 min read
On this page

On Thursday 12 November 2026, email stopped — not for one business in Thunder Bay, but for businesses everywhere at once. Outlook would not load, Teams misbehaved, Copilot went quiet. By the time most people in Northern Ontario had a working inbox again, it was Friday.

If your answer to “what do we do while Microsoft 365 is down” was to keep refreshing Outlook, this is the plan you did not have.

What actually happened

Microsoft tracked the event as MO1550821 across Microsoft 365, with EX1550543 for Exchange Online and TM1550488 for Teams. Loss of Exchange Online mailbox access was logged at 16:17 UTC on 12 November; Microsoft’s stated end time for impact was 16:10 UTC on Friday 13 November (azureblog.co.uk incident write-up). That write-up lists Exchange Online, Teams, SharePoint Online, Copilot, Defender for Office 365, Purview, Intune and Power BI among the services affected. When Microsoft 365 is your office, an outage is not an email problem — it is an everything problem.

On the cause, Microsoft said: “The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change.” It had “no indication that the outage was caused by malicious activity” and said the problem was “not related to cyber or AI / agents.” The apology came the next morning, nearly 24 hours after the trouble started: “We are deeply sorry for the disruption this incident has caused our customers and partners” (NBC Chicago).

A preliminary post-incident review is now posted against those incident IDs in the admin centre. If you are the admin, read it once — not for the engineering, but for what Microsoft commits to in writing.

Step one in any outage: confirm it is not you

The expensive mistake is troubleshooting your own network while the fault sits in a Microsoft datacentre. Microsoft says so itself: check service health “to determine whether this is a known issue with a resolution in progress before you call support or spend time troubleshooting” (Microsoft Learn).

Three places to look, in this order:

  • Service health in the admin centre. Sign in to admin.microsoft.com and go to Health > Service health. It shows every service, any active incidents, and a separate section for issues in your environment needing your action. You need not be a global admin — the Service Support admin and Helpdesk admin roles can view it.
  • status.cloud.microsoft, the public status page. Microsoft points you here for when you cannot sign in to the admin centre — exactly what a sign-in outage creates.
  • @MSFT365Status on X, which Microsoft recommends following for certain events.

Two things to set up before the next one: in Service health, choose Customize > Email to send incident notifications to up to two addresses, at least one outside the tenant; and put the Microsoft 365 Admin app on a phone for push notifications.

Do not start changing things

When nobody can get into email, the instinct is to act: reset a password, toggle MFA, remove and re-add the account, change a DNS record found in a forum.

Don’t. When the fault is inside Microsoft’s datacentres, nothing you change in your tenant brings mail back — it just leaves a second problem after the first one clears: a locked-out user, a half-configured mail flow rule, a DNS record pointing nowhere.

There is a security reason too. Outage days are good days for phishing: staff are expecting messages about Microsoft and frustrated enough to click. The Canadian Centre for Cyber Security describes the pattern — “an urgent request with a deadline,” or an offer to “resolve an urgent issue with their account,” where “the sender asks you to log in via a provided link” (ITSAP.00.101).

Microsoft does not email you a link to fix an outage. Give staff one rule: nobody enters a password anywhere except the normal sign-in page, and nothing gets clicked from an email about the outage. The Cyber Centre also advises “protocols and procedures for your employees to verify and report suspicious communications internally” — a named person to forward it to, decided in advance.

A continuity plan short enough that you will keep it

You do not need a binder. You need four things.

An out-of-band contact list. Mobile numbers and personal email for your team, your MSP and your critical vendors, stored where it opens without Microsoft 365 — printed in the front office, or in a phone’s notes app. A list that lives only in Outlook is no help on outage day.

A phone path that does not depend on email. Decide now how you reach staff and how customers reach you: a text group, a cell number on the voicemail greeting, a note for the front desk.

Local copies of the files you actually need. OneDrive’s Files On-Demand keeps files online-only to save disk space, and Microsoft is blunt about the trade-off: “You can’t open online-only files when your device isn’t connected to the Internet.” Right-click the folders that matter — current jobs, price lists, forms — and choose Always keep on this device, so “they’re always there for you even when you’re offline” (Microsoft Support). Same idea in Outlook: Cached Exchange Mode keeps a local copy of the mailbox, and Microsoft recommends always using it with a Microsoft 365 account (Microsoft Learn). Staff on desktop Outlook could still read recent mail and draft replies that sent once service returned; staff living in the browser could not.

A separate Microsoft 365 backup. An outage is not a data-loss event, and this one was not — but it is the week people notice their only copy of everything lives in one tenant: why your Microsoft 365 data needs backup. If you already have backup, this quarter’s job is to prove a restore works.

What an MSP does during an outage

We cannot fix Microsoft’s network, and neither can anyone else selling you IT support. What we remove is the guesswork: confirm the fault is upstream rather than your firewall, say plainly what is affected, stop changes that will cost money later, and tell you when it is genuinely over rather than when it looks over. Afterward we read the post-incident report and ask the question that matters: which services need a fallback, and which can wait a day?

No written answer to that? Book a free assessment and we will work through it on your systems.

Frequently Asked Questions

How do I know whether Microsoft 365 is down or it is just us?

Check Health > Service health in the admin centre first. If you cannot sign in, use status.cloud.microsoft, which Microsoft provides for that case, and check @MSFT365Status. If neither shows anything and the problem is only in your office, it is probably local.

Should I reset passwords during a Microsoft 365 outage?

No. A service-side outage is not a credential problem, and resets mid-outage create lockouts that outlive it. Wait for Microsoft to confirm service restored.

Was the November 2026 outage a cyberattack?

Microsoft said no: there was “no indication that the outage was caused by malicious activity” and the issue was “not related to cyber or AI / agents.” It attributed the incident to an earlier network capacity upgrade.

Did we need to change anything in our tenant to recover?

No. Recovery was entirely on Microsoft’s side; tenant and device configuration changes were not required. Making them anyway is how a one-day outage becomes a cleanup project.

How long should we plan to survive without Microsoft 365?

Plan for a full business day. The practical test: can we answer the phone, reach staff, open today’s documents and tell customers what is happening? If yes, a day is an inconvenience rather than a crisis.

Sources and last verified

Last verified 16 November 2026. Read the post-incident review for MO1550821 and EX1550543 in your own admin centre for the authoritative account.

Ask AI

Accessibility