Menu
a close up of a phone screen

Outlook not so good? Staying secure during a service outage

Posted on 18 November 2026

Reading time 7 minutes

What happened?

A major Microsoft 365 outage began on Thursday 12 November 2026 and continued into Friday, disrupting Outlook mailbox access and delaying email delivery. The disruption also affected Exchange online-dependent features across Teams, Copilot, security, compliance and administration services. Microsoft tracked the incidents as EX1550543 and MO1550821, with subsequent reporting of its service-health updates indicating restoration by early 14 November.

Microsoft attributed the disruption to an issue introduced during an earlier network capacity upgrade that surfaced following a recent network change. It described the incident as a technical issue unrelated to cyber activity or AI/agents and said a full post-incident report would follow its review. The continuity lesson extends beyond cyberattacks technical failures at a critical supplier also need to be included in disruption scenarios.

For businesses reliant on Microsoft as a key technology supplier, the disruption brought business continuity planning into sharp focus. An external service failure can affect several critical activities at once, even when an organisation’s own infrastructure remains operational. Business continuity plans must therefore address supplier dependencies—not just failures within the organisation’s own systems.

For security teams, the challenge extended beyond restoring communications. Microsoft identified potential difficulties accessing Defender XDR portals, delays or failures in certain Defender for Office 365 policy evaluations and governance actions, and impacts on Purview capabilities including data loss prevention, audit searches and eDiscovery.

While this was not a complete platform shutdown, as core Teams communications and direct access to SharePoint files remained functional, this disruption highlighted the need for tested continuity arrangements that preserve essential operations, secure access and incident response when a major supplier experiences disruption.

So what?

The potential consequences extend beyond unavailable email:

  • Operational and financial impact: interrupted communications, delayed approvals and reduced access to essential functions can slow service delivery, disrupt customer and supplier relationships and delay revenue-generating work.
  • Security exposure: reduced visibility or delayed policy enforcement can complicate threat detection and response. Unapproved workarounds, such as personal email or removing information protection, may introduce additional risks.
  • Regulatory and reporting obligations: disruption to communications, audit searches or eDiscovery could hinder an organisation’s ability to investigate events, retrieve evidence or meet applicable reporting deadlines. Microsoft identified potential impacts on these capabilities during the incident. Continuity plans should identify relevant obligations, responsible owners and alternative reporting routes rather than assume deadlines can wait for recovery.
  • Reputational damage: delayed responses, interrupted services and inconsistent updates can undermine customer confidence. Clear, timely communications should remain part of the response even when the underlying failure sits with a supplier.
  • Governance and assurance: organisations need to establish which controls remain effective, authorise temporary exceptions and record decisions. A plan that restores productivity without addressing weakened safeguards provides only partial continuity.

The objective is to maintain essential activities without losing control of security, accountability or external commitments. This means finding ways to continue working without quietly accepting uncontrolled access, weakened information protection or unexplained gaps in oversight, and without security becoming an unexamined casualty of the outage.

What should I do?

The recommendations below focus on the Microsoft 365 outage and draw on Microsoft’s guidance for mitigating service incidents, but the principles apply more broadly to disruption affecting any critical software vendor or service provider. Adapt them to your organisation’s dependencies, security controls and contractual or regulatory obligations, using your supplier’s guidance to inform the technical response.

Establish which security capabilities are affected

Start by understanding how the disruption affects your security operations, distinguishing between three types of limitation:

  • Visibility: analysts cannot access the information or interfaces they normally use.
  • Enforcement: policy evaluations or protective actions may be delayed or fail.
  • Access: users or administrators cannot reach resources or management functions.

This distinction helps teams respond proportionately rather than treating an entire service as either operational or unavailable - separate confirmed effects from suspected ones, assign responsibility for material limitations and record any temporary measures introduced.

Where an essential safeguard cannot be confirmed, consider restricting or deferring the relevant activity until its status is understood; an accessible dashboard does not establish that every dependent function is healthy, just as an inaccessible dashboard does not mean all protection has stopped.

Keep incident response reachable

If your incident-management system relies on Exchange to summon responders, the mechanism for coordinating recovery may depend on the service experiencing disruption.

Microsoft recommends parallel email, telephone and SMS notifications, with automatic escalation when the primary responder does not engage and backup contact methods embedded in notifications. Where Teams supports incident triage, its guidance also recommends a third-party backup conferencing service. Build these alternatives into the response plan before they are needed, making clear who activates them, who issues authoritative updates and how staff recognise genuine instructions.

Security, IT and business teams should communicate a consistent position so that staff understand which workarounds are approved, what restrictions remain in place and how to report suspicious activity.

Make response instructions accessible

Response procedures, escalation instructions and essential contact details need to remain accessible when normal working arrangements fail, as keeping them solely within the environment covered by the outage scenario risks making the plan unavailable precisely when it is needed.

Microsoft recommends synchronising critical OneDrive documents locally and using “Always keep on this device” for key files. It also advises training users to access Teams files directly through SharePoint where that route remains available; apply this preparation to the documents needed to coordinate your security response.

Ultimately, alternative access arrangements should match the failure being addressed - mobile connectivity can avoid dependence on an organisation’s network, while Outlook mobile or web access may help during a protocol-specific incident.

Preserve authentication and control emergency access

Review crucial business and security systems for dependencies on email-delivered authentication codes or recovery links, and configure approved alternative multi-factor authentication (MFA) methods that do not rely on the affected mailbox, so users can maintain secure access without disabling safeguards.

Ensure to include account recovery in any testing; an alternative sign-in method is insufficient if recovery still requires access to an unavailable inbox.

Break-glass access - emergency administrative access for use when normal sign-in methods are unavailable - should sit alongside these arrangements as a controlled procedure. Establish when its use is authorised, who can obtain access, how activity is recorded and what review follows, then test the process against its intended scenario. Emergency credentials can address an access problem, but they cannot restore an unavailable underlying service; they complement resilient user authentication rather than replace it.

Put boundaries around workarounds

Give staff approved alternatives promptly, explaining the boundaries around personal email, external sharing and changes to information protection. Where an exception is necessary, record its scope, authorisation and review point so that a temporary measure does not quietly become normal practice.

Operational pressure makes clear guidance particularly important; explain the conditions attached to each workaround so that staff do not have to interpret its limits under pressure.

Connect continuity planning to security assurance

ISO provides a framework for connecting resilience with continued protection. Relevant ISO 27001 Annex A controls include:

  • A.5.29 - Information security during disruption: maintain safeguards during alternative working arrangements.
  • A.5.30 - ICT readiness for business continuity: plan and test continuity when essential technology is unavailable.
  • A.5.23 - Information security for use of cloud services: understand provider commitments and manage cloud dependencies.
  • A.8.14 - Redundancy of information processing facilities: assess appropriate redundancy and shared points of failure.

ISO 22301 adds the business-impact perspective. Its business impact analysis requirements in clause 8.2.2 include dependencies such as partners and suppliers. Compare actual disruption with the documented maximum tolerable period of disruption, rather than assuming existing plans remain realistic.

Translate these principles into exercises. Test whether the security team can receive an alert, assemble, access instructions, authorise emergency access and communicate restrictions during degraded service.

Turn recovery into improvements

Do not close the incident simply because users can sign in again. Microsoft warned during recovery that service access could return before mail flow fully normalised.

  • Check delayed and failed messages, reconcile time-sensitive communications and confirm that dependent workflows and security controls are operating as expected.
  • Review temporary workarounds, withdraw unnecessary exceptions and record any remaining gaps.
  • Use the disruption to test assumptions about critical supplier dependencies, assign owners to improvements and test the revised continuity arrangements.

Preserve evidence and review recovery options

Record the disruption’s duration, affected services, business impact and mitigation costs. Review applicable supplier service-credit provisions, contractual notification requirements and insurance terms promptly, including any claim deadlines or waiting periods. Do not assume that a non-malicious technical outage automatically qualifies for compensation or insurance cover.

How can we help you?
Help

How can we help you?

Subscribe: I'd like to keep in touch

If your enquiry is urgent please call +44 20 3321 7000

I'm a client

I'm looking for advice

Something else