VMware is taking Allstate to federal court, accusing the insurer of obstructing a software licensing audit and ignoring key reporting and record-keeping duties.

In a filing dated December 15, 2025, in the United States District Court for the Northern District of California, VMware LLC lays out its side of a dispute with Allstate Insurance Company over how the carrier managed, reported and documented its use of VMware software.

The case centres on what VMware claims are breaches of a long‑standing licensing framework that includes a Master End User License Agreement, an Enterprise License Agreement and an amendment to that ELA.

According to the filing, VMware and Allstate entered into a Master End User License Agreement on December 12, 2008. VMware says Section 3.8 of that agreement, titled “Audit Rights,” requires Allstate to maintain accurate records of its use of VMware software for at least two years from the last day on which support and subscription services expired for the applicable software.

The same provision, VMware says, allows VMware or its designees to inspect Allstate’s records and computing devices to verify that the software was used in line with the contract and that all license and support fees were paid. If an audit shows an underpayment of more than 10% for the audited period, Allstate must repay the audit costs as well as any underpaid fees, according to the filing.

The dispute also involves what VMware calls the “ELA Contracts” — an Enterprise License Agreement executed on September 30, 2019, and Amendment No. 1 to that ELA signed on July 29, 2022. VMware says the ELA granted Allstate a license to use certain VMware software for a three‑year period and made clear that Allstate’s use of VMware software remained subject to the Master Agreement.

The 2022 amendment, VMware says, granted Allstate rights to additional VMware software and extended the ELA period to July 29, 2025. Under these agreements, VMware alleges, Allstate was required to report the total number of licenses it deployed on specified dates, to provide additional information reasonably requested to confirm compliance and to maintain accurate records sufficient to show that it and its affiliates followed the terms.

The relationship reportedly soured in 2025. VMware says that on March 4, 2025, it issued a formal audit notice to Allstate under the Master Agreement’s audit clause, telling Allstate that any changes in its environment during the license review process had to be reported promptly. After an introductory call, VMware emailed Allstate on April 11, 2025, saying that audit workstream teams would reach out to schedule kick‑offs. VMware’s audit partner, Connor Consulting, then contacted Allstate on April 16, 2025, and later held an audit kick‑off call on May 5, 2025, providing a technical questionnaire, a deployment detail workbook and scripts.

From there, VMware describes a pattern of delay. Connor Consulting followed up in May 2025, stressing the need to return the technical questionnaire to keep the audit on track. The filing says Allstate acknowledged receiving the materials but said it could not meet the requested timing.

VMware recounts further follow‑ups in May, June and July, including a July 22, 2025 update in which Allstate allegedly identified August 29, 2025 as its target date to return completed audit materials. When that date arrived, VMware says, Allstate still had not provided the promised information.

In September, things took a sharper turn. On September 12, 2025, according to VMware, Allstate told its consultant that VMware had been “removed from all devices” and that Allstate could not execute the scripts because they depended on “having VMware components running in the environment.” Allstate also said it had “no access to data” and was unable to populate the technical questionnaire, VMware says. Allstate did send a technical questionnaire for a “NatGen VMware ELA” environment, but VMware characterises it as “woefully incomplete.” A follow‑up email from VMware’s consultant on September 15, 2025, with additional questions, reportedly went unanswered.

On October 1, 2025, Allstate informed VMware that “all VMware instances have been terminated and removed from Allstate’s VMware ELA environment” and declared the audit “complete and satisfied, in compliance with the contractual entitlements, with no further action or obligation from Allstate,” the filing states. Allstate also redirected future correspondence to counsel.

VMware contends that terminating VMware instances and unilaterally declaring the audit complete does not relieve Allstate of its obligations to maintain accurate records, provide required deployment reports and permit an audit for the ELA period.

The company says Allstate’s conduct has impaired its ability to verify whether Allstate underpaid fees for the audited period or otherwise failed to comply with the agreements, and notes that if an audit reveals an underpayment of more than 10%, Allstate would be required to cover VMware’s audit costs in addition to any unpaid amounts.

VMware is asking the court for damages in an amount to be determined at trial, an order requiring Allstate to provide complete access to records, data, systems, computing devices and other materials necessary to verify compliance, and an injunction barring Allstate from destroying, altering or concealing relevant records. It is also seeking a declaratory judgement that the Master Agreement and ELA Contracts should be interpreted in line with VMware’s view and that Allstate’s contrary position is without merit.