IT Business Continuity Plan: Lessons From the Microsoft Outage

Last Thursday afternoon, Outlook stopped loading. Then Teams invites failed, shared files went missing from view and Copilot went quiet. For many UK businesses, the working day ended early. If your team spent Friday morning chasing delayed emails and wondering what else you had lost, you are not alone. The Microsoft 365 outage was a sharp reminder that every business needs an IT business continuity plan, not just big ones with an IT department. This guide explains what happened, what it means for a business of 10 to 200 people, and how to build a simple plan that keeps you trading the next time a cloud service, broadband line or laptop fleet lets you down. You will get a one-page template, worked examples for hospitality, professional services and manufacturing, and a short checklist you can run this week.

What happened in the Microsoft 365 outage?

The trouble started late on the afternoon of Thursday 12 November 2026. Users lost access to Exchange Online mailboxes, and problems spread to Teams scheduling, SharePoint, OneDrive and Copilot, according to TechRadar’s live coverage. Downdetector logged a peak of more than 131,000 reports for Outlook alone.

Microsoft said it was “a technical issue not related to cyber or AI / agents”, linked to a recent network change. Recovery was slow and uneven. By Friday afternoon, Microsoft said email queues were approaching normal levels. It extended its email timeout window to 48 hours so delayed messages could still arrive, and promised a full post-incident report.

The impact reached well beyond office workers. Police forces including Hertfordshire and Dorset told the public to use 101 for non-emergency reports. Councils warned that online forms might not work.

There was a second risk too. The National Cyber Security Centre warned people to be cautious with unexpected calls and messages, especially those with links, and to watch for scammers posing as IT helpdesks (reported by Ads Advance). Big outages give criminals perfect cover. A fake “restore your mailbox” email looks very believable when your mailbox really is broken.

What is an IT business continuity plan?

An IT business continuity plan is a short document that answers one question: how do we keep serving customers when a key system fails? It covers the technology you depend on, how long you can live without each piece, what you do instead, and who makes the calls.

It is not the same as a disaster recovery plan. Disaster recovery is about getting systems back. Continuity is about keeping the business running while they are down. You need both, but most small firms only think about the first.

The NCSC’s Small Business Guide on response and recovery puts it simply. Identify your critical systems and data, back them up, share key tasks so no single person is a bottleneck, and keep contact details somewhere you can reach when normal channels are down.

Why does a small business need IT business continuity?

Because almost everything now runs through a handful of cloud services. Email, files, phones, bookings, card payments and accounts software often sit with two or three providers. When one of them stumbles, you have no control over the fix. You only control your response.

Last week showed three gaps we see again and again:

  • No offline contact list. Staff could not find client or supplier numbers because they lived in Outlook.
  • No fallback for email. Nobody knew whether to wait, use personal accounts (a data protection risk) or pick up the phone.
  • No one in charge. Without a named decision maker, teams lost hours waiting to be told what to do.

None of these need new technology. They need a plan written down before the outage, not during it.

How do you write an IT business continuity plan? (6 steps)

1. List the systems you cannot trade without

Walk through a normal day. Write down every system staff touch: email, Teams, phones, file storage, practice or production software, EPOS, booking platforms, card terminals, broadband. Keep it to one line each.

2. Decide how long you can live without each one

This is your recovery time objective (RTO). It is simply the longest a system can be down before real damage starts. Card payments in a restaurant on a Saturday night might be 15 minutes. Email at an accountancy practice in January might be two hours. An archive drive might be a week.

Then decide how much data you could afford to lose. This is your recovery point objective (RPO). If you back up nightly, you could lose a full day’s work. Is that acceptable?

3. Write a workaround for each critical system

For every system with a short RTO, write the manual or alternative way to keep going. Phones instead of email. A printed run sheet instead of the booking screen. A 4G router instead of the leased line. Keep it practical.

4. Name who decides and who does what

Pick one person to declare an incident and a deputy for when they are away. Decide who tells staff, who updates customers and who calls your IT provider. Write down the trigger point, for example “if email is down for more than one hour, switch to the phone plan”.

5. Keep a copy outside the systems that might fail

Your plan is useless if it lives in a SharePoint folder that you cannot open. Print it. Keep a copy on a phone. Store key contact numbers in at least two places that do not depend on Microsoft 365.

6. Test it twice a year

Run a 30-minute tabletop exercise: “It is 10am on a Tuesday and email is down. What do we do?” The NCSC recommends its free Exercise in a Box tool for this. You will find gaps fast, and fixing them costs almost nothing.

A one-page IT business continuity plan template

Here is a simple structure you can copy. Most growing businesses can fill it in within an afternoon.

SystemMax downtime (RTO)WorkaroundOwner
Email (Microsoft 365)2 hoursPhone and SMS from printed contact list; holding message on websiteOffice manager
Shared files (SharePoint / OneDrive)4 hoursSynced offline copies of key folders on two laptopsOperations lead
Phones1 hourDivert main number to mobilesMD
Broadband1 hour4G or 5G backup routerIT provider
Card payments15 minutesTerminals on mobile data; manual process agreed with acquirerSite manager
Line-of-business software4 hoursRead-only export of today’s jobs or bookings, printed each morningDepartment head

Add one more line underneath: “Who calls our IT provider, and on what number?” Make sure the answer does not rely on email.

Office worker taking a phone call at her desk, a simple IT business continuity workaround when email is down

What does this look like in your sector?

Hospitality

Picture a 60-cover restaurant on the Wirral. On Thursday evening the booking confirmations stop and the shared rota in Teams will not load. With a plan, the manager prints tonight’s bookings from the platform’s app, texts the team from a printed staff list and switches card terminals to mobile data if the broadband also wobbles. Service carries on. Our guide to reducing IT downtime in hospitality covers the venue side in more detail.

Professional services

Now picture a 25-person accountancy practice in Chester two months before the January self assessment deadline. Client emails are delayed for most of a day. With a plan, the partners know to phone clients with urgent deadlines, staff work from synced offline files, and everyone is reminded that bank details are never changed by email. That last point matters: outages are prime time for invoice fraud.

Manufacturing

Finally, a 40-person manufacturer in Ellesmere Port. Production machines run fine, but purchase orders, delivery notes and supplier emails all flow through Outlook. With a plan, the shift lead prints the day’s job sheets every morning, key suppliers are on a printed call list and the transport desk confirms collections by phone. The factory keeps moving even when the inbox does not.

Does Microsoft back up your Microsoft 365 data?

Microsoft runs the service and builds in a lot of resilience. But keeping the service available is not the same as giving you a separate copy of your data that you control. If someone deletes a folder, a mailbox is wiped when a leaver goes, or ransomware encrypts synced files, you want a backup that sits outside your tenant.

That is why many businesses add an Office 365 backup service that copies mail, OneDrive, SharePoint and Teams data to a separate location. The NCSC’s guidance on backing up your data recommends keeping backups separate from your main systems and testing that you can restore them.

Rows of server racks in a data centre, where a separate Office 365 backup keeps a copy of business data

A backup would not have stopped last week’s outage. It does protect you from the many smaller incidents that hit businesses every month, and it belongs in any business continuity plan for small business IT.

IT business continuity and disaster recovery: a quick checklist

Run through this list this week. If you cannot tick at least eight, your plan needs work.

  • You have a written list of critical systems and how long you can live without each.
  • Key client, supplier and staff numbers exist outside Microsoft 365.
  • Your main phone number can be diverted to mobiles in minutes.
  • You have a 4G or 5G backup for broadband at each site.
  • Key files sync offline on at least two devices.
  • Microsoft 365 data is backed up to a separate service.
  • You have restored a file from backup in the last six months.
  • One person (plus a deputy) is named to declare an incident.
  • Staff know never to act on emailed bank detail changes.
  • You have a holding message ready for your website and social channels.
  • You have tested the plan with a tabletop exercise this year.

[CIRRUS INSIGHT: 2-3 sentences from Wayne or an engineer on what they actually see with this problem. Elis to fill in.]

If you would rather not do this alone, a good managed IT support partner will help you write and test the plan, set up backups and monitor the services you rely on. With outsourced IT support in place, last week’s outage becomes a phone call and a checklist, not a lost day.

Frequently asked questions

What are the five components of a business continuity plan?

Most plans cover five things: critical systems and processes, recovery time targets, workarounds, roles and contacts, and a testing schedule. For a small business, all five can fit on one or two pages.

What is the difference between business continuity and disaster recovery?

Business continuity keeps you trading while systems are down. Disaster recovery restores those systems and data afterwards. A good plan includes both.

How often should I test my IT business continuity plan?

At least once a year, and ideally twice. Also review it after any major change, such as opening a new site, changing IT provider or moving systems to the cloud.

Was the November 2026 Microsoft outage a cyber attack?

No. Microsoft said it was a technical issue not related to cyber activity. However, the NCSC warned that scammers may exploit outages, so treat unexpected “fix your account” messages with suspicion.

Want a second pair of eyes on your plan?

If last week exposed gaps, we can help. Book a free, no-obligation IT review call and we will walk through your critical systems, spot the weak points and suggest practical improvements. No hard sell. Get in touch here or call us on 0330 313 0966.

Related reading

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top