Skip to content

Microsoft 365 Went Down for Days. Would Your Cyber Insurance Have Paid?

On November 12, 2026, Outlook stopped delivering mail. Teams calls dropped. Copilot went quiet. For millions of businesses around the world, a normal Wednesday turned into a day of refreshing browser tabs and wondering when work could start again. 

Nobody hacked Microsoft. There was no ransomware and no data breach. A software defect simply gave way under load, and the damage spread from there. Now the insurance industry is adding up the bill, and the early numbers are big enough that every business owner should take a fresh look at their cyber policy.

What happened

The Microsoft 365 outage began on November 12 and took down Outlook email, Teams and Copilot for users worldwide. On November 16, a Microsoft executive explained that several things went wrong at once. A hidden defect dating back to July was exposed when demand rose while server capacity was reduced, and the result was a chain reaction of failures. IT Pro reported that at one point more than 80% of the servers involved were not responding.

How much could it cost insurers?

Estimates vary a lot, which tells you how hard this kind of event is to measure:

  • Kovrr, a cyber risk modeling firm, put insured losses between $300 million and $1.4 billion, with a central estimate of about $700 million. That figure rests on roughly $16 billion in economic losses from lost productivity (as reported by The Insurer).
  • Morningstar DBRS, the credit rating agency, estimated global insured losses of $300 million to $500 million (as reported by Insurance Journal).

Why the wide range? Because the loss isn’t one big check. It’s thousands of smaller losses at thousands of companies, each depending on how much that business relied on Microsoft that week. A law firm that couldn’t email clients, a staffing agency that couldn’t run Teams interviews, a sales team that lost two days of follow-ups: individually modest, collectively enormous.

It’s not the first time, and it won’t be the last

Large tech outages are becoming a regular feature of doing business:

  • July 2024: A faulty CrowdStrike update crashed about 8.5 million Windows computers, grounding flights and disrupting hospitals.
  • October 2025: An Amazon Web Services outage knocked websites and apps offline around the world.
  • November 2026: Microsoft 365 goes down for days.

The pattern is clear. Most businesses now run on a handful of cloud providers, and when one of them stumbles, everyone downstream feels it. As one Burns & Wilcox broker put it, “You may outsource the technology, but you are not outsourcing the business risk.”

Will your cyber policy actually pay for this?

Maybe. It depends on details that most people never read until they need to file a claim. Here’s what to look for.

1. Dependent business interruption (DBI)

Standard business interruption coverage on a cyber policy usually responds when your systems go down. Dependent business interruption covers lost income when a vendor’s systems go down, such as Microsoft, AWS, your payroll provider or your practice management software. If your policy doesn’t include DBI, an outage like this one may not be covered at all.

2. System failure, not just cyberattacks

This is the big one. Some cyber policies only pay for interruptions caused by a security event, like a hack or malware. The Microsoft outage was a non-malicious technical failure. To be covered, your policy needs to include system failure (sometimes called non-malicious or operational failure), and it needs to extend that coverage to outsourced providers, not just your own network. Coverage for outages without a cyberattack is not automatic.

3. Waiting periods

Most cyber policies have a waiting period, a set number of hours your business must be down before income-loss coverage starts. Eight, twelve or even twenty-four hours is common. If the outage hit you for six hours and your waiting period is eight, there’s no claim. Many business owners don’t know this until the claim is denied.

4. Exclusions and sub-limits for widespread events

Insurers worry about one outage triggering claims from thousands of policyholders at once. As a result, some policies exclude or cap coverage for widespread infrastructure failures. Others offer DBI only at a much lower sub-limit than your main policy limit. Events like this one tend to reveal exactly where those gaps are.

5. You have to prove the loss

Being offline isn’t enough by itself. You’ll need to show a real financial loss, and payouts are generally based on lost net profit. That means records: revenue before, during and after the outage, and the extra expenses you paid to keep working. Some policies include a separate limit to pay a forensic accountant to calculate the loss for you. It’s worth asking whether yours does.

A newer option: parametric downtime insurance

Parametric coverage works differently. Instead of measuring your actual loss, it pays a pre-agreed amount when a named service (say, Microsoft 365 or AWS) is down long enough to hit the trigger. Waiting periods can be as short as two hours, and you may not need to prove lost income at all. It’s not a replacement for a solid cyber policy, but for businesses that live and die by one or two platforms, it can fill a real gap.

The good news: it’s a buyer’s market

Right now, cyber insurance is relatively buyer-friendly. Burns & Wilcox shared an example of a payment processor that got broader coverage and a lower premium, which dropped from $150,000 to $109,000. In other words, upgrading your coverage doesn’t have to cost more. Sometimes it costs less.

Your 5-minute checklist

  1. List your critical vendors. Email, file storage, payments, payroll, CRM, scheduling. Which ones would stop your business cold?
  2. Pull your cyber policy and look for “dependent business interruption” and “system failure.”
  3. Find the waiting period. Is it hours or days?
  4. Check for sub-limits and exclusions on vendor outages and widespread events.
  5. Have a backup plan. Know how you’ll keep serving customers if a key platform goes dark for two days.

If you got stuck at step 2, that’s normal. Cyber policies are written in dense language, and the differences between carriers are significant.

Let us compare it for you

At Paperless Insurance Services, we can pull cyber liability proposals from 20+ carriers in about five minutes and show you side by side which ones cover dependent business interruption, system failure and vendor outages, and how long each waiting period is. Already have a policy? Send it over and we’ll review it with you. No jargon, no pressure.

Source: Burns & Wilcox, "Microsoft 365 Outage Could Trigger $1.4B in Insured Losses" (Nov. 18, 2026), citing Kovrr, Morningstar DBRS, IT Pro, The Insurer, Insurance Journal and NBC News. This article is for general information only. Coverage depends on your specific policy terms, conditions and exclusions.
Call us · (877) 239-0067