Microsoft 365 outage triggers global disruption, limited insurance losses
A widespread Microsoft 365 outage caused severe operational disruption across multiple sectors for up to 38 hours.

A global Microsoft 365 outage caused widespread service disruption across healthcare, financial services, education and government sectors for approximately 18 hours of severe disruption and 38 hours total. The disruption, which began around 12:35pm US Eastern time on November 12, affected access to Outlook, Exchange Online, Teams, SharePoint, OneDrive, and Copilot. In the UK, hospitals, GP practices, schools and the Metropolitan Police reported difficulties accessing email and other services. By the morning of November 13, services were broadly but unevenly recovering. Marsh Re described the event as a significant but uneven disruption with broad geographic exposure and progressive recovery, noting that widely used technology can create global exposure.
Insurance loss estimates and market impact
Insurance industry estimates for the outage range from minimal to hundreds of millions of dollars, with most analysts expecting minimal market impact due to the short-term nature of losses. The figures from different analytics firms show a wide spread.
| Firm | Estimated Insured Loss |
|---|---|
| Morningstar DBRS | $300 million to $500 million |
| CyberCube | Less than $100 million (upper bound: $350 million) |
| Acrisure London Wholesale | Approximately $700 million |
CyberCube stated the outage was due to a technical issue during a network capacity upgrade, not cyber activity. The firm expects the event to have a loss ratio impact for cyber insurers of 0% to 2% of global cyber premium. Marsh Re said the impact on the insurance market was expected to be minimal, because most losses were likely to be short-term productivity and operational delays rather than business shutdowns. "Overall, the impact on the insurance market is expected to be minimal, with most losses likely limited to short-term productivity and operational delays," Marsh Re said. For comparison, CyberCube estimated the recent CrowdStrike outage's insured losses at $400 million to $1.5 billion.
Policy waiting periods and claim eligibility
The scale of any insured loss is highly dependent on the waiting periods set out in policies, which average around four hours for smaller organisations and 12 hours or more for larger ones. The outage, which lasted beyond 12 hours, exceeded the typical 8-12 hour waiting period for many businesses. However, for cover to be triggered, affected organisations must not only experience disruption beyond the applicable waiting period but also demonstrate an actual, documented loss of profit. Lara Wheeler, assistant vice president at Acrisure London Wholesale, said cyber policies typically cover business interruption from system failure, even without malicious activity.
Key factors affecting claim outcomes
Claim success depends on whether services were critical, waiting periods were exceeded, and policy terms cover non-malicious system failure. Marsh Re said losing email access was likely to have limited financial impact for most organisations, with bigger losses concentrated among those relying on Microsoft 365 for time-sensitive transactions or critical operations, such as financial services, healthcare and professional services. CyberCube noted email is not in the critical transaction path of most businesses. The first task for brokers is helping affected clients establish whether they have a claim: which services they relied on, how long they were impaired, whether that exceeded their waiting period, and whether they can document a real loss of profit. The bigger task is reviewing cover before the next outage, checking whether clients’ cyber policies cover non-malicious system failure, how contingent business interruption defines dependent providers, and whether waiting periods suit how dependent the business is on a single technology provider. Marsh Re stressed that the incident was not a general cloud infrastructure failure, which would typically cause broader and more simultaneous impacts, but it highlighted Microsoft’s dominance and the potential for a systemic event from a single point of failure.
Brokers must now help clients establish whether their reliance on these services exceeded policy waiting periods and document any actual profit loss to determine claim eligibility.





