The Microsoft 365 Outage - What DORA and the FCA Require

The Microsoft 365 outage of 12–13 November was a live test of incident reporting. Here's what DORA and the FCA's new regime require.
5 min read time

When Microsoft 365 went dark

On Thursday 12 November, Microsoft 365 started failing worldwide. Outlook, Teams, SharePoint, and more were degraded. Microsoft only reported broad recovery on the evening of Friday 13 November.

For most businesses it was a lost day. For lots of regulated financial services firms, it was also a live test. Under the EU's Digital Operational Resilience Act (DORA) and the UK's new incident reporting regime from March 2027, the question is not just "when will email come back?", it is "is this reportable and has our clock started?"

‍

Was it a major ICT-related incident?

If a provider's failure disrupts your services, it is your incident to classify.

In broad terms, an incident is major when it affects critical services and also crosses the thresholds for other criteria, such as:

  • Clients and counterparties affected
  • Duration and downtime
  • Geographical spread
  • Data, reputation and economic impact

The impact of the outage ran past 24 hours and had a large global impact. For most firms, the deciding question is whether email and Teams support a critical or important function. A firm that confirms trades, handles claims or serves clients by email may have to answer yes.

‍

The DORA reporting clock

Once an incident is classified as major, three reports go to your competent authority. The deadlines are set by Article 5 of Delegated Regulation (EU) 2025/301:

  • Initial notification - within 4 hours of classification as major, and no later than 24 hours after becoming aware of the incident. It covers what happened, the first view of the impact and the systems affected.
  • Intermediate report - within 72 hours of the initial notification, even if nothing has changed. Update it again whenever the status changes significantly. It covers the cause, classification details and estimated impact.
  • Final report - within one month of the latest intermediate report. It covers the root cause, lessons learned and actual costs.

Because the outage ran into a Friday, the weekend rule matters too. If a deadline falls on a weekend or bank holiday, many firms can file by noon on the next working day. That relief doesn't apply to initial or intermediate reports from credit institutions, central counterparties, trading venues and other entities identified as essential or important.

Note also that the 24-hour backstop runs from awareness, not classification. A firm that waited for Microsoft's root-cause statement before classifying the incident could already have missed the deadline.

‍

The UK clock from March 2027

UK firms will soon have a single regime of their own. The FCA's PS26/2, published with the PRA and Bank of England, applies from 18 March 2027.

An outage like this one would be reportable when a firm reasonably believes it risks intolerable harm to consumers, the firm's safety and soundness or market integrity. That threshold is judged on what the firm knows at the time.

  • Most FCA solo-regulated firms (standard report) - a single, limited submission within 24 hours of the threshold being met, with no later reports.
  • Firms in scope for enhanced reporting - an initial report as soon as practicable, and within 24 hours of the threshold determination. Intermediate updates follow as significant developments occur, and a final report is due within 30 working days of resolution, with a 60 working day long-stop.
  • Payment service providers - an initial report within 4 hours of first detecting the incident, with later reports depending on the firm's report type.

All reports go through FCA Connect, and each firm in a group files separately. Firms operating in both Ireland and the UK will need to run the DORA and UK clocks side by side for the same event.

‍

Outages and your obligations

A firm can outsource the mechanics of reporting but it stays fully responsible for classifying the incident and filing on time. That means working from Microsoft's Service Health updates and not waiting for a post-incident review that may take weeks.

The outage also tests the rest of your third-party risk framework. Your register of information should show which critical or important functions rely on Microsoft 365. Your exit and contingency plans should cover how you keep operating when it is unavailable. And the event is a reminder of the concentration risk DORA asks firms to assess. The UK is moving the same way from March 2027. Firms must keep a register of material third-party arrangements, file it annually through FCA RegData and notify the FCA of new or significantly changed material arrangements.

‍

Five questions to ask this week

  1. Did we log the outage as an incident and when did we become aware of it?
  2. Did we assess the outage against every regime we report under (DORA, the FCA, or both), and record the decision either way?
  3. If it was reportable, could we have filed on time? That means 4 hours from classification under DORA, or 24 hours under the FCA rules.
  4. Does our third-party register show which important services depend on Microsoft 365?
  5. Did our business continuity plan actually work without email and Teams?

If any answer is "we're not sure", now is the time to fix it. calQrisk brings incident logging, DORA classification, reporting deadlines and third-party registers together on one platform, so the clock never catches your team by surprise.

Next Steps

Learn more