Why the CISPE Filing Is Not Your VMware License Position
A CISPE VMware license position is not a Brussels filing. CISPE filed a competition complaint with the European Commission on 19 March 2026 and asked for interim measures to halt Broadcom’s termination of the VMware Cloud Service Provider program in Europe. CISPE alleges price hikes, bundling, upfront payment, and minimum commitments based on potential rather than actual use: “which cumulatively have increased costs by more than 1,000 percent.” The January 2026 decision, it says, “removed all but a tiny minority of hand selected partners.” Broadcom disputes the framing. None of that is a VMware license position.
That’s the problem.
The parent pack is the VMware Broadcom stay vs exit page: perpetual versus VCF, the support path, portable VCF on AVS, and third-party cover.
This is not a Brussels briefing you can leave with legal. The CISPE filing does not name the partner who can still transact. If your hosted VMware still sits with a CSP that lost authorization, the next conversation is who can sell you the product in the EU, on what bundle, and whether the commitment is sized to what you run.
The complaint is not a stay of your seller list
Cloud Infrastructure Service Providers in Europe (the trade body for European infrastructure providers) called the VCSP termination a threat to European CSPs and to the customers who buy through them. It is CISPE’s second complaint against a US vendor over software licensing terms in the European cloud market. The association asked DG Competition, as a minimum, to suspend the VCSP termination and readmit European providers; to restore the white-label program Broadcom axed in 2025; and to put protections against retaliation, with fines for non-compliance.
Francisco Mingorance, CISPE secretary general, said cloud providers and their customers are being “irreparably damaged by Broadcom’s unfair actions, which we believe are illegal,” and that Broadcom is applying the “coup de grâce.”
Treat that as the filer’s case, not as a ruling. A complaint is receipt. Interim measures have not landed until the Commission says they have. Do not brief the CIO as if they have.
The January signal that closed the European VCSP program is a different event from this March filing. After the remaining transaction window, only a select group can sell VMware subscriptions, standalone or inside a broader service. CISPE’s earlier challenge to the Commission’s clearance of the VMware purchase is another event again. None of those filings is a purchase order.
You do not need to pick a side. You need a named seller.
Who can still sell you VMware in the EU
Your SAM job this week is three names. Who is on the invoice. Who is still authorized to sell you VMware in the EU. Who takes the estate if the first name is not on the second list. Treat any published slice of remaining providers as a reported sample (not as your list until you have it in writing for your country and your SKU).
If your invoice still carries last year’s CSP, that is a reporting layer. Keeping the lights on through a remaining term is not the same as being able to grow or renew on that partner. CISPE’s case is that many European CSPs lose the right to sell the product at all. Those built around VMware must hand customers to another authorized supplier or migrate.
That is a channel argument. You still have to run the estate.
Picture your procurement director, sixty days from a VMware conversation. Legal has the CISPE PDF. Finance has last year’s CSP invoice. Infrastructure has a host list. If the pack cannot answer who is authorized, what is bundled, and what is committed versus deployed, you do not have a VMware position. You have a Brussels headline.
Bundling is a position problem, not a catalog preference
CISPE’s complaint puts bundling on the record: products sold regardless of customer need, on top of the VCSP cut. Since Broadcom completed the VMware takeover, the commercial path for many estates has been a private-cloud stack rather than the SKUs they used to buy.
That is the SAM question, not the trade-association question. If the quote is a private-cloud stack you did not design, your job is not to decide whether Cloud Foundation is the right architecture. It is to know which SKUs you will operate, which you will pay for and park, and what that costs against the estate you already run.
A bundled line item is not a license position. vSphere you already deploy is not the VCF SKU list walking in with a retained partner. Subscriptions sold standalone and subscriptions sold as part of a broader service are not the same paper. If you cannot split deployed versus quoted in fifteen minutes, you will buy the frame the vendor brought.
This is not a criticism of the teams who kept the CSP relationship running. Traditional SAM tools were built to prove completeness, not to tell you whether the only authorized path is a narrower partner selling a wider bundle.
Potential use is not actual use
CISPE also put two commercial terms on the record: payment demanded upfront, and minimum commitments based on potential rather than actual consumption. Costs, it says, have risen more than tenfold.
Treat the 1,000 percent figure as CISPE’s allegation (not a measurement of your estate). It is a warning about the math in the next quote.
Potential-versus-actual is the interpretation work. A commitment sized to what you might host is not a position sized to what you host. If your file still says “we committed X because the partner said the capacity would land,” you have a forecast. You do not have an Effective License Position.
Upfront payment compresses the window. Cash leaves before consumption is proven. If you cannot reconcile cores, hosts, and VMs to the committed quantity before the prepay is signed, the vendor has already framed the year. Infrastructure Mapper is the topology layer for that host and VM count; RVTools and vCenter land on the same data sources page. A potential-use number looks like a forecast in a partner deck and like a floor in a contract. You need the floor, the deployed count, and the cash date on one page before anyone talks discount.
What to lock if your CSP is in the firing line
Produce a decision pack. Do not wait on Brussels.
| If this is your position | What is on the record | What you lock now |
|---|---|---|
| CSP lost authorization | After the VCSP cut, only a select group can sell VMware | Remaining term end date and a named retained seller |
| The quote is a bundle | Products bundled regardless of need | Deployed SKUs vs the quoted stack, not a VCF line as a proxy |
| Commitment sized to potential | Minimums on potential, not actual use | Actual cores, hosts, VMs vs the committed quantity |
| Payment demanded upfront | CISPE: payment demanded upfront | Cash date vs proven consumption |
| Waiting on Brussels | CISPE asked for interim measures | A filing is not a stay. Do not brief a ruling that was not issued |
Can a non-specialist brief the CIO in fifteen minutes from the pack? If not, you have a channel rumor, not a supplier position.
The decision layer, not another Brussels briefing
You already have invoices, a CMDB full of VMware records, and a partner name on the PO. The gap is not another inventory. The gap is a decision: who can still sell you VMware in the EU, whether the next authorized path is a bundle you did not design, and whether the commitment is sized to actual use. LICENSEWARE sits on the inventory and ITSM tools you already run. It is not a rip-and-replace SAM suite. It is a decision layer: what matters, why it matters now, what should happen next.
If a VMware renewal or audit is coming and your tools still need three weeks to turn “our CSP” into a named counterparty and a deployed-versus-committed count, book an Audit Readiness Review. You can start on the free plan and run the analysis on your own data.
The question to walk in with
Do not let anyone frame this as “Brussels will sort the channel.” The right question is: who is still authorized to sell us VMware in the EU, what the current term allows, and what a move to a retained VCSP (or a bundled Cloud Foundation quote) costs against this estate rather than a list price or a potential-use forecast. That is a data question, not a sales question.
CISPE asked for interim measures. Broadcom disputes the allegations. The Commission will assess the complaint under its procedures. None of that is your license position. The vendor will walk in with a number and a shorter partner list. The only question is whether you have yours first: current, defensible, and tied to the contract in front of you.
