Blogpost

Microsoft 365 outage: Who can contact your crisis management team?

The Microsoft 365 outage, which lasted for hours on 12 and 13 November 2026, highlights just how reliant crisis communication is on standard tools. What can you do now?
18/11/26
15 views
7 minutes reading time
Risk Management
Microsoft 365 outage: Who can contact your crisis management team?
Contents

Included in this collection:

Open collection

A Microsoft 365 outage lasting several hours paralysed email, calendars and parts of Teams worldwide on 12 and 13 November 2026. The incident highlights just how reliant crisis communication is on standard tools. Find out what you can do now.

How do you contact your crisis management team today if email and Teams are down?

Standard tools are more than just productivity tools. They serve as a means of alerting staff, a basis for decision-making, a link to the supervisory body and, in some cases, the second factor in the login process.

Anyone, in an emergency, who relies solely on the very provider they are trying to restore has no fallback solution.

Under Article 5(2) of DORA, your management body is responsible for the ICT risk management framework. This includes regularly approving, monitoring and reviewing the business continuity policy as well as the response and recovery plans (point (e)).1 An initial test takes an hour: convene your crisis management team today without using email or Teams. Further steps and four questions can be found at the end of this article.

What happened

The outage began on Thursday, 12 November 2026. According to Downdetector, Outlook and other Microsoft 365 services, the AI assistant Copilot and the admin portal were affected in more than 70 countries.2 However, in many cases, it was only individual functions that were down: In Teams, scheduling meetings and calendar integrations in particular often did not work properly.3

During the outage, Microsoft explained that a number of servers had unexpectedly become unavailable, reportedly due to failed health checks, according to All About Security.4 The company cited a previous upgrade to network capacity as the cause: A problem introduced during this process only became apparent following recent network changes.5 According to Microsoft, there is no evidence of a cyberattack. For consumers, the services were fully operational again on Friday at around 5.10 pm (CET); for business customers, the backlog of emails first had to be processed.6

The outage disrupted fund management operations at securities firms, life insurers and investment companies in Taiwan. According to Reuters, one company cancelled a planned securities repurchase agreement, whilst another, according to insiders, reverted to using fax machines for stock market transactions. According to the Ministry of Digital Affairs, companies in Germany were affected across the board.7

The real risk: email as a gateway to critical applications

Business applications continued to run, but access failed due to the absence of the link required to log in. In a financial institution’s loan processing system, the application was running, but it had to be accessed via a transaction-specific link in an email (multi-factor authentication), which did not arrive. It is not possible to sign in, even though the application is running. Such dependencies are not included in any process model; they are usually only discovered when a problem arises.

Why this is a BCM, DORA and regulatory issue

If email is used not only for communication but also as a source of two-factor authentication during login, it can thereby block critical process steps. If the application in question is not included in your Business Impact Analysis (BIA), this dependency remains hidden. Consequently, business continuity plans will fail to identify emergency procedures. This level of detail must therefore be taken into account in the BIA and emergency planning.

Fundamentally, crisis communication is not an optional extra. DORA requires that crisis communication plans not only be established but also tested, in such a way that the tests challenge the assumptions underlying the business continuity plans, including the crisis communication plans.8 A plan whose communication relies on Outlook and Teams is unlikely to pass this test.

Microsoft is one of the 19 critical third-party ICT service providers designated by the EBA, EIOPA and ESMA in November 2025.9 Following the classification of M365 in the information register10, auditors will enquire about the reporting obligation and a tested fallback channel. The relevant questions can be found at the end of this article.

How much does such an outage cost?

There is no exact figure, but here is a point of reference: following the CrowdStrike outage in 2024, Parametrix estimated the direct losses to US Fortune 500 companies at 5.4 billion US dollars.11 In Germany, according to the BSI and Bitkom, just under half of the affected companies had to temporarily suspend operations, for an average of ten hours.12

A useful scenario for your organisation is as follows: hours of downtime multiplied by the number of affected processes multiplied by the value added per hour, plus additional costs and consequential losses. In operational risk (OpRisk), this incident falls under the event category ‘Business Disruption and System Failures’ and should be assessed in your scenario analysis. It is not the exact figure that matters, but the order of magnitude: only if you know what an hour without email and Teams costs your processes a weigh up of a fallback channel against the potential damage can be done.

The fallback channel: what it offers and what it costs

A fallback channel that operates independently of your primary provider relieves your crisis management team of two burdens: they do not have to set anything up from scratch under pressure, as users, contact lists and access rights are already in place. And it allows for realistic drills. Euronext demonstrated how this works in practice: the stock exchange operator asked companies to report important information and urgent matters, such as trading suspensions, by telephone.13 The telephone is the simplest fallback channel.

There is a cost involved: running a parallel system incurs costs for licences, maintenance and attention, and it only works if those involved actually use it. Not every organisation needs the highest level:

Level

Meaning Effort Focus
Cold

 Emergency contacts and documentation outside your M365 environment (tenant), telephone bridge. Must be activated in the event of an emergency.

Low organisational
Warm

Independent fallback channel set up, crisis management team registered, tested regularly. Routine is only established through drills.

Medium organisational and technical
Active

Fallback channel operates as part of day-to-day operations, with its own access credentials and login procedures. Parallel operation and ongoing maintenance.

High technical

Which level is appropriate depends on the criticality of your processes and your recovery objectives. This is a matter for the business impact analysis, not something to be addressed at the start of a procurement project.

One provider for everything? Following the outage, the Ministry for Digital Affairs stated that redundancies and alternatives are needed to fall back on in the event of a failure, whilst Bitkom and DIHK are calling for greater digital resilience.14

Our position: Not every service needs a second provider; this increases complexity, costs and the number of interfaces. However, your fallback channel should not depend on the same provider and the same login procedures as your office IT. Sovereignty solutions do not automatically resolve this; they address control and data sovereignty, not availability.

What you can do now

Three steps that require little effort and provide clarity quickly. The time estimates are based on our experience.

  1. Convene the crisis management team without standard tools (approx. 60 minutes). Alert the members without using email or Teams, for example by telephone or via your fallback channel. Make a note of: who could be reached, how long did it take, and where were numbers or access details missing?
  2. Retrieve emergency documents and access credentials from the tenant (a few days). Contact lists for the crisis management team, the regulatory authority and key service providers, the crisis manual and templates for customer notifications should be stored in a single location that is accessible even without M365 – either offline or in printed form. Also check which critical accounts receive two-factor authentication via email and provide an alternative for these.
  3. Table-top exercise with senior management (approx. 90 minutes). Scenario: Mail, Calendar and Teams are down for 24 hours. Check who makes which decisions: reporting to the supervisory authority, customer communications, time-critical business matters.

The result shows which level of the fallback channel your institution requires.

Conclusion

The technical cause is of secondary importance to your resilience. What matters is whether your organisation remains capable of functioning if a key service is unavailable, even if the specialist applications themselves are still running. No provider can answer this for you; it must be regulated, resourced and practised within your BCM.

Four questions you should be asking yourself right now

  1. Where do you stand? Do you know which core processes and crisis roles rely on email and Teams – whether as a link, a notification or a second factor in the login process – and does the classification of M365 in the information register reflect this?
  2. Is your emergency documentation stored in the same tenant that could fail?
  3. Would a failure of this kind have triggered a reporting obligation for your organisation, and who decides this if the primary channels are unavailable?
  4. Have you ever worked out what 24 hours without email and Teams would cost your organisation?

How we support you

The dependencies that this outage has brought to light – the link in the email, two-factor authentication via email – do not feature in any process model. They can only be identified by specifically looking for them. Together with you we can perform a Communicaton Channel Dependency Check: a workshop involving BCM, IT, line organisations and senior management. You will receive an overview of which processes, crisis roles and login procedures rely on email and Teams, the gaps in relation to BCM and DORA requirements – including the classification of M365 in the information register – and prioritised measures.

Building on this, we support the business impact analysis, the risk analysis and the IT implementation in line with the protection objectives, as well as the selection of your fallback channel – from consultancy through to implementation. msg provides independent advice: the selection is criteria-based and open-ended.

Get in touch with us. We’d be happy to arrange an initial meeting to discuss how the dependency check can be tailored to your organisation.

Harald Eisele | Head of Information Security | Harald-M.Eisele@msg.group

Thorsten Haß | BCM Expert | Thorsten.Hass@msg.group

Disclaimer: Our comments are non-binding and do not constitute legal advice. Each institution is responsible for its own assessment and implementation.

This article was produced with the support of Claude from Anthropic.

Quellen
  1. 1. Regulation (EU) 2022/2554 (DORA), Article 5(2), second subparagraph, point (e). EUR-Lex
  2. 2. ORF, 13 November 2026: Microsoft is still struggling to find a solution (Downdetector: 74 countries and regions).
  3. 3. Tagesschau, 14 November 2026, based on reports from Reuters, dpa and AFP: What is known about the Microsoft services outage.
  4. 4. All About Security, 13 November 2026: Microsoft 365 outage: Outlook, Exchange Online and Teams affected.
  5. 5. Microsoft, announcement on X (13 November 2026), reported by Tagesschau (14 November 2026) and Trending Topics (14 November 2026).
  6. 6. APA via Tiroler Tageszeitung, 14 November 2026: Global Microsoft outage: Services are up and running again, but the backlog of emails remains for the time being.
  7. 7. Reuters via onvista, 13 November 2026: A Microsoft glitch is causing disruption for companies and public authorities worldwide.
  8. 8. Regulation (EU) 2022/2554 (DORA), Article 11(2) and (6)(b), Article 14; Delegated Regulation (EU) 2024/1774 (technical regulatory standards, RTS, on the ICT risk management framework), Article 25. EUR-Lex.
  9. 9. EBA, EIOPA, ESMA, Pressemitteilung vom 18.11.2025: The European Supervisory Authorities designate critical ICT third-party providers under the Digital Operational Resilience Act.
  10. 10. (the DORA register of your ICT service providers),
  11. 11. Parametrix estimate, as reported by Claims Journal, 25 July 2024. The estimate relates to US corporations and an end-user device failure, not a cloud service such as M365, and illustrates the scale of the issue.
  12. 12. BSI and Bitkom, press release, September 2024: CrowdStrike: Consequences for businesses. Survey of 331 affected businesses; according to BSI and Bitkom, the sample is not representative.
  13. 13. Reuters via onvista, 13 November 2026: Stock exchange operator Euronext: Companies should use the telephone due to the Microsoft outage.
  14. 14. Reuters, 13 November 2026 (see footnote 7).
WORDPRESS_URL: https://admin.banking.vision/wp-json