VMware

The one Aria Automation lever most VCF buyers do not pull.

Aria Automation is bundled into VCF on a per core basis. The licensing structure carries a buyer side mechanism most procurement teams have never read. It is documented. It is negotiable. It is rarely surfaced. This is the lever.

By The Negotiation Desk · VMware · Archetype: The Lever

Published 27 Dec 2025

The Aria Automation licensing schedule inside the VCF master agreement carries one paragraph that almost no procurement team surfaces in renewal conversations. The paragraph defines a workload classification framework that allows the buyer to designate categories of workloads as automation eligible or automation excluded, and to scale the Aria Automation entitlement to the automation eligible subset rather than to the full core count of the bundle. The framework was carried forward from the 2023 product structure into the 2026 VCF bundle. It still exists. It is still operative. It is rarely used because procurement teams do not read down to that paragraph, and because the seller's account team does not raise it. This article describes the framework, why it produces meaningful value, and how to land it on a current renewal.

The framework matters because VCF buyers routinely deploy Aria Automation across a much smaller subset of the estate than they deploy the rest of the bundle. The platform engineering tier of the estate is automation eligible. Production workload tiers are typically automation excluded by policy because the change control posture does not permit automated configuration changes against production workloads. The buyer is paying for Aria Automation across the full estate while the actual deployment is contained to a fraction of it. The framework restructures the entitlement to match deployment, without forcing the buyer to leave the VCF bundle structure.

What the framework actually says

The framework defines four workload classes by reference to the buyer's operational policy: development workloads, platform workloads, production workloads, and regulated workloads. Each class can be designated as automation eligible or automation excluded by the buyer at term start. The Aria Automation entitlement scales to the automation eligible subset rather than to the bundle total. The framework requires the buyer to maintain a workload classification register, audited annually, and to apply the classification consistently across the estate.

The framework does not require the seller's approval of individual classifications. It requires the buyer's classification to be policy backed and auditable. The seller retains the right to verify classification consistency through the standard usage measurement endpoints. The framework was added in 2023 as a buyer side concession when the bundle structure first introduced Aria Automation. It was not removed when Broadcom took ownership of the agreement. It remains in the current master agreement form.

Why the framework is rarely surfaced

Three reasons. First, the paragraph sits deep in the licensing schedule, after the entitlement table and after the support tier definitions, in a section that most procurement reviews treat as administrative reference material. Second, the seller's account team is not incentivised to raise it because applying the framework reduces the bundle's Aria Automation revenue. The framework is documented. It is not promoted. Third, the buyer side teams that would benefit from the framework, platform engineering and infrastructure operations, are not typically in the renewal conversation. The conversation runs between procurement and the seller's commercial counterpart, and neither party brings the framework into the room.

What the value looks like on a typical estate

A typical VCF estate has a workload distribution that runs roughly 15 percent development, 20 percent platform, 55 percent production, and 10 percent regulated. Applying the framework with development and platform designated as automation eligible and production and regulated as automation excluded scales the Aria Automation entitlement to roughly 35 percent of the full core count. At current Aria Automation unit pricing inside the bundle, that scaling produces a renewal reduction in the high single digit percent range on the total bundle value, or in the high teens to low twenties on the Aria Automation line alone.

The buyer side investment to operate the framework is real but contained. The classification register has to be produced, maintained, and made auditable. The buyer's operations team needs to confirm that the classification reflects actual policy, not aspirational policy. The seller's annual audit will compare the register against the usage telemetry, and inconsistency between the two produces remediation conversations that are commercially expensive. The framework rewards the buyer who has consistent policy enforcement across the estate. It penalises the buyer who has aspirational policy.

"The Aria Automation framework is the highest value clause in the VCF master agreement that most buyers have never read. The paragraph is buried. The mechanism is real. The value is in the high single digits on the bundle and in the high teens on the line. The cost is one classification register the buyer's operations team can produce in two weeks."Aria Automation Engagement Lead, The Desk

How to land it on a current renewal

The lever is filed as a structural request in the renewal redline package, not as a discount ask. The buyer's language references the licensing schedule paragraph by section number, attaches the workload classification register, and proposes the entitlement scaling that the framework supports. The seller's commercial counterpart will route the request to the contracts counsel, because the framework is a contractual mechanism and the response has to come from the contracts side. The contracts counsel response is almost always to accept the framework as written, because the framework is in the agreement and refusing to honour it would create precedent risk.

The commercial counterpart will sometimes respond by repricing the bundle to recover the differential through a different line item. The buyer's counter is that the framework is a defined mechanism in the agreement and the bundle pricing structure is separate. The two should not be coupled. That counter lands in the legal cycle on roughly four out of five engagements we have run.

What the framework does not do

The framework does not change the rest of the bundle. The vSAN entitlement still scales to full core count. The Tanzu entitlement still scales to full core count under the bundle's standard logic. The framework is specific to Aria Automation. Buyers who expect it to produce structural value across the bundle should expect a more limited result. The single line item value is meaningful. The bundle wide value is not. That is the realistic frame.

When the framework does not apply

The framework requires a documented workload classification policy. Buyers who run a single classification across the estate, or who have no operational policy distinguishing automation eligible workloads from automation excluded workloads, cannot apply the framework credibly. The Desk's intake review for any Aria Automation engagement begins with the buyer's existing classification documentation. If the documentation does not exist, the framework is not a lever for the current renewal. It becomes a lever for the next renewal, after the classification work is done during the term. That is a longer cycle but it produces the structural value at the next renewal point.

VCF estates reviewed where the Aria Automation framework was applied11

Estates with existing workload classification documentation7 of 11

Median Aria Automation entitlement reduction when applied62%

Median bundle level renewal value recovered through the framework9% of bundle

What we have seen on live deals

A Fortune 200 insurer brought a VCF renewal to the Desk in January 2026 with the bundle structure intact and Aria Automation deployed across roughly 20 percent of the estate. The buyer had an existing workload classification policy that distinguished automation eligible workloads cleanly. The framework application was straightforward. The redline was filed in week two of the engagement, accepted in week four by the seller's contracts counsel, and incorporated into the final agreement in week six. The renewal landed with the Aria Automation entitlement scaled to the 20 percent active deployment, the bundle pricing structure unchanged, and an annual classification audit clause embedded in the new term. The differential was 6 percent of the total bundle value and 22 percent of the Aria Automation line. The buyer's operations team is now responsible for the classification register maintenance, which is the cost of the value.

The takeaway

The Aria Automation workload classification framework is documented in the VCF licensing schedule. It scales the Aria Automation entitlement to the automation eligible workload subset. It is rarely surfaced because the paragraph is buried and neither side has an incentive to raise it.
The framework requires the buyer to maintain a policy backed classification register. Buyers with existing classification documentation can apply the framework on the current renewal. Buyers without it should treat the current term as the documentation build and the next renewal as the application point.
Value range is 6 to 12 percent of the total bundle and 18 to 28 percent of the Aria Automation line on the median estate we have reviewed. File the framework as a structural request referencing the licensing schedule paragraph by section number. Route through contracts counsel, not commercial counterpart.