Cookie Consent by Free Privacy Policy Generator

The Outlook Outage Wasn't a Cyberattack. It Still Tested Incident Response.

Incident Response | Business Resilience

The Microsoft 365 disruption was a reminder that incident response is not only about cyberattacks. It's about knowing what to do when a critical service stops working and the answers aren't immediately clear.

When Outlook and other Microsoft 365 services became unavailable around the world on 12 and 13 November 2026, organisations lost access to tools they rely on every day.

Email access was disrupted, calendars and other connected functionality were affected, and teams had to find ways to keep communicating and operating while Microsoft investigated the issue.

Microsoft subsequently said the disruption was caused by a technical issue, not malicious activity. But that does not make it irrelevant to cybersecurity.

It raised a question every business should be able to answer: if an important system suddenly becomes unavailable, does everyone know what happens next?

Free On-Demand Webinar

Incident Response: Rehearsing the First Hour

Explore the decisions, communications and responsibilities that matter most in the early stages of an incident.

Watch the webinar on demand →

What happened during the Microsoft outage?

The disruption affected Outlook, Exchange Online and other Microsoft 365 services on Thursday 12 and Friday 13 November 2026. For organisations that depend on those platforms, the operational impact was immediate.

IT teams had to work out whether the issue was local, supplier-related or potentially a security concern. Employees needed updates. Business leaders needed to understand what work could continue and what might be delayed.

Although the outage was not attributed to a cyberattack, the first questions looked familiar:

  • What has happened, and which services are affected?
  • Who needs to know?
  • Is there any indication of a security issue?
  • How do we keep essential operations running?
  • How do we communicate if our usual tools are unavailable?
  • Who is coordinating the response?

These are all part of being prepared for an incident, whatever its eventual cause.

An incident rarely arrives with all the answers

When something stops working, the cause is not always immediately obvious. A service disruption might be the result of an internal configuration problem, a supplier outage, a connectivity issue or a malicious attack.

The first hour is often about establishing what is known, what remains uncertain and who needs to act. A useful incident response process gives people clear escalation routes and responsibilities without requiring them to know the root cause from the outset.

What happens when your communication platform is the thing that fails?

Microsoft 365 is more than an email platform for many businesses. Teams supports day-to-day communication, Outlook holds contacts and calendars, and SharePoint or OneDrive may contain important documentation.

If those systems are unavailable, an organisation could also lose access to the very tools it planned to use to coordinate its response.

If Microsoft 365 went down during an incident, could your response team still communicate?

Alternative channels, accessible contact details, offline copies of essential plans and clear decision-making arrangements can make a significant difference. But those fallbacks need to be familiar to the people expected to use them.

A written incident response plan is only the starting point

Having a plan is valuable. Knowing whether it works in practice is even more valuable.

A tabletop incident response exercise gives teams an opportunity to work through a realistic scenario, make decisions and identify gaps before they face the pressure of a real event.

The exercise might reveal that people are unsure who leads, where the plan is stored, how to contact a key supplier or when to involve senior leadership. These are practical issues that can often be improved with the right preparation.

Incident response is a business capability, not just an IT responsibility

While technical teams investigate and address the issue, other parts of the organisation have important roles. Leadership may need to assess business impact, legal and compliance teams may need to review obligations, and customer-facing teams may need to provide updates.

Everyone does not need to be a cybersecurity specialist. They do need to understand who makes decisions, who communicates and how teams work together.

Try this with your team: rehearse the first hour

Imagine your organisation arrives at work tomorrow and Outlook is unavailable. You do not yet know why. Use the next 60 minutes as a discussion exercise.

Eight questions worth asking

  1. Who investigates, and who coordinates the response?
  2. Who decides whether to escalate it as an incident?
  3. How will colleagues receive updates?
  4. Where is the incident response plan stored, and can everyone access it?
  5. What alternative communication channels do you have?
  6. Which critical processes cannot continue without Microsoft 365?
  7. How will you assess whether there is also a security concern?
  8. Who will update customers and suppliers if disruption continues?

You do not need to recreate a sophisticated cyberattack to learn something valuable. Sometimes taking one essential service away is enough to reveal where your response could be stronger.

Build confidence before the next disruption

Incident response exercising is not about predicting every scenario. It is about ensuring that when something unexpected happens, the right people can respond together, make informed decisions and keep improving.

At Secarma, our Incident Response Exercising service helps organisations test their plans, people and processes through realistic, facilitated tabletop scenarios.

Our focus is practical learning: understanding what works, identifying what could improve and helping teams build confidence.

To explore the early stages of an incident in more detail, watch our on-demand webinar, Incident Response: Rehearsing the First Hour.

How ready is your team to respond?

Start with practical advice in our free webinar, or explore how a facilitated exercise can help your organisation prepare.

Watch the on-demand webinar →

Explore Incident Response Exercising →

The best time to find a gap in your incident response process is during an exercise, not during the incident itself.

News and blog posts
Incident Response | Business Resilience The Microsoft 365 disruption was a...
This week's security developments share a common thread that will resonate with...
A critical vulnerability in VMware vCenter Server was exploited as a zero-day...
A security vulnerability in Optimizely, a widely used website personalisation...