The quote almost always priced capacity the customer never used, with 20 to 40 percent of reserved capacity sitting below half utilization in the first year
It looks like one line item on a cloud bill. The real cost sits in the node hours, the reserved term, and an entitlement most estates pay for twice.
Prepared by Redress Compliance · August 18, 2026 · VMware migration and renewal reviews. 25 to 35 reviews led, 2024 to 2025.
Executive summary
20 to 40 percent of reserved capacity sat below 50 percent utilization in the first year. You rent whole hosts rather than machines, so packing density sets the real unit cost.
Estates kept a separate virtualization subscription for hosts whose entitlement was already inside the node price. That is paying twice for the same right.
Data transfer and managed storage added 10 to 25 percent on top of the node bill that the original business case had ignored entirely.
Reserved terms cut the node rate 30 to 50 percent against pay as you go. That only helps if the node family and count were right before the term was signed.
What is actually being rented?
Whole dedicated hosts, billed per node per hour, not virtual machines. Each node ships a fixed core count, memory and storage, and your job is to pack machines densely enough that the per node rate divides into an acceptable per workload cost.
Current rates are published on the Azure VMware Solution pricing page, with the architecture in the service documentation.
The node family decides the core to memory ratio
Memory bound and compute bound estates reserve very different families, and the wrong choice strands capacity you still pay for. Right size the family before you reserve the term, because the term is the part that cannot be undone.
What sits outside the node price?
More than the business case usually carries. The node rate is the floor rather than the bill, and three services meter separately.
| Component | Billed on | Discount lever | Surprise risk |
|---|---|---|---|
| Dedicated node | Per node per hour | One or three year reserved term | Low once reserved |
| Data transfer | Volume leaving the environment | Architecture rather than rate | High, and usually unmodelled |
| Managed storage | Capacity beyond node storage | Tier and retention design | Moderate, grows quietly |
| Backup and recovery tooling | Third party subscription | Consolidation with the estate standard | Moderate |
Together the transfer and managed storage lines added 10 to 25 percent on top of the node bill in the reviews, which is enough to change the migration case on its own.
The VMware Cloud Foundation licensing brief
What the entitlement covers, where it is already included, and what a renewal prices on top.
Get the brief →What 25 to 35 VMware reviews showed
Across roughly 25 to 35 VMware migration and renewal reviews led between 2024 and 2025, the quote almost always priced capacity the customer never used. Three patterns recur.
- Node overprovisioning: 20 to 40 percent of reserved capacity sat below 50 percent utilization in the first year.
- Double licensing: estates kept a separate virtualization subscription for hosts whose entitlement was already inside the node price.
- Transfer blind spots: data movement and managed storage added 10 to 25 percent on top of the node bill that the business case ignored.
The entitlement is included in the node price. A separate subscription for those same hosts is not a belt and braces decision, it is a duplicate invoice.
- Estate inventory in, core sizing out, across three pricing scenarios and discount bands
- Your quote benchmarked against real closed transactions for comparable estates
- Exit and alternative scenarios priced, so you negotiate with a credible walkaway
How large are the reserved discounts?
Between 30 and 50 percent against pay as you go on one and three year terms. That is a large enough saving to justify the commitment and a large enough commitment to punish a sizing error.
Reserve after the node family is right, not before. A term signed against the default family is a multi year purchase of the wrong core to memory ratio, and the stranded capacity bills at the discounted rate rather than disappearing.
Utilization is the number to hold yourself to
A fifth to two fifths of reserved capacity below half load in year one is a packing problem rather than a pricing one, and it is measurable from the first month.
Watch the briefing · 4:44The VMware VCF RenewalPreparing the core inventory and the right sizing before the price is named.
What changed underneath this after the acquisition?
Standalone perpetual licences no longer renew, which pushes more estates toward hosted equivalents like this one or toward a rival hyperscaler's version of it.
That is the context to price this against. The comparison is not hosted against on site as it used to be, it is hosted against a subscription renewal on terms that changed, which is worked through in the licensing pillar.
The comparison changed shape after the acquisition
Where the estate is genuinely portable, the exit comparison belongs in the same model rather than in a later one. The alternatives sit in the exit architecture brief.
What the reviews measured, 2024 to 2025
Two cuts of the engagement file, one on capacity and one on the lines nobody modelled.
In the first year, measured across the estates reviewed, on nodes already committed under a reserved term.
On top of the node bill, from data movement and managed storage that the original business case did not carry.
Both are sizing and modelling gaps rather than commercial ones. Neither is recoverable through a discount once the term is signed.
Your first five moves
- Right size the node family before reserving anything, because the core to memory ratio decides how much capacity strands and the term makes it permanent.
- Cancel any separate virtualization subscription for hosts already entitled inside the node price, which is a duplicate invoice rather than a safeguard.
- Model data transfer and managed storage into the business case, since they added 10 to 25 percent on top of the node bill in the reviews.
- Hold utilization to a stated target from month one, because 20 to 40 percent of reserved capacity below half load is a packing problem visible long before the renewal.
- Reserve for one or three years only once the family and count are settled, for a 30 to 50 percent rate cut. The VMware practice sizes the estate before the term is signed.
Frequently asked questions
How is the service priced?
Per dedicated bare metal node per hour, not per virtual machine. You rent whole hosts, so the number and type of nodes reserved sets the floor on cost.
Is a separate virtualization subscription needed?
No. The entitlement is included in the node price, so keeping a separate subscription for those hosts is paying twice for the same right.
How much do reserved terms save?
Between 30 and 50 percent against pay as you go on one or three year terms. The saving is large enough to justify the commitment and large enough to punish a sizing error.
What is the typical utilization problem?
Between 20 and 40 percent of reserved capacity sat below 50 percent utilization in the first year. That is a packing problem, measurable from month one.
What sits outside the node price?
Data transfer, managed storage, and third party backup and recovery tooling. Transfer and storage alone added 10 to 25 percent on top of the node bill in the reviews.
Does the node family matter?
Yes. It sets the core to memory ratio, so memory bound and compute bound estates reserve very different families, and the wrong choice strands capacity you still pay for.
Why are more estates looking at this now?
Because standalone perpetual licences no longer renew after the acquisition, which pushes estates toward hosted equivalents or a rival hyperscaler's version of the same thing.
What should the comparison actually be?
Hosted against a subscription renewal on changed terms, rather than hosted against on site as it used to be. Where the estate is portable, the exit belongs in the same model.
When should the term be signed?
After the node family and count are settled. A term signed against the default family is a multi year purchase of the wrong ratio, and the stranded capacity still bills.
Is the node rate the whole bill?
No, it is the floor. Treating it as the bill is what produced the 10 to 25 percent surprise at the first reconciliation in the estates reviewed.