By David A. Gauntlett*
Introduction
The November 12, 2026 Microsoft 365 outage is estimated to have caused $7 to $17 billion in productivity loss, yet only $100 to $700 million is estimated to be recoverable.[1] The most applicable insurance coverage for the outage is a cyber policy, but Microsoft’s characterization of its malfunction and specific policy provisions may interact to narrowly preclude coverage.[2]
Applicable Coverage Under Cyber Policies
Cyber policies usually have a “trigger” for coverage. Even if policies include the now-common provisions for business interruption, the precise policy language for a cyber-event is commonly defined as a “security failure.” This language is often limited malware, unauthorized access, or unplanned outage. In contrast, Microsoft explains its outage was not a “security failure,” and instead originated from a defect in dormant code cascading into overloading its Exchange Online server. Microsoft’s description works counter to many insured’s interests as it does not constitute an effective “trigger” for coverage depending on a “security failure.” Indeed, creative workarounds for policyholders are significantly limited as many carriers added an endorsement for system overloads after a similar event from CrowdStrike in July 2024.
The recoverable loss from cyber policies is usually linked to first-party business interruption—meaning the technology failure must be the insured’s own systems, not Microsoft’s. Possible carve outs include how a “systems provider” is defined in the respective policy. For example, some cyber carriers offer blanket insurance for “outsourced service providers” and others require a third-party provider to be under a written contract. But again after the CrowdStrike outage in 2024, many carriers introduced sub-limits or exclusions for “widespread” events, which the Microsoft 365 outage may fall into. This does not mean, however, there is no recoverable loss where those sub-limits exist. The newly-crafted endorsements have never been tested in court, and their application may vary on jurisdiction.
Timing of the outage can pose a different challenge on an insured’s recoverable loss and. To begin, policies can impose an eight to twenty-four hour minimum waiting period in order to trigger coverage. Whether policy benefits are available for the entire outage, or only the time after the waiting period depends on the language. Furthermore, if the loss fell outside of business hours, it may not qualify as a business interruption. For most United-States-based companies, this is not a challenge as the outage fell in the middle of a workday. However, businesses with overseas branches, overnight shifts, or 24-hour healthcare facilities must present evidence their loss is real.
The restoration efforts of Microsoft will also be the subject of scrutiny when determining policy benefits. Most cyber coverage considers partially restored systems as a continued “interruption” and the claim period continues through the complete restoration. Insurers may argue, however, that a partial interruption could have been mitigated by workarounds that a company chose not to pursue. Microsoft’s own report states that Teams functioned for most of the outage; SharePoint, OneDrive, and Office apps were restored sooner; but Online Exchange was not available as all. This report positions insurers to argue not about the duration of the outage or restoration efforts, but instead about the viable alternatives for insureds.
Applicable Coverage Under Traditional Property and Business Interruption Policies
While not as tailored for online system failures, traditional property and business interruption insureds may be eager to apply for coverage. These claims, however, come with their own challenges.
Microsoft’s description of the outage as a “defect” of latent code will likely support insurers precluding coverage under property policies. Nationwide, the most recent precedent for property insurance is to apply it strictly to “direct physical loss or damage.” A cyber event does not fit the bill. Moreover, faulty design or unrecognized defects are common exclusions in traditional policies. These exclusions have been challenged in the past with creative workarounds, including service interruption or computer systems damage. But, these exclusively apply to loss of electricity or functionality of electric data.
In contrast these property policies, business interruption policies occasionally contain provisions for “dependent properties” that insure businesses dependent on a supplier. A successful claim may be built on the company’s service chain and describe which services they rely on for their operations. This strategy, however, is entirely fact-dependent and requires careful review of the policy and the business.
Despite this clear path to coverage with the right business interruption insurance, insurers are often quick to deny claims by reflex. The case of DeVaughn James, LLC v. Palomar Excess and Surplus Ins. Co.[3] is illustrative for digital law firms in ransomware attacks that materially affect business. There, the insured was a “paperless” law firm where “client files, case documentation, legal work, and communications are maintained, processed, and transmitted digitally.”[4] Because the law firm operates in that manner, a ransomware attack compromised many of the firm’s critical systems.
According to the complaint, “they were essentially unusable from Monday, August 4, 2025, through Friday, August 8, 2025. Plaintiff’s computer system was only partially operational on Monday, August 11 and Tuesday, August 12, 2025.”[5] Despite the firm’s complete shutdown for an entire week and reduced capacity for two additional days, the insurer maintained that the firm “suffered absolutely no loss of profit.”[6] This complaint, while applying to ransomware attacks and not system failures, was still litigated by the insurer with a much more obvious interruption to business and covered malware attack. Insurers often present an uphill battle for insureds seeking policy benefits, even when the facts work to their advantage.
Coverage Beyond Business Operations: Applicable Coverage for Customer Claims
The Exchange Online communication failure cascaded into interrupted messages with vendors, firms, service providers, or deliveries. These failures are not contained within a company, but affect outside individuals and risk third-party claims for the failure to render professional services.
The most applicable insurance policies for this type of loss are technology errors and omissions, as well as a professional liability. Collecting the applicable policy benefits demands early notice to insurers as most of these policies are claims-made and later reporting can exclude coverage if the policy period has already lapsed. A customer complaint or demand letter may count as a claim and trigger a mandatory reporting period. Insureds must also review the exclusions carefully for service-level liability, third-party technology failures, or failure to perform a contract as all may be applied to the Microsoft outage.
Directors and officers coverage may apply to some public companies that suffered material disruption if their customers claim they misrepresented their technological resilience. These policies advantageously lack a waiting period and physical damage requirement, but their applicability has not been tested in court.
The last, yet most common, general liability insurance coverage is often not suited for cyber events as exclusions for lack of bodily injury or property damage can defeat many claims. This does not mean they should be automatically ruled out as some companies, such as healthcare providers, may suffer downstream effects of the loss that result in an insurable bodily injury claim.
Microsoft Commercial Agreements and Their Effect on Recovery
Microsoft’s licensing agreements typically limit recovery against any system failure to “service credits.” Business may still pursue these “service credits,” but it is not likely they will approach comparable compensation to an insurance policy. Moreover, if the service credits are pursued in addition to insurance, the policy must be checked to see if their value will be deducted from any insured loss.
The report from Microsoft positions itself as not liable for recovery. It details the defect passed safe deployment for three months, the cascading effect occurred due to routine operations, and had these effects not coincided it would have been harmless. The report does acknowledge failure in the load testing and bulkhead containment, which will likely become the focus of any claim against Microsoft.
Conclusion
The Microsoft 365 Exchange Online outage cascaded into a system failure affecting millions of businesses across 74 countries for nearly 36 hours. The subsequent loss of communication and online software affected many public-facing industries exposing them to third-party claims and is estimated to cause billions in lost revenue. Because the exposure is so varied across each industry, review of potential insurance coverage will require careful analysis of insurance agreements and a company’s reliance on different Microsoft products. An avenue of recovery precluded for one company may be available for another under the same policy depending on how its claim construed. As such, it remains important to invest in the appropriate consultant or lawyer to provide expert analysis on the applicability of a policy to viable loss.
*David A. Gauntlett is a principal of Gauntlett Law and represents policyholders in insurance coverage disputes regarding intellectual property, antitrust, and business tort claims, as well as in the underlying actions. Mr. Gauntlett can be reached at (949) 514-5662 or dag@gauntlettlaw.com. For more information, visit Gauntlett Law at www.gauntlettlaw.com.
[1] Tim Keary. “Microsoft Outage Chaos Exposes The Risks Of Relying On One Cloud Provider” Forbes. www.forbes.com/sites/timkeary/2026/11/17/microsoft-outage-chaos-puts--operational-resilience-under-a-spotlight/
[2] Carlton Wilde III and George Buckley. “You Haven't Got Mail: Coverage Claims For Microsoft Outage.” Law360. hwww.law360.com/insurance/articles/2550169
[3] DeVaughn James, LLC v. Palomar Excess and Surplus Ins. Co., Case No. 2:26-cv-02064 (D. Kan., filed Feb. 2, 2026).
[4] Complaint, ¶ 19.
[5] Complaint, ¶ 18.
[6] Complaint, ¶ 25.