Broadcom Oracle Licensing Case Study.

This case study describes the engagement, redacted to remove identifying client information, in which a major UK media group sat between a Broadcom subscription renewal and a live Oracle license review. Both publishers were applying pressure simultaneously. Either negotiation handled in isolation would have produced a poor outcome. Handled together, the same facts produced a defensible commercial close on both sides.

The client

A UK media group with editorial, broadcast, and digital distribution operations across the United Kingdom and continental Europe. Approximately fourteen thousand employees. Annual technology spend in the high three digit millions.

Oracle had been a strategic database supplier for fifteen years across newsroom systems, rights management, finance, and HR. VMware had been the strategic virtualisation platform for almost as long. The client had a competent Oracle licensing function and an experienced procurement team. They did not have the publisher side experience to fight the cases that arrived in the same quarter.

The problem

In Q1 of the engagement year the client received two letters. The first was from Oracle License Management Services confirming that the client had been selected for a license review across the Oracle Database estate. The letter referenced specific instances. It did not yet name VMware, but the supporting questionnaire was structured to elicit virtualisation evidence. Anyone who has read an Oracle audit pack from the last five years knew exactly where it was going.

The second letter was from Broadcom, with the standard subscription pricing schedule for the renewal of the client's VMware vSphere and vSAN deployment. The new subscription bundled vSphere Foundation across all sockets, regardless of feature use. The subscription quote was approximately four times the prior perpetual maintenance line. Renewal date was tight. The client had ninety days to commit before the existing entitlement expired.

If you do not control the sequence between Oracle's audit and Broadcom's renewal, the publishers will. We control the sequence.

The Oracle exposure

The client's Oracle Database estate was deployed across multiple vCenter clusters that had not been segmented along licensing boundaries. Affinity rules existed in some clusters but not others. Storage vMotion was enabled across all clusters.

The client had documented their licensing policy internally as restricting Oracle Database to specific hosts, but the documentation had not been kept current with the operational reality. Several clusters had hosts that could theoretically run an Oracle workload even though they never had.

If Oracle's License Management Services team had successfully argued that every host in every cluster where an Oracle workload could potentially run needed to be licensed for Oracle Database Enterprise Edition with the full processor metric, the gap between scenarios would have been the difference between a routine close and a balance sheet event.

The Broadcom renewal

Broadcom's pricing logic for the VMware portfolio is simple. Every socket gets a per core subscription regardless of which features the client wants to use. The cheapest tier, vSphere Foundation, included far more than the client had been running on the prior perpetual licenses. The most expensive tier, VMware Cloud Foundation, was being positioned aggressively for any client with a meaningful Oracle Database or other tier one workload.

The client's procurement team had already pushed back once. The second quote came back almost identical, with longer term length offered as the only commercial flex. The Broadcom account team had also begun to suggest, in writing, that maintaining tight Oracle compliance under VMware was easier on Cloud Foundation, where dedicated host capabilities and built in tooling could be presented to Oracle. That suggestion is one of the more impressive cross publisher maneuvers of the post acquisition era. It is also not a contractual commitment.

Our strategy

Our partner ran the engagement from London with daily contact through the in house Oracle and procurement teams. The engagement plan had four parallel tracks.

• Track one. Oracle position. Reconstruct an evidenced license position based on actual deployment, host pinning, and storage configuration. Document every affinity rule, every cluster boundary, every isolation control. Submit a detailed response to the LMS questionnaire in our preferred format, not theirs.
• Track two. Oracle commercial framing. Open a parallel commercial channel with the Oracle account team to size what a clean close would look like, separately from the audit track. Use our negotiation playbook to ensure both tracks could converge on a single close.
• Track three. VMware segmentation. Identify the smallest defensible cluster that could host every Oracle workload, with hard affinity rules, storage isolation, and audited evidence of exclusivity. Build the segmentation plan to be reversible if the commercial outcome required it.
• Track four. Broadcom commercial. Run the Broadcom subscription negotiation against a credible exit threat. Identify the workloads that could move to Hyper V, KVM, or Nutanix, the timeline cost of moving them, and the residual that had to stay on VMware. Present that residual as the negotiating envelope.

Each track was sequenced to the others. The Oracle position evidence was built in lockstep with the VMware segmentation so the same data underpinned both tracks. The Broadcom negotiation was deliberately paced to stay one step ahead of the Oracle audit close so the segmented cluster boundary was already in production before the Oracle position letter went out. Read more about the Broadcom audit and licensing patterns we encounter in 2026.

The outcome

Eleven weeks from kick off the client signed both deals.

The Oracle close was driven by the position letter that documented Oracle Database deployment on a single segmented cluster of twelve hosts, with hard affinity rules in place, storage isolation, and a maintained log of any rule modifications. The compliance position was bounded to those twelve hosts. The eighteen million dollar exposure scenario evaporated.

The Broadcom close was driven by a credible alternative quote from a non VMware platform sized to absorb the workloads that did not require VMware specific functionality. The Broadcom subscription was rebuilt around the same cluster footprint the Oracle close had locked in.

For the broader pattern see our Broadcom VMware transition case study and the Broadcom VMware Knowledge Hub. Read also our financial services Oracle vertical for a parallel two publisher pattern in banking.

Lessons for any enterprise running Oracle on VMware

Three observations from the engagement that apply to almost every enterprise running Oracle Database on VMware in 2026.

• The publishers do not coordinate. They do exploit each other's pressure. Broadcom will use Oracle compliance language in subscription positioning. Oracle will use VMware deployment patterns to size compliance demands. Treat them as one negotiation, not two.
• Documentation that is not maintained is not evidence. A licensing policy from 2018 that nobody has updated will not survive an Oracle position challenge. Maintain affinity rules, isolation controls, and the change log as a continuous discipline, not as an audit response artefact.
• The cluster boundary is the only durable defense. Once an Oracle workload could potentially have run on a host, Oracle will argue that it should be licensed. Hard segmentation, with audited evidence, is the only position that holds across audit cycles. Read the Oracle audit response playbook for the full evidentiary framework.

If you are looking at a similar two publisher pressure pattern, our Vendor Shield program provides always on cover for both Oracle and Broadcom audit and renewal events. Read also our Oracle Services and Broadcom Services overviews, the full case study library, and our blog for ongoing publisher movements. The Oracle CIO Playbook covers the broader executive frame.