Research note, November 2026
Microsoft 365 Mail Dependency and Cyber Insurance Accumulation Risk
What one week of Microsoft events shows about correlated exposure in a cyber insurance portfolio, and the five conditions that decide whether that exposure becomes insured loss.
Executive summary
Cyberwrite measured Microsoft 365 mail dependency across a random sample of 50,000 companies profiled on its platform. Microsoft Exchange Online hosts the mail of 50.1% of them. A failure of that one service is therefore a correlated exposure across a commercial cyber portfolio. Microsoft's preliminary post-incident report puts customer impact from the 12 November 2026 Microsoft 365 outage at just under 24 hours, longer than the 8 and 12 hour waiting periods brokers cite as typical. Whether that exposure becomes insured loss depends on five conditions that sit in each policy and in each insured's accounts.
Who this report is for
Cyber underwritersWhich single risks to follow up, and what to ask.
Portfolio and catastrophe risk managersHow much of a book one Microsoft event can reach.
ReinsurersCorrelated exposure across cedents and the stress test by duration.
BrokersThe policy terms that decide whether an outage becomes a claim.
CIOs and CISOsThe operational dependency and the actions to close it.
Boards and risk committeesThe questions to ask about cost and cover.
Key findings
- 50.1% dependency. Exchange Online mail hosting was detected at 25,059 of 50,000 sampled companies.
- Size and geography drive the spread. Detection ranges from 32% (revenue under $1M) to 64% ($50M to $250M), and from 31% to 71% across countries.
- The November outage passed common waiting periods. Microsoft's preliminary report puts customer impact at 23 hours 50 minutes, against 8 and 12 hour waiting periods commonly cited by brokers.
- Three exposure groups, three underwriting actions. 93 companies show a self-hosted Outlook Web App (OWA) login, 3,418 combine Exchange Online with other Microsoft cloud services, and 21,598 show Exchange Online for mail only.
- Loss is concentrated. In the stress test, 4% of Exchange Online companies (those with revenue of $1 billion or more) carry 71% to 73% of modeled business interruption loss.
- Exposure is not insured loss. Share affected, policy trigger, waiting period, provable income loss, and limits and retentions all sit between the footprint and a paid claim.
Inside the full research note
19 pages of exposure data, outage analysis and an upper-bound stress test. A preview of four pages:
What the full note adds
- Exposure by revenue band, country and sector
- The 2026 outage and attack timeline with sources
- Modeled and insured business interruption loss at 12, 24 and 48 hours
- Sensitivity to waiting periods and sublimits
- Loss concentration by company size, sector and country
- Credential attack scenarios
- Methodology, limitations and all sources
- What it means for CIOs and boards
Definitions
- Microsoft 365 mail dependency.
- In this research, a company's mail domain is hosted on Microsoft Exchange Online, as detected by external, non-intrusive scanning. The company depends on that service for mailbox access and mail flow, whichever mail client its staff use.
- Self-hosted Outlook Web App (OWA).
- An on-premises Exchange server with a public login page. It is reported as a separate group because it carries a different attack exposure.
- Accumulation risk.
- The risk that one event, such as the failure of a shared cloud provider, causes losses across many insureds in the same portfolio at the same time.
- Waiting period.
- The number of hours a business interruption must last before cyber business interruption cover responds.
- Contingent (dependent) business interruption.
- Cover for income loss caused by an outage at a third-party provider rather than at the insured itself.
What happened in November 2026
Mail risk arrived through two channels in the same week.
- 10 November. Microsoft patched an Outlook for Windows vulnerability (CVE-2026-124194) that attackers were already exploiting. It affects classic Outlook for Windows and exposes a user's NTLMv2 hash when a crafted message file is opened.
- 12 to 13 November. A Microsoft 365 outage (EX1550543 / MO1550821) began with Exchange Online. Microsoft's preliminary post-incident report puts customer impact from 16:20 UTC on 12 November to 16:10 UTC on 13 November, attributes it to a defect in a change to its network gateway servers, and reports no evidence of malicious activity.
- 13 November. Microsoft Threat Intelligence detected a phishing campaign that copied its service health notices and used the outage as a lure.
Earlier in 2026, Exchange Online outages ran about 10 hours (January, North America), 4 hours (March) and 15.4 hours to majority mail recovery (August to September). From July 2026, a Russia-aligned group exploited self-hosted Exchange through OWA.
What Cyberwrite measured
- Sample. 50,000 companies drawn at random from the Cyberwrite platform dataset and profiled January 2025 to October 2026, across 82 countries. Every scan predates the November events, so the sample measures dependency, not outage impact.
- Detection. Mail hosting and public login pages were identified by external, non-intrusive scanning. The mail client staff use and internal patch status are not visible from outside.
- Segmentation. Companies were grouped by revenue band, country, sector and Microsoft deployment pattern.
- Stress test. The platform's modeled business interruption figure for each company was applied to outage durations of 12, 24 and 48 hours, with illustrative policy terms. These figures are an upper bound and are not an estimate of the loss from the November outage.
Exposure concentration
| Segment | Exchange Online detection |
|---|---|
| All sampled companies | 50.1% |
| Revenue under $1M | 31.9% |
| Revenue $10M to $50M | 61.0% |
| Revenue $50M to $250M | 63.9% |
| Revenue over $1B | 50.8% |
| Australia (highest country) | 71.3% |
| United Kingdom | 66.1% |
| United States | 52.8% |
| Germany | 32.0% |
| Utilities and energy (highest sector) | 60.5% |
| Financial services | 59.9% |
| Technology | 45.0% |
Company size explains part of the country spread. Within the $10M to $50M band, detection is 47% in Germany and 60% in the United States. The ranking describes this sample and is not a market share estimate for any country.
Three exposure groups, three underwriting actions
| Group | Companies | What it means | Priority underwriting action |
|---|---|---|---|
| 1. Self-hosted OWA login | 93 | On-premises Exchange with a public login, the deployment targeted by the 2026 OWA campaign | Confirm the July 2026 Exchange update; review add-in permissions and mailbox delegation |
| 2. Exchange Online plus other Microsoft cloud services | 3,418 | A Microsoft cloud failure could reach customer-facing systems as well as mail | Identify revenue systems on Microsoft cloud and failover in place |
| 3. Exchange Online, mail only | 21,598 | The observed dependency is mail | Ask how the business operates when mail is down, and whether revenue stops or is delayed |
The Outlook for Windows vulnerability cuts across all three groups, because external scanning cannot show which mail client is in use. Underwriters should confirm the November 2026 Office update and outbound NTLM and SMB blocking with the insured.
From footprint to insured loss: five conditions
- Share affected. Microsoft's preliminary report gives no share of customers affected.
- Policy trigger. The failure was non-malicious and sat with a third party. Some policies require a security failure; some limit dependent cover to named or non-IT suppliers.
- Waiting period. 8 to 12 hours is commonly cited. At 24 hours of outage, a 12 hour period leaves 12 covered hours and a 24 hour period leaves none.
- Provable income loss. Lost staff time alone does not establish income loss. Insurers are expected to test whether revenue was lost or only delayed.
- Limits and retention. Dependent business interruption is commonly sublimited, and a monetary retention can apply beside the waiting period.
What this means for insurers, reinsurers and brokers
Single-risk underwriting (Cyber Risk Assessment)
- Build a short follow-up list from self-hosted OWA detections instead of sending blanket questionnaires.
- Ask event-specific questions about the November Office update, NTLM and SMB blocking and MFA on mail.
- Ask how much revenue depends on email. External data shows the dependency, not its financial weight.
Portfolio accumulation (Cyber Catastrophe Modeling)
- Measure the Exchange Online share in your own portfolio.
- Inventory wordings by trigger, waiting period, contingent business interruption sublimit and retention.
- Review the largest insureds first, because a small share of large companies drives most modeled loss.
- For reinsurers, aggregate exposure across cedents, because the same company can sit in several portfolios.
What this means for CIOs and boards
The exposure that concerns insurers sits inside each company. About half of the sampled companies depend on one provider for mail, and the November outage ran for almost 24 hours. Whether that becomes a financial loss, and whether insurance pays for it, is decided inside each organization.
For CIOs and CISOs
- Map the revenue path. Identify which revenue processes stop when email stops, and which are only delayed.
- Test a 24 hour outage. Walk through how orders, invoicing, customer service and approvals run without Exchange Online.
- Close the November exposure. Confirm the November 2026 Office security update and outbound NTLM and SMB blocking where classic Outlook for Windows is in use.
- Check self-hosted Exchange. If a public Outlook Web App login exists, confirm the July 2026 Exchange update and review mailbox and add-in permissions.
- Know the wider dependency. List the other Microsoft cloud services in customer-facing systems, and the failover for each.
Questions for the board
- What would a 24 hour Microsoft 365 outage cost us in lost income, not lost staff time?
- Does our cyber policy respond to a non-malicious failure at a provider, or only to a security failure?
- What is our waiting period, and how much of a 24 hour outage would fall inside it?
- Is our dependent business interruption sublimit enough against that loss?
- Which suppliers beyond Microsoft would stop our revenue if they failed?
Cyberwrite cyber risk quantification projects answer the first question for an individual organization, in dollar terms. Learn about cyber risk quantification
Get the full 19 page research note
Exposure data, outage analysis, the stress test and what it means for CIOs and boards.
FAQ
What share of companies depend on Microsoft 365 for email?
How long did the November 2026 Microsoft 365 outage last?
Was the November 2026 outage a cyberattack?
Does a cyber insurance policy cover a Microsoft 365 outage?
Why is a Microsoft 365 outage an accumulation risk for cyber insurers?
Is the Cyberwrite stress test an estimate of the November outage loss?
How can a carrier apply this analysis to its own book?
What should boards ask about Microsoft 365 dependency?
How does Cyberwrite detect Exchange Online without access to a company's systems?
Methodology and sources
Exposure figures come from a random sample of 50,000 companies with modeled loss figures, drawn from the Cyberwrite platform dataset and profiled January 2025 to October 2026. Detection is a lower bound. The sample's mix by country, size and sector reflects the platform dataset and is not market representative. Event facts are as reported up to 16 November 2026, including Microsoft's preliminary post-incident report, which may be revised. Full sources and methodology are listed in the research note.
Important notice. This article is for general information only. It is not underwriting, legal, actuarial, financial, insurance or investment advice. No individual company is identified. Microsoft, Microsoft 365, Exchange Online and Outlook are trademarks of Microsoft Corporation. All other trademarks, product names and company names are the property of their respective owners. Their use is for identification only and does not imply any affiliation with, or endorsement by, them.
About Cyberwrite
Cyberwrite is a cyber risk quantification company, founded in 2017 and headquartered in New York. Its platform profiles any of 320M+ companies on demand, in real time, for cyber insurance underwriting, cyber catastrophe modeling, cyber risk quantification (CRQ) and vendor risk management (VRM), serving insurers, reinsurers, brokers and corporates across 56 countries.