This is Part 3 of our four-part series examining Broadcom’s acquisition of VMware, the disorienting changes that followed, the legal and regulatory matters that came after, and what VMware customers should do to protect themselves.
As we shared in Parts 1 and 2, many long-term customers saw their reliable and steadfast relationship with VMware take an abrupt about-face after Broadcom acquired the near-ubiquitous virtualization technology company. What had once seemed predictable was now anything but, and what lay ahead was fraught with risks. Almost overnight, the world of software licensing changed.
In Part 2, we examined Broadcom’s seismic decision to shift from VMware’s traditional perpetual-license model to subscriptions while simultaneously drastically reducing the availability of individual software products in favor of cumbersome software bundles. We also looked at what happens when support expires, how these changes raise important questions about what rights customers continue to have under their existing agreements, and what happens when Broadcom challenges those rights.
In this Part 3, we address the legal and regulatory landscape.
In some ways, aggressive and mercurial auditing and licensing scripts are nothing new. As one example of many, we have written endlessly about our extensive experiences countering Oracle’s deeply unpopular market behavior. However, with Oracle and many other vendors, the licensee shouldn’t necessarily worry that contentious litigation is imminent. There are exceptions, of course, but we have observed that litigating against its licensees has not emerged in Oracle’s market behavior.
Not so regarding Broadcom’s conduct in the marketplace. As we detail below, Broadcom has aggressively pursued litigation against its licensees, thereby sending a clear message to the market that it can be very costly to defend your company’s contractual rights.
Indeed, the disputes between Broadcom and VMware customers are increasingly moving outside the commercial world of negotiations and audit responses, and making their way into court, allowing judges to take a closer look at what Broadcom’s licensing changes really mean for existing agreements.
Taken together, these cases illustrate a massive range of legal and commercial issues customers might face as they navigate Broadcom’s post-acquisition VMware strategy.
But one thing is abundantly clear. Every company interfacing with Broadcom regarding VMware or CA agreements must have a litigation-avoidance strategy. What follows is a compendium and table reflecting the already burgeoning litigation ignited by Broadcom against its licensees.
T-Mobile went to court after Broadcom refused to honor what T-Mobile contended was its contractual right to extend support for its VMware perpetual licenses. T-Mobile argued that its existing agreements entitled it to an additional year of support, while Broadcom disputed that interpretation. In 2025, the court granted T-Mobile preliminary relief requiring Broadcom to continue providing support, and in April 2026, a New York appellate court affirmed that relief.
In the UK in September 2025, Tesco brought a major lawsuit against Broadcom and VMware arising from changes to its VMware licensing and support arrangements. Tesco alleges that it purchased perpetual VMware licenses with support commitments extending for years, only to face significant changes following Broadcom’s acquisition. Tesco is seeking more than £100 million in damages and has begun moving approximately 40,000 servers away from VMware. The case remains ongoing.
The Allstate litigation illustrates another side of Broadcom’s post-acquisition approach: software licensing audits. VMware sued Allstate in December 2025 after Allstate allegedly failed to comply with an audit. In a June 2026 court filing, Allstate argued that the audit was retaliatory, initiated by Broadcom after Allstate decided to stop doing business with Broadcom’s VMware and CA businesses. The case was referred to private ADR in March 2026 and remains ongoing.
A Dutch court confronted yet another issue in litigation involving Rijkswaterstaat, the Netherlands’ government agency responsible for water management and infrastructure. After Broadcom’s changes to VMware’s licensing model, Rijkswaterstaat faced a substantial increase in costs and sought continued support while it transitioned away from VMware.
In June 2025, the District Court of The Hague ordered VMware and Broadcom to continue providing support for up to two years to give the agency time to complete its migration.
Broadcom/VMware is also suing VMware customers over alleged licensing violations, and the VMware v. Siemens litigation is a good example. Here, VMware is the plaintiff and alleges that Siemens was using VMware software beyond its licensed entitlements and refused to cooperate with an audit. Siemens has disputed VMware’s position and challenged, among other things, whether the case belongs in a U.S. court.
In February 2026, a magistrate judge provisionally denied Siemens’ request to transfer the case to Germany while recommending dismissal of Siemens AG for lack of personal jurisdiction.
Two other disputes ended in settlement rather than a court ruling. In August 2024, AT&T sued over VMware support and licensing rights after Broadcom sought to end support for certain legacy products. In November 2025, Fidelity alleged Broadcom threatened to cut off access to software critical to its operations. Both matters ultimately settled (AT&T in November 2024 and Fidelity in January 2026), with the terms of the AT&T settlement remaining confidential and Broadcom agreeing to continue providing software and services to a Fidelity subsidiary in the Fidelity matter.
European regulators and industry groups are also examining the broader competitive implications of Broadcom’s changes to the VMware business model.
In March 2026, the Cloud Infrastructure Services Providers in Europe (CISPE) filed a competition complaint with the European Commission concerning Broadcom’s changes to VMware’s cloud service provider ecosystem. CISPE and other European business groups have since asked the Commission for interim measures and a transition period, arguing that Broadcom’s changes have increased costs and restricted competition. Broadcom disputes those allegations.
In August 2026, the EU General Court rejected Broadcom’s request for interim relief in connection with the Commission’s investigation.
We have included the table below to clearly show each case and the parties involved, the venues, the allegations and/or issues asserted, and the current status of each case.
| Case / Parties | Venue | Allegations / Issues Asserted | Status (November 2026) |
| T-Mobile v. Broadcom — T-Mobile USA, Inc. and Broadcom/VMware entities | New York state courts | T-Mobile alleges that Broadcom breached existing contractual commitments by refusing to honor its right to extend support for perpetual VMware licenses. | T-Mobile obtained preliminary relief in 2025 requiring continued support. A New York appellate court affirmed the relief in April 2026. The injunction was scheduled to expire August 3, 2026. T-Mobile is transitioning approximately 303,000 VMware processor cores away from VMware. |
| Tesco v. Broadcom/VMware — Tesco plc and Broadcom/VMware entities | United Kingdom courts | Tesco alleges that Broadcom changed VMware licensing and support arrangements, increased pricing by approximately 175%, and failed to honor existing support commitments. Tesco also challenges the costs associated with migrating away from VMware and CA Technologies mainframe software. | Tesco is seeking more than £100 million in damages and migrating approximately 40,000 servers. Trial is expected between November 2027 and February 2028. |
| VMware v. Allstate — VMware, Inc. and Allstate | U.S. federal court | VMware alleges that Allstate failed to comply with a software licensing audit. Allstate argues that the audit followed its decision to discontinue business relationships with Broadcom's VMware and CA businesses. | Discovery is underway, and the parties have pursued alternative dispute resolution. Dispositive motions are scheduled for 2027. No publicly verified final resolution has emerged. |
| CA Technologies v. Allstate — CA Technologies and affiliated entities and Allstate | U.S. federal court | Separate contractual allegations involving CA Technologies software and issues arising from Allstate's sale of its Employer Voluntary Benefits business to StanCorp. | Separate litigation from the VMware audit dispute. The proceedings remain ongoing. |
| VMware v. Siemens — VMware, Inc. and Siemens entities | U.S. District Court for the District of Delaware | VMware alleges that Siemens used VMware software beyond its licensed entitlements and refused to cooperate with a licensing audit. Siemens disputes the allegations and challenges the appropriateness of litigating the dispute in the United States rather than Germany. | On September 30, 2026, the court rejected transfer to Germany but dismissed Siemens AG for lack of personal jurisdiction. The litigation continues against the remaining Siemens entities. |
| CISPE competition complaint concerning Broadcom's VMware business model — CISPE and supporting European business groups; Broadcom; European Commission | European Commission | CISPE alleges that Broadcom's changes to VMware's cloud service provider ecosystem increased costs and restricted competition. Broadcom disputes the allegations. | Filed in March 2026. In August 2026, the EU General Court rejected Broadcom's request for interim relief in connection with the Commission's investigation. The underlying competition issues remain unresolved. |
| CISPE and others v. European Commission — CISPE and supporting parties; European Commission; Broadcom | General Court of the European Union | Challenges the European Commission's original approval of Broadcom's acquisition of VMware. A related procedural dispute concerns Broadcom's request to identify CISPE members supporting the challenge. | On October 23, 2026, the EU General Court protected the identities of supporting CISPE members from disclosure to Broadcom. The underlying challenge to the acquisition approval remains unresolved. |
| AT&T v. Broadcom — AT&T and Broadcom/VMware entities | U.S. federal court | AT&T challenged Broadcom's efforts to discontinue support for certain legacy VMware products, alleging that doing so violated its existing VMware support and licensing rights. | Filed in August 2024 and settled in November 2024. The settlement terms remain confidential. |
| Fidelity v. Broadcom — Fidelity and Broadcom/VMware entities | U.S. federal court | Fidelity alleged that Broadcom threatened to cut off access to software critical to its business operations. | Settled in January 2026. Broadcom agreed to continue providing software and services to a Fidelity subsidiary. |
| Rijkswaterstaat v. Broadcom/VMware — Rijkswaterstaat and Broadcom/VMware entities | District Court of The Hague, Netherlands | Rijkswaterstaat challenged the consequences of Broadcom's changes to VMware's licensing model, which substantially increased its costs. The agency sought continued support while transitioning away from VMware. | In June 2025, the District Court of The Hague ordered VMware and Broadcom to continue providing support for up to two years to allow Rijkswaterstaat time to complete its migration. |
***
Taken together, these disputes demonstrate that the novel legal issues, and attendant risks to licensees, surrounding Broadcom/VMware go above and beyond the pricing of goods and services, and can actually involve a wide range of tripwires and landmines for VMware customers, including contract interpretation, support rights, audits, licensing compliance, migration, jurisdiction, and competition.
For customers navigating the Broadcom/VMware transition, it is best to address legal concerns before a licensing issue turns into a contentious dispute. Litigation avoidance can be tricky, especially with a vendor that, at least on the surface, doesn’t worry about the expense and negative public perception of engaging in litigation. In our experience, the most crucial avoidance steps must be taken in the very early stages of the interaction. Waiting until things have escalated is hardly ever – if ever – the best time to find your way forward. In Part 4, we will provide our recommendations.
Published on November 18, 2026
Software licensors are known for vague contracts—they’ve made a business of it.
Read the latest industry news.