
Supplier risk management is not just about checking whether a supplier is financially sound. It is also about understanding how much of your business depends on them, and what you would do if their service stopped working.
The Microsoft 365 outage of 12 and 13 November 2026 is a useful case to learn from, precisely because it ended the way most do. It started at 16:20 UTC on the Thursday and customers were clear of active impact at 16:10 UTC on Friday, a little under 24 hours later.
Microsoft's preliminary post-incident report says the cause was a latent defect introduced in a July change to its network gateway servers. The change had been running worldwide for three months without issue. It surfaced when two ordinary events coincided: Teams failed over to the primary gateway serving Exchange Online, and almost 14% of gateway capacity was out of service for an unrelated reason. Neither would have mattered alone. At the low point, more than 80% of servers were unresponsive.
Two details are worth a director's attention. A rollback was not possible because the defect was months old, so engineers had to write a patch that returned the code path to its previous known-good state. And roughly 15 hours passed between the first customer support case and a fix that held. Neither is a criticism of the response. Both are a reminder that “they will fix it soon” is an assumption, not a plan.
The incident was not a cyber security event, and Microsoft confirmed that no malicious activity was involved. You can read its Microsoft 365 service status and the BBC’s coverage of the outage.
One supplier can mean several business functions
The immediate lesson is not that a small business should stop using Microsoft 365. It is that the label “email supplier” may understate how many essential tasks depend on one provider.
Services affected include Outlook, Teams, SharePoint, OneDrive, OneNote, To Do and Copilot, all of which depend on Exchange Online. Microsoft Azure was unaffected, while consumer products also experienced degraded service. Microsoft says more than 430 million people use its 365 apps. Downdetector recorded 140,000 reports from 74 countries on Thursday evening, and problems were reported in more than 70 countries.
The effects described by organisations show how a technology disruption can spill into everyday operations: UK police forces asked people to phone instead of email; NHS email was affected, with the National Pharmacy Association warning of longer waits and delays to some prescriptions. GMB reported serious impacts across ambulance and NHS trusts, including difficulty referring patient details as normal and a growing backlog. GP practices, schools and Parliament also reported communication disruption or set out alternatives. Internationally, government services in Japan, Australia and Singapore were affected, while the Philippines Supreme Court warned of delayed email responses. OpenAI and Anthropic also reported problems connecting to Microsoft services.
These are not all the same operational risk. But they share a question every director can ask: if one supplier or platform becomes unavailable, which parts of our business are affected together?

Start with the work you cannot pause
For a business of 10–250 people, supplier risk management does not need to start with a complex scoring model. Start with a practical test: which suppliers could you not operate without for a day?
Think beyond obvious suppliers and list the tools and services that help you take orders, deliver work, access records, pay people, communicate with customers or meet important obligations. Then ask what happens if each is unavailable for a few hours, a full working day or longer.
A 40-person manufacturer might find that its production can continue for a short time, but orders, delivery changes and customer updates rely on email and shared files. A 15-person professional services firm might be able to do client work offline, but struggle to confirm deadlines or access current documents. The aim is to identify the interruption that matters, not to catalogue every supplier you use.
For each critical supplier, record four things:
- What work depends on it? Name the business activity, not just the software.
- How long can you manage without it? Set a realistic tolerance with the people doing the work.
- Who owns the dependency? Give one person responsibility for keeping the information current.
- What is the workable fallback? Be specific about what staff would do, and how customers would be told.
This is the core of a proportionate supplier risk management approach: clear dependencies, named ownership and useful actions.
Prepare a first-hours response
During an email or Teams outage, people can lose time trying the same service repeatedly or waiting for someone else to decide what happens next. A short response plan can help your team move from uncertainty to action.
Agree in advance:
- An out-of-band contact route. This means a route that does not rely on the affected provider. Decide how your team will reach one another and how customers can reach you.
- Who makes the call. Name the person who decides when to activate the fallback, and who stands in if they are unavailable.
- What must keep running. Identify the work that cannot sensibly wait, and what can be paused until service returns.
- How you will inform customers. Agree a simple message and the channels you will use.
- Where key phone numbers are kept. Store essential contacts somewhere people can reach without Outlook or SharePoint.
A fallback route only helps if staff can find and use it. If a business relies on email to announce that email is down, it has not yet planned a workable alternative. The same goes for contact details stored only in Outlook.

Keep the plan proportionate
A full supplier risk programme (with detailed questionnaires, scoring models and routine reviews of every vendor) is likely to be overkill for a 15-person firm. The lighter version is a one-page list of critical suppliers, a named owner for each, and a fallback contact route that has been checked.
That does not mean ignoring supplier terms or security. It means putting your limited time into the dependencies that could stop important work. Review the list when you take on a major new supplier, change how you work or discover that a fallback is no longer usable.
This kind of preparation can also help a business make better choices. If you know that several core activities depend on one provider, you can weigh the convenience and cost of that arrangement against the impact of disruption. You may decide the current setup is still right, but with a tested alternative for the most important tasks. Risk management is about enabling informed choices, not automatically avoiding every risk.
Our business resilience approach focuses on the activities that matter, the dependencies behind them and practical response actions. For wider leadership decisions, strategic risk management helps make risk part of day-to-day choices without adding unnecessary process.
Common mistakes to avoid
Assuming the standard choice is risk-free. Microsoft 365 is widely used, but being a familiar or common service does not remove the possibility of disruption. A sensible plan recognises the dependency without treating it as a reason to panic.
Choosing a fallback inside the same ecosystem. If Outlook and Teams are both unavailable, a plan that depends on using one to replace the other may fail at the same time.
Keeping every contact in the affected system. Make sure essential staff, customer and supplier numbers are available somewhere else.
Leaving the decision to “someone”. A named decision-maker and clear stand-in prevent avoidable delay when the team needs to act.
Treating the outage as an opportunity to share sensitive details. Microsoft reported a high-volume phishing campaign that used the outage as its lure from 13 November. The emails impersonated service-health notifications, quoted the real incident ID, and claimed held messages would be deleted within 24 hours unless the recipient clicked a link. Microsoft says it blocked the campaign and that incidents should be checked in the admin centre, never through a link in an email. Be wary of unexpected requests for credentials, particularly during a disruption, and verify them through a contact route you already trust.
The BBC also notes that some organisations no longer publish press office phone numbers. If email is down and there is no phone fallback, a contact route that normally seems unimportant may disappear precisely when it is needed.
For how losses build if a disruption runs beyond a day, our follow-up article asks what a week-long outage would do to a small business.
A short supplier risk management FAQ
What is supplier risk management?
It is the process of understanding how suppliers affect your ability to operate, what could happen if a critical service is disrupted, and what practical steps you can take to reduce the impact.
Does a small business need a formal supplier risk programme?
Not necessarily. A small business can start with a one-page list of critical suppliers, the work that depends on them, a named owner and a tested fallback contact route.
Should we move away from Microsoft 365?
This outage alone does not answer that question. First understand which activities rely on Microsoft services and what the consequences of disruption would be. Then decide whether a practical fallback or a different supplier arrangement is proportionate for your business.
What should a small business continuity plan include?
At minimum, identify essential work, who makes decisions during disruption, how staff and customers will communicate if usual channels are unavailable, and what the team should do first. Keep it easy to find and test it with the people who will use it.
One useful next step
Take 20 minutes with your leadership team to list the three suppliers or systems you could least afford to lose for a day. For each, name an owner and write down one fallback you can use without relying on the same provider. That simple exercise is a practical start to supplier risk management, and a useful foundation for a business continuity plan for a small business.
If you would like a proportionate view of your key dependencies and practical next steps, Philip Alcock can discuss a Rapid Resilience Diagnostic. Contact Philip at philipalcock@realrisksolutions.com or +44 (0)1223 230205.
Philip Alcock
Real Risk Solutions
