General 13.11.2026

Webinar summary: The Microsoft outage and your cyber insurance.

Webinar summary: The Microsoft outage and your cyber insurance.

What happened

The outage came from several separate failures lining up:

  1. In July, Microsoft deployed a fix containing a bug. It was tested on infrastructure that didn’t reflect production, so the bug went undetected.
  2. The day before the outage, about 14% of Microsoft’s gateway servers went out of service, which was still within capacity headroom.
  3. Fifteen hours before the impact, a routine Microsoft Teams failover added load to the gateway serving Exchange Online and Outlook.
  4. Peak US traffic tipped the strained system over the edge, and overloaded servers shut down. At one stage about 80% of gateway servers were unresponsive.
  5. Recovery was slow because users kept sending emails, which queued up and flooded the servers each time Microsoft tried to bring them back.

The impact ran from Thursday evening through Friday. Outlook was down, Teams and Safe Links weren’t working properly, and some people couldn’t log in to other systems because their one-time passcodes arrive by email.

Questions and answers

If my business was affected by the outage, would my cyber policy be triggered?

Likely, yes. Cyber policies have two main triggers: the malicious trigger (ransomware, malware, unauthorised access) and the non-malicious trigger, often called system failure. System failure is usually defined as any unintentional or unplanned outage, which is what we would expect to respond here.

Which parts of the policy would respond?

Two insuring clauses. Business interruption covers loss of income after an outage of your own systems, plus extra expenses to reduce that loss. Dependent business interruption covers the same losses when a supplier you rely on, such as a technology provider like Microsoft, has the outage.

What could affect how a claim is paid?

First, the waiting period: the number of hours before business interruption cover starts. Good policies use 8 to 12 hours, but some competitor policies go up to 48 hours. This outage ran well past 8 to 12 hours. Second, and more importantly, there must be a provable loss. Email is rarely how businesses actually transact sales, so most losses are expected to be small, with more potential under extra expenses than lost income.

How do insurers calculate a business interruption loss?

The insurer usually pays for a forensic accountant to work with you to quantify the loss. They typically ask for three years of financial information plus your targets and budgets for the affected period, which together form a proof of loss statement for the insurer.

How can a business prepare for that in advance?

It varies by business. A restaurant or travel business taking bookings by email, for example, should be able to show typical bookings for the period and past booking data, alongside standard figures like revenue, profit and EBITDA.

From a security perspective, how can businesses be better prepared?

We recommend thinking about operational continuity:

  • Identify your critical business functions and the technology each depends on.
  • Find single points of failure, such as MFA codes delivered only by email.
  • Put alternatives in place before you need them. For a Microsoft-dependent business, that could be a ready-to-go Google Workspace.
  • Make sure you can still reach clients, patients or customers, including having their contact details outside the main system.

A detailed business continuity plan should cover all of this, and goes much further than the yes-or-no question insurers often ask.

What happens when one event affects thousands of policyholders at once?

We expect the same policy mechanics to apply, even at a much larger scale. During COVID, insurers disputed property claims where policies were silent on pandemics, but the courts sided with policyholders. There’s no sign of insurers trying to avoid claims for this outage.

Does the infrastructure exclusion apply?

No. The exclusion protects the market from catastrophic systemic events and usually covers three areas: power and utilities, financial market infrastructure, and internet infrastructure. The internet part usually requires an impact on core DNS root servers or the IP addressing system, and there’s no evidence of that here. Microsoft’s services are also not the kind of underlying infrastructure the exclusion is aimed at.

Will this outage push up cyber premiums?

We don’t expect it to. Realistic estimates put insured losses at roughly 30 million to 150 million, which is the kind of event insurers already price in. The contrarian view is that reinsurers fear a cloud provider outage more than anything, so some could get cold feet. But we don’t expect that to happen.

What if we switched off MFA to keep working during the outage?

Some businesses used email-based MFA for non-Microsoft apps and couldn’t log in, so they disabled it. Making that risk decision quickly is a sign of a mature organisation. But because policies are built on the controls you declared, removing MFA could amount to a misrepresentation of risk if an attack follows. Our advice: contact your broker as soon as possible so the insurer can give its position before you decide.

If a breach followed, would it count as the same claim as the outage?

It depends on the policy wording, and there are arguments both ways. It could be one claim, because the outage was the proximate cause. Or it could be treated separately, because the breach was caused by the change in security rather than the outage itself. Either way, the key step is telling your insurer, through your broker, so they’re comfortable with the risk.

 

Latest articles

Be an insider. Sign up now!