The 18-hour Microsoft 365 outage on 13 November 2026: how to stop an Exchange blackout paralysing your business

If your office spent Friday 13 November staring at an empty Outlook window waiting for a contract, an invoice, or a password reset code to arrive, you were in large company. Starting on Thursday evening and stretching past eighteen hours today across seventy-four countries, a global Microsoft 365 outage took down Exchange Online, Outlook, OneDrive, OneNote, Copilot, and Teams calendar scheduling. Across the UK today, NHS hospitals and GP practices dropped back to paper records, Ofqual’s complaints service went offline, and removal vans sat loaded outside houses in Kent because conveyancing solicitors could not send the emails needed to release the keys.

Microsoft says there is no sign of a cyberattack. Instead, part of its connection-handling and authentication infrastructure went offline, which dumped all global traffic onto the remaining servers and caused a cascading overload that resisted Microsoft’s first rounds of fixes. To stop delayed messages from bouncing permanently, Microsoft had to stretch its Exchange email timeout window to forty-eight hours. When I design servers and infrastructure or build custom software for UK businesses, days like today prove a simple rule: putting your email, your files, your login codes, and your emergency contacts inside one vendor’s cloud basket means a single routing bug in Redmond shuts your company down.

Why the "New Outlook" app left staff staring at blank folders

One of the most frustrating parts of today’s blackout was watching staff open Outlook on their laptops and find they could not even read yesterday’s emails or look up a client’s phone number from an old signature.

That happened because Microsoft has spent the last two years pushing small businesses off Classic Outlook onto the “New Outlook for Windows” app. Unlike Classic Outlook, which keeps a full offline `.ost` copy of your mailbox on your laptop’s solid-state drive, the New Outlook is a thin web wrapper around `outlook.office.com`. When Microsoft’s connection-handling servers choked this morning, the web shell loaded on screen with completely empty folders. Staff who had not enabled offline caching or kept a real local mail client lost access to their historical correspondence at the exact moment they needed to phone clients directly.

A single-vendor Microsoft setup vs a resilient small-business setup

You do not need an enterprise IT budget to survive an eighteen-hour Microsoft 365 blackout. You just need to separate five things that most offices accidentally tie to their Exchange mailbox:

What broke today (13 Nov 2026)	Standard "All-in-Microsoft" Office	Resilient UK Small-Business Setup
Reading past emails & client phone numbers	Blocked in webmail and New Outlook when Exchange servers fail	Local offline mail cache + independent off-site M365 backup you can search anytime
Logging into banking, Xero, or portals (2FA)	Locked out if the portal sends a 6-digit login code to your dead `@company.co.uk` email	Hardware security keys (YubiKey) or TOTP authenticator apps that never rely on email delivery
Sending urgent contracts or completion notices	Stuck in Microsoft’s 48-hour delayed outbound queue	Standby secondary mail domain / SMTP relay on separate infrastructure (e.g. Linux / Fastmail / SES)
Opening live working documents	OneDrive and SharePoint web tabs time out under load	Critical active project files mirrored locally or backed up to an independent European storage box
Internal team & site coordination	Teams calendar invites and live events fail because they depend on Exchange Online	Core job tracking, rotas, and site logs run on dedicated independent web infrastructure

Five practical steps so the next Microsoft outage does not stop your work

You cannot stop Microsoft breaking its own load balancers, and ripping out Microsoft 365 completely is rarely the right move for a ten-person UK company. Instead, put five cheap circuit-breakers in place before the next outage hits.

1. Never use email as your two-factor authentication method. Today, thousands of directors could not log into their accounting software, courier portals, or supplier accounts because those websites sent a six-digit verification code to an Outlook inbox that was dead for eighteen hours. During a Windows security audit, I move every critical login off email-based codes and onto an authenticator app or a physical FIDO2 security key. An app on your phone generates the code locally without needing Microsoft’s mail servers to be awake.

2. Keep an independent, searchable backup of your Microsoft 365 tenant. As I wrote earlier this autumn about why Microsoft 365 does not back up your files, Microsoft’s Service Level Agreement only promises financial service credits when they go down; it does not get your work done on a Friday morning. If you have an independent off-site backup of your Exchange mailboxes, OneDrive folders, and SharePoint libraries sitting on separate storage, you can open that backup portal during an outage, pull the PDF contract or spreadsheet you need, and carry on working while OneDrive is timing out.

3. Turn on full local offline storage for mail and active files. On Windows laptops, check that your mail client is actually storing at least twelve months of mail locally on the disk, and on OneDrive, right-click your active current-month client folders and select Always keep on this device. If a file only exists as a blue cloud icon in File Explorer, you cannot open it when Microsoft’s authentication layer goes down.

4. Keep a £5/month emergency communications channel on a second domain. If you run a solicitors’ practice, an accountancy firm, or a logistics company where a delayed email kills a transaction, register a clean secondary domain (such as `yourcompany-ops.co.uk`) hosted on a completely separate Linux mail server or European provider outside Microsoft and Google. When Exchange Online stalls for a whole working day, your key staff have a working inbox and outbound SMTP relay ready in two minutes.

5. Stop running your field operations through Outlook and Teams. If your engineers or site crews rely on emailed worksheets or Teams calendar entries to know where they are working today, an Exchange outage blinds the whole company. Moving operational workflows onto dedicated, self-contained custom web software hosted on clean Linux infrastructure means your field team can clock in, read site documents, and generate invoices even when Microsoft 365 is dark across Europe.

Common questions

What caused the global Microsoft 365 outage on 12 and 13 November 2026?
Microsoft reported that part of its connection-handling, authentication, and routing infrastructure became unexpectedly unavailable on Thursday 12 November. That failure pushed traffic onto the remaining healthy servers, causing an elevated load spike across Exchange Online, Outlook, OneDrive, Copilot, and Teams calendar services that took more than eighteen hours to clear. Microsoft stated there was no evidence of a cyberattack.

Will emails sent to our business during the November 2026 outage be lost?
Most delayed messages should eventually arrive. On 13 November, Microsoft extended its Exchange Online email timeout window to 48 hours so that messages sitting in retry queues would not bounce back to the sender as undeliverable while engineers worked through the backlog.

Why did Microsoft Teams calls work today while Teams calendars and invites failed?
Because Teams chat and audio/video calls run on separate real-time media servers, whereas Teams calendar views, meeting invitations, scheduling, and Live Events depend directly on Exchange Online in the background. When Exchange Online went down, anything touching the calendar failed with it.

If today’s Microsoft 365 blackout brought your office to a standstill and you want an independent backup of your mailboxes and SharePoint files, or a standby setup that keeps your business moving when the big clouds fail, take a look at my Servers and Infrastructure or Windows Security Audits pages, or send me a message.