Sky News reported that the Microsoft 365 outage of 12 and 13 November 2026 disrupted Outlook and Teams, affecting businesses and public services in the UK and overseas. The impact varied between services and organisations, but it exposed a question that every business should be able to answer: what would we do if our everyday tools were unavailable for the next working day?
You may have little influence over when a provider restores its service. You can still decide which activities must continue, how people will communicate and which temporary arrangements are safe to use. A business continuity exercise tests whether those arrangements actually work.
For technical background, a public copy of Microsoft’s preliminary post-incident report (PDF, hosted by a third party) covers incidents EX1550543 and MO1550821. Dated 15 November 2026, it describes Exchange Online as the most affected service, with knock-on effects on features in other services that depend on it. Many of those services remained accessible, so the incident should not be read as every Microsoft 365 application being entirely unavailable. The report is preliminary and subject to change; Microsoft 365 administrators should check Service health in their admin centre for the latest incident report.
Start with the work that must continue
The first question is not which application has failed. It is what the business can no longer do as a result.
For a small organisation, that might include:
- receiving and confirming customer orders;
- contacting staff, customers and suppliers;
- accessing the records needed to deliver today’s work;
- approving payments or time-sensitive decisions; and
- coordinating people across different locations.
Decide which activities can wait, which need a temporary workaround and how long each can reasonably be interrupted. Give somebody responsibility for making those decisions during an incident, including a deputy if they are unavailable.
A useful plan describes how essential work continues at an acceptable level. It does not need to promise that every normal activity will remain available.
Check whether the fallback shares the same dependency
Microsoft 365 can bring email, meetings, files and identity together. That integration is useful in everyday work, but it can also mean several apparent alternatives depend on the same underlying services.
Consider these examples:
- The continuity plan is stored only in SharePoint.
- The emergency contact list is accessible only through Outlook.
- The alternative communication application requires the same Microsoft sign-in.
- The instructions for accessing a backup are in an unavailable shared folder.
Buying another application does not automatically create an independent fallback. Check how people sign in, where essential information is held and what access will remain possible during the scenario you are planning for.
Cloud, on-premises and hybrid systems all have dependencies. Running your own servers gives you different recovery options and responsibilities, but connectivity, hardware availability, suppliers and specialist skills can still limit how quickly you recover.
Agree practical workarounds before they are needed
A proportionate fallback might be a telephone contact tree, a protected copy of essential contact information, or a temporary manual process for recording work that can be entered into the normal system later.
For each workaround, establish:
- who can authorise its use;
- where the necessary information and equipment are kept;
- who checks that the information is current;
- how access and sensitive information remain protected; and
- how temporary records will be checked and reconciled afterwards.
Avoid leaving staff to improvise with personal email accounts, unapproved file-sharing services or weakened payment checks. The pressure to keep working should not quietly remove the safeguards the business normally relies on.
Also agree who monitors the provider’s updates and who communicates with staff and customers. Microsoft’s service-health guidance explains the admin-centre dashboard and alternative status page. Include a way to obtain updates that does not depend entirely on your usual email service.
Backups and continuity answer different questions
Backups help answer whether information can be recovered. Continuity planning asks how the business will operate during an interruption.
A successful backup does not by itself provide working email, access to an application or a safe way to process today’s orders. Restoring data may also require systems, credentials and people that are unavailable during the same incident.
Check what is protected, how it can be accessed and whether the agreed recovery process has been tested. A Backup & Recovery Assessment can help establish the coverage and available recovery evidence, while the continuity plan needs to address the wider business activities and decisions.
Rehearse a working day without your usual tools
A plan can say “contact customers by phone” without establishing whether anyone has the numbers, who makes the calls or what they should say. A short discussion exercise can expose those gaps before an actual outage.
Bring together the people responsible for the affected work, communications and technical support. In a small business, one person may cover several of those roles. Start with a scenario such as:
It is 9am. Email, Teams and shared documents are unavailable, and there is no reliable restoration estimate. A customer needs an urgent response, an important approval is due, and your usual incident contact is absent. What happens in the first 30 minutes?
Work through the decisions in order:
- How do you establish what is affected and tell staff what to do?
- Can you reach the plan and the people needed to put it into action?
- Which work continues, which uses a workaround and which pauses?
- Who approves exceptions, and which safeguards must remain in place?
- What changes if the interruption continues into the following day?
- How do you confirm recovery and reconcile work completed through temporary processes?
Ask people to show where they would find the information rather than assuming it will be accessible. Record any decision that depends on a person, password or system that the scenario has made unavailable.
The NCSC’s Exercise in a Box offers resources for practising responses to cyber attacks. A provider outage can use a similar discussion format, with the emphasis on continuing essential business activities rather than assuming a malicious cause.
Turn the exercise into changes you can verify
An exercise is useful when it changes what the organisation can do next time. Finish with a short action list that records each gap, its owner, a target date and how the fix will be checked.
That might mean updating contact details, providing controlled access to essential records, naming a deputy or testing a temporary approval process. Revisit the relevant parts of the plan when people, systems or responsibilities change, and rehearse again after significant changes.
You cannot prevent every supplier outage. You can prepare people to recognise the interruption, make informed decisions and keep the most important work moving while recovery takes place.