On November 12, 2026, Microsoft 365 suffered an outage that affected email (Exchange Online), Teams, SharePoint and OneDrive, among other services, for hours. According to Microsoft's preliminary report, the cause was a failure in its own infrastructure, not a cyberattack. Even so, for many companies the effect was that of a serious incident: they could not email customers, open their documents or coordinate their work.
Many discovered that day that their procedures did not cover this kind of failure. "So what do we do now?"
- If there is no email tomorrow, how will we reach the team and our customers?
- How long can we manage without that service?
- Do we know how long it could take to come back?
1. Know what you depend on
A plan B starts with an honest list of the services your company cannot work without: email, video calls, shared documents, ERP or CRM, online banking and phones. For each one, note which processes stop if it fails and who should decide what to do.
Do not forget hidden dependencies. If you sign in to several applications with your Microsoft account, an outage of that service can also lock you out of tools that seem to have nothing to do with it.
2. Decide how long you can manage
Not every service is equally urgent. Ask yourself how long each one can be down before the damage becomes serious: customers left waiting, lost orders or missed deadlines. That figure (a few hours, a day, a week) tells you which services need a ready alternative and which can wait.
When the failure is on the provider's side, you do not control how long it takes to come back. That is why your plan should start from what you can do in the meantime.
3. Prepare alternatives before you need them
- An alternative communication channel for the team (phone, messaging or a broadcast list) that does not depend on the failed service, with contacts stored outside it.
- A ready-made message to inform customers and suppliers, and a person in charge of sending it.
- Another way to reach essential information: locally synced copies of critical documents and a list of key contacts outside the cloud.
- Backups that you control: Microsoft 365 retention options are not necessarily the same as a copy you can restore whenever you need to.
- Where to check service status: Microsoft's official Microsoft 365 status page (status.cloud.microsoft) and, if you have one, your IT provider's alert channel.
4. Know who decides and who informs
During an outage, confusion does more damage than the failure itself. Decide who declares that you are switching to plan B, who informs the team and customers, and who stays in touch with the provider. Keep that list printed or available without the failed service.
5. Test the plan
A plan that has never been rehearsed is an assumption. A short session where the team answers "there is no email today, what do we do?" is enough to find what is missing: a phone number nobody has, a document that only lives in the cloud or a person who does not know they are supposed to send the alert.
What ISO 27001, the ENS and NIS2 say
Continuity is not just good practice. ISO 27001 includes controls to maintain security during a disruption and to keep ICT ready for business continuity. Spain's National Security Scheme (ENS) requires, depending on the system category, measures such as impact analysis, a continuity plan, periodic testing and alternative means. And the NIS2 Directive lists business continuity and crisis management among the measures that entities in its scope must adopt.
Where to start
If you are not sure where your company stands, start with our free initial test: 15 questions and your score by area instantly. And if you want to review what your organization would do in an outage like this, get in touch and we will go through it with you.
More from the blog
- Cybersecurity for SMEs: the 5 habits of a responsible company
- Ransomware and double extortion: when attackers threaten to publish data
- What a company can learn from INCIBE's blog: risks and priority actions
Conclusion
Outages at large providers cannot be avoided, but you can decide in advance how to keep working. A simple plan B that the team knows and has tested at least once is the difference between a few uncomfortable hours and a lost day.
At Blue Moon Cybertech we help companies prepare it before they need it: which services are critical, which alternatives to have and how to test them.
Review my plan B →