What the Broadcom VMware compliance team is opening cases on in Q4 2026.

The Broadcom VMware compliance function is not a single team. It is a set of workflows that the Desk tracks by the kinds of cases that arrive at the buyer's procurement inbox. The mix of cases changes from quarter to quarter, partly because the team is reorganising internally and partly because the team works to a quarterly target that is set by what the commercial side wants to harvest. The Q4 2026 mix has narrowed against the Q3 mix in three ways. The cases are more product specific. The opening notices arrive earlier in the quarter. The remediation requests are more often framed as a true up against a specific entitlement line rather than a portfolio reconciliation.

The piece below describes the three case types that the Desk is seeing most often in Q4 2026 across the buyers we are tracking. None of the descriptions name a specific case or buyer. The purpose is to give the buyer side procurement team a reading of what the compliance workflow is staging into the quarter, so the buyer can prepare before the notice arrives rather than respond after.

Case type one. vSphere CPU undercount notices on dense estates

The most common case type this quarter is a vSphere CPU undercount notice. The notice asserts that the buyer's deployed physical CPU count exceeds the entitlement on record by a margin of 4 to 12 percent. The notices are concentrated on estates above 8,000 cores that have grown organically across the prior 18 months and have not refreshed the inventory record at the seller. The remediation request is a true up at the renewal rate against the delta, often with a request to extend the term by 12 to 24 months to absorb the true up across a longer commit window. The Desk has seen 14 such notices arrive at procurement inboxes between April and May 2026. The buyer can almost always reduce the asserted delta by 30 to 60 percent through a clean inventory pass, and can almost always decline the term extension without conceding the true up itself.

Case type two. Aria managed object overage notices

The second case type is an Aria Operations managed object overage. The notice asserts that the buyer's Aria entitlement covers fewer managed objects than the Aria deployment is actually managing in production. The notices are concentrated on buyers who moved from the legacy Aria perpetual licence into the subscription line in 2024 and have grown their telemetry surface since. The remediation request is a tier upgrade rather than a per object true up, which is materially more expensive per managed object than a per object true up would be. The Desk has seen 9 such notices arrive in Q2 2026 alone. The buyer can often hold the original tier by reducing the telemetry surface against non production objects, which is rarely litigated by the compliance team because the negotiation cost exceeds the additional revenue.

"The compliance workflow is not random. It targets the entitlements where the buyer's inventory record has decayed against the production reality. The buyer who refreshes the inventory before the notice arrives is rarely the buyer who receives the notice."Audit Lead, The Desk

Case type three. VCF bundle composition mismatch notices

The third case type is the newest. The notice asserts that the buyer is running a component of the VCF bundle in a configuration that does not match the bundle composition the buyer is entitled to. The most common variants are vSAN deployed at a capacity above the bundle's included tier, Aria Automation deployed against scopes outside the bundle's documented coverage, and Tanzu workloads running on infrastructure the bundle does not cover. The notice asks for a bundle upgrade rather than a per component true up, which raises the per core renewal rate across the entire estate rather than just the deviating component. The Desk has seen 6 such notices arrive in May 2026. The remediation pattern that has worked on the cohort is to renegotiate the bundle definition itself, on the same notice cycle, so the bundle the buyer is entitled to is updated to match the production reality without raising the per core rate across the unaffected portion of the estate.

What the three case types share

All three case types share the same opening move on the seller's side. The notice asserts an entitlement gap, presents a remediation that prices the gap at the renewal rate, and offers a settlement that combines the remediation with a renewal extension or a tier upgrade. The combined settlement is always priced higher than either the remediation or the renewal would be on its own, because the combination removes the buyer's ability to negotiate the two events independently. The remedy on the buyer side is to refuse the combination, settle the gap on its own merits at the prior rate, and treat the renewal or the upgrade as a separate conversation on a later calendar.

What we have seen on live deals this quarter

A regional insurer in North America received a vSphere CPU undercount notice in April asserting a 9.4 percent entitlement gap across an estate of 10,200 cores. A buyer side inventory pass conducted across three weeks resolved the asserted delta to 3.1 percent. The seller's combined settlement, which had bundled the true up with a 24 month renewal extension, was unwound. The true up was paid at the prior rate against the resolved delta. The renewal conversation was deferred to its scheduled quarter. The total cost the buyer paid was roughly 22 percent of the original combined settlement number, with no extension. A federal subcontractor received a VCF bundle composition mismatch notice in May. The remedy taken was to renegotiate the bundle definition to include the deviating Aria Automation scope without raising the per core rate across the unaffected portion of the estate. The renegotiation took five weeks. The cost effect of the original notice, as originally presented, was avoided in full.

The takeaway

• The Q4 2026 compliance mix is concentrated on vSphere CPU undercounts on dense estates, Aria managed object overages on post 2024 subscription migrations, and VCF bundle composition mismatches on production deviations.
• Every case type opens with a combined settlement that prices the gap at the renewal rate and folds the remediation into a renewal extension. Refuse the combination. Settle the gap on its own merits.
• The buyer who refreshes the inventory record against the production reality before the notice arrives is rarely the buyer who receives the notice. The compliance workflow targets decayed records, not deployed estates.