Microsoft’s Email Outage Outlasted Common Waiting Periods. Proving Lost Income Decides Most Claims, Cyberwrite Says.

Estimated reading time: 7 minutes

Exchange Online was down for pretty much a full 24 hours from the 12th of November. That’s well past the 8 and 12-hour windows that brokers will typically cite. Whether it becomes an insured loss will depend on the policy wording and on proof of lost income, according to Cyberwrite CEO Nir Perry.

“Expected loss and maximum exposure are different questions,” said Nir Perry, Cyberwrite’s founder and chief executive.

Most users could not reach their mailboxes for nearly a day. Microsoft’s preliminary post-incident report puts customer impact from 11:20 a.m. Eastern time on Nov. 12 to 11:10 a.m. the next day, Cybersecurity News reported. That is 23 hours and 50 minutes.

The cause was a defect in a fix for Microsoft’s network gateway servers. At the worst point, more than 80% of those servers stopped responding. Teams, SharePoint, and other services tied to Exchange Online were hit too. Microsoft found no evidence of malicious activity, Cyberwrite’s research note says.

Attackers moved with the speed of light anyway. A day later, Microsoft was seeing phishing emails that were replicating the outage notices. These were warning that held messages would be deleted unless the recipient clicked on a link.

For the insurers, it’s a test of accumulation. One provider failure can impact a multitude of policyholders at the same time. CINI has looked at how the insurers go about modeling that risk.

How Far Microsoft 365 Mail Reaches

Cyberwrite sells cyber risk analytics to the insurers. They’ve scanned a random sample of 50,000 companies from the outside and found that Exchange Online was hosting mail at 50.1% of them (25,059).

Size made a difference. 32% of those under $1m in revenue used it. 64% of those between $50m and $250m did. By country, it varied from 31% in Spain to 71% in Australia. The US was at 53%, the UK at 66% and Canada at 56%.

A security gateway can hide the mail provider behind it. Cyberwrite’s detection goes right through the gateway, Perry said. Of the 2,867 companies we sampled that were using Proofpoint or Mimecast, it confirmed Exchange Online behind the gateway at 1,618 (56%).

It’s only the confirmed detections. Even if all the remaining gateway companies were running on Exchange Online the share would only be up to 52.6%, Perry said.

See also  What a Difference a Day Makes: Berkley Sues as a Cyber Insurance Subrogee to Recover Claim Settlement
Chart of four 2026 Microsoft Exchange Online outages in hours against 8 and 12 hour waiting periods, with the November outage running nearly 24 hours

Five Conditions Between A Microsoft 365 Outage And A Claim

Five conditions lie between shared exposure and insured loss according to the note. Those are the number of customers affected, the policy trigger, and the waiting period. Then you have the income the insured can demonstrate and the limits and retentions.

The Nov outage cleared the time test for a number of policies. At 24 hours you’ve got an 8 hour waiting period which leaves you with 16 hours of cover. 12 hour waiting period leaves you with 12.

It was the longest of the four Exchange Online outages this year (the note says). The August incident (which Cyberwrite attributes to a certificate management issue) lasted 15.4 hours before the majority of mail got back. CINI have previously written about how certificate failures can lead to outages.

Perry went in when a policy would cover an outage of this nature. The business interruption trigger would have to be for non-malicious system failure (not just a security failure). Dependent cover would have to cover technology providers in general rather than just the named suppliers. The outage would also have to go beyond the waiting period that applies to dependent cover.

“The answer differs by carrier and by wording,” Perry said.

What The Loss Estimates Say

Published estimates of insured loss are all over the place according to Cyberwrite’s compilation. CyberCube has it most likely below $100m with an upper end of $350m. Kovrr at $700m (range $300m to $1.4bn). Morningstar DBRS at $300m to $500m. Marsh Re has it as likely to be minimal.

The proportion of customers impacted will be the difference between the low and high estimates, Perry said. Microsoft’s final post-incident report will tell us. That report is due by 20th November.

Perry didn’t say whether carriers on the Cyberwrite platform have received the claims notifications. One broker did report having received them by the 13th of November.

Cyberwrite also did a stress test. They treated every sampled Exchange Online company as completely interrupted for 24 hours. Every hour without mail is an hour’s lost income. The modeled business interruption loss was $7.4 bn to $8.5 bn.

See also  Cyber Risk Analytics: Cyberwrite and Markel Expand AI Partnership in Europe

Under the illustrative policy terms and the published take-up rates, insured loss was $740m to $850m. The note refers to that as an upper bound rather than an estimate of the November loss.

The loss is very much concentrated. Of the companies in the Exchange Online group, those with $1 bn or more in revenue are just 4% of the group but account for 71- 73% of the modeled loss.

“Expected loss and maximum exposure are different questions,” Perry said. CyberCube and Marsh Re estimate expected claims, Perry said. The stress test is “deliberately set at full email dependency to show the ceiling a carrier needs to plan for.”

Where Email Sits In The Path Of Revenue

Published views are that the vast majority of companies will have carried on trading through the outage. Perry has identified the exceptions to that. They are the businesses where a transaction comes in by email and can’t wait a day:

  • Freight & logistics brokers taking same day bookings.
  • Wholesale distributors receiving purchase orders.
  • Professional and financial firms working to filing, closing or tender deadlines.
  • Insurance wholesalers and MGAs receiving submissions.

Marsh Re makes exactly the same point. There can be claims where the policyholder has relied on M365 for time sensitive or revenue generating work after the waiting period has elapsed.

The exposure goes beyond mail. Of the Exchange Online organizations, 3,418 also have other Microsoft cloud services running. There, a failure can propagate to customer-facing systems.

What CFOs And Boards Should Check

Perry’s checklist runs in order, to work through with a broker:

  • Trigger. Does business interruption cover respond to a system failure with no attack?
  • Dependent cover. Does that include cloud and technology providers? All of them or just the ones specifically named in the policy?
  • Waiting period. How many hours apply to dependent cover? Is there a further monetary retention on top?
  • Sublimit. Is the business interruption dependent on the policy capped at some amount below the full policy limit? At what amount?
  • Proof of loss. How does the policy deal with lost income? Does income which was delayed and subsequently earned count?
See also  Jaguar's New Tagline is "Copy Nothing," but its Cyber Insurance Disaster Suggests "Penny Wise, Pound Foolish" Might be More Apt

“The fifth point decides most outcomes for an email outage,” Perry said. “Lost staff time alone is not an insured loss.”

FAQ – Microsoft 365 Outage

How long did the Microsoft 365 outage last?

Microsoft’s preliminary report puts customer impact at 23 hours and 50 minutes, from Nov. 12 to Nov. 13. Its final report is due by Nov. 20.

Does cyber insurance cover a Microsoft 365 outage?

It depends on the policy. The trigger must include non-malicious system failure, dependent cover must reach technology providers, and the outage must pass the waiting period.

What is a waiting period in cyber insurance?

The number of hours an outage must run before business interruption cover starts. Brokers commonly cite 8 or 12 hours.

How many companies rely on Exchange Online for email?

Cyberwrite detected it at 50.1% of 50,000 sampled companies. The share ran from 31% in Spain to 71% in Australia.

How much insured loss could the outage cause?

Published estimates range from minimal to $1.4 billion. Cyberwrite’s upper-bound stress test is not an estimate of the actual loss.

What should CFOs check in their cyber policy?

The trigger, dependent cover, waiting period, sublimit and proof of loss. Lost staff time alone is not an insured loss.

Leave a Comment

×