The VMware Renewal Trap: When Azure VMware Solution Is Strategy, and When It's Avoidance

The renewal quote lands on a Tuesday. The number is a multiple of last year's — often 3×, and in the cases quoted to regulators, far more. Somewhere in the next 30 minutes, someone will say "let's just lift it to Azure VMware Solution." That sentence is a strategy decision wearing a migration task's clothes — and getting it wrong is a multi-year, multi-million-dollar commitment.

The Renewal Quote Is a Forcing Function

For a decade, "what do we do about VMware" was a question you were allowed to not answer. The hardware ran. The team knew every quirk of vCenter by heart. The perpetual licenses were bought and paid for years ago. Modernization sat in the backlog behind every revenue feature, lost every planning round, and no one was blamed for the delay. That was the arrangement.

Broadcom tore up the arrangement. Perpetual licensing: gone. The catalog of pick-what-you-need SKUs: collapsed into a handful of take-it-or-leave-it bundles. And since April 10, 2025, the smallest order you can place is 72 cores — up from a 16-core-per-processor floor. Run a small cluster of modest dual-socket hosts and the floor alone can have you licensing more cores than you actually run, before a single per-core increase enters the arithmetic.

This is not a handful of unlucky customers venting. It is the shape of the whole market:

And the pressure only compounds from here. Gartner expects 35% of VMware workloads to leave the platform by 2028. Meanwhile the exit most teams reach for first — lift it to Azure VMware Solution and sort the licensing out later — has quietly picked up an expiry date of its own, courtesy of Microsoft's latest AVS licensing changes. That story is a few sections down, and it moves the deadline closer.

Here's the trap. A renewal deadline creates urgency, and urgency collapses a strategy question into a procurement question. The room stops asking "where should these workloads live for the next seven years" and starts asking "what's the fastest way to not pay this invoice." Those are different questions with different right answers.

Microsoft's Cloud Adoption Framework is unusually blunt about where Azure VMware Solution fits: it's the right choice "when the business value of moving to Azure is clear, and the cost, risk, or time required to redesign applications aren't acceptable." That's the sentence to anchor the whole decision on.

Meridian's platform owner did the thing that feels responsible: she asked her team for a migration plan. Two weeks later she had a Gantt chart for lifting 340 VMs into Azure VMware Solution. What she didn't have was an answer to the question the board would actually ask — why AVS and not native Azure, and what does this commit us to?

The Wrong Question

"How do we migrate?" is the wrong first question, because it has already chosen the destination. The right first move is to interrogate the destination itself — because lift-and-shift to AVS isn't a neutral parking spot on the way to somewhere better. It's a fork in a roadmap you'll be living with for years.

Say yes to AVS and you've said yes to three things, whether or not anyone spelled them out in the meeting:

• You stay in the VMware business. vSphere, vSAN, NSX — the same stack, the same daily operations, just running on hardware Microsoft racks and patches instead of hardware you bought.
• Your bill is set by the host, not the workload. AVS charges per AVS host, never per VM — so a half-empty cluster costs exactly what a full one does, and every point of consolidation you skip before you migrate is money you keep paying every month afterward.
• Broadcom is still your vendor. You still buy the VCF portable subscription — now straight from Broadcom, not folded into the Azure price. AVS changes who racks the servers; it doesn't end the Broadcom relationship. It splits your VMware estate across two suppliers, each with its own contract and its own renewal clock.

None of this is an argument against AVS. It's an argument for choosing it with your eyes open — with the case for not doing it sitting on the same table.

And "AVS vs. refactor" isn't the whole board either. The full slate is wider: the other hyperscalers' VMware services (AWS, Google Cloud, OCI), re-hypervisoring to Hyper-V or another platform, Nutanix on Azure, or a deliberately smaller on-premises footprint. Most of those are worse fits for a renewal-clock timeline — but a platform owner who hasn't named them on a slide will get asked why in the board meeting, not before it.

One more thing the Gantt chart won't show you: the portable VCF subscription is bought directly from Broadcom, on Broadcom's terms and timeline. Through 2025 those quotes were inconsistent — slow to arrive, re-priced, occasionally refused. If your AVS plan depends on a renewal-window cutover, get the licensing commitment in writing before you cancel anything on the old platform.

When AVS Is the Right Call — and When It Isn't

The Cloud Adoption Framework gives five signals that point toward Azure VMware Solution. Read them as a checklist, not a menu — the more that apply, the stronger the case:

And the CAF is equally direct about when to send the workloads to native Azure IaaS or PaaS instead. Consider Azure-native if:

• You plan to modernize or refactor the applications in the near term anyway.
• The workloads run well on Azure VMs with no VMware dependencies.
• The VMware footprint is small enough to migrate directly to native services.
• Your primary objective is long-term cloud optimization, not VMware continuity.
• Most of the estate is new or could be built cloud-native from the start.

In those cases, the CAF notes, "moving directly to Azure IaaS or PaaS services often provides greater cloud-native benefits and can reduce long-term platform costs." AVS there is an expensive way to postpone a decision you've already made.

When the signals point native, the target is workload-specific, not one-size-fits-all. The common mappings:

Native wins the long game — consumption pricing with no dedicated-hardware floor, no Broadcom subscription, cleaner egress economics, and much lower exit friction. The cost is a real operating-model change and per-app migration effort, which is exactly why the renewal clock rarely leaves room to do it all at once.

The TCO Baseline Everyone Gets Wrong

Here is the single most common mistake in the room when that renewal quote is on the screen: teams compare the Azure VMware Solution monthly cost to the Azure-native VM cost, see that AVS looks more expensive per unit, and conclude AVS is a bad deal.

Wrong baseline. The CAF is explicit: "Compare Azure VMware Solution against the full cost of your existing VMware platform. Include hardware refresh costs, datacenter expenses, and operational support."

Per compute unit, AVS is not cheaper than the hardware you already own — that's the wrong lens. The savings come from the lines that disappear: the colocation contract, the next hardware refresh, the mostly-idle DR site, and the platform-operations time you get back. Microsoft's commissioned Forrester study attributes the bulk of its modelled ROI to roughly 90% hardware-refresh avoidance and datacenter exit, plus redeploying admins off maintenance — and, for out-of-support Windows Server and SQL Server, the free Extended Security Updates that AVS includes but on-premises does not.

Directional, not a quote. Your actual position depends on estate size, utilization, reserved-instance commitment, and how aggressively your renewal was priced — build the model with the Azure pricing calculator and your own finance data.

One floor to know before you model: an AVS cluster has a three-host minimum, so the smallest production private cloud is three hosts regardless of how little you're running on it. Below roughly that footprint, native Azure IaaS is almost always the cheaper answer — which is exactly the CAF's "small VMware footprint" exclusion, expressed as a bill.

Two levers move the AVS number more than anything else, and both are yours to pull:

• Host density. Because you pay per host, a cluster running at 45% utilization is burning roughly half your spend on air. Right-sizing and consolidation before migration is the highest-ROI work in the whole program.
• Reserved instances. A 1- or 3-year reservation on AVS hosts changes the comparison materially against a fresh hardware capital outlay. If the workloads are staying put for three years — and if you're choosing AVS, they are — not reserving is leaving money on the table. Reservations are also a compliance runway now: licence-included RIs bought on or before 15 October 2025 hold their VCF terms until 30 August 2027, while any new reservation is BYOL from day one.

From Decision to Proposal: How You Get the Numbers

Everything to this point is the argument. What a board actually approves is the argument with a costed proposal stapled to it: host counts, a three-year TCO, a wave plan, and a defensible number for "why not just go native." In Azure, that deliverable comes out of one place — Azure Migrate.

What the assessment actually produces

Azure Migrate does three jobs, and they line up one-to-one with the questions a platform owner has to answer:

The AVS assessment is the output that anchors the proposal. Per workload group it returns a readiness verdict (Ready / Ready with conditions / Not ready), the number of hosts required, and — the useful part — the limiting factor that drives that count: CPU, memory, or storage. It also bakes in the management overhead for vCenter, NSX, and HCX (roughly 44 vCPU, 75 GB RAM, and 722 GB of storage before dedupe), a fixed tax on the first host that catches people sizing on a spreadsheet.

Host count isn't a fixed readout. A short list of settings moves it — and moves the bill — which is where an experienced assessor earns the engagement fee:

The prerequisites nobody budgets time for

"Run Azure Migrate" sounds like something you do in the last week before the renewal date. It isn't. Performance-based sizing needs a representative sample of real load — one day at the absolute minimum, one to four weeks to trust the confidence rating — and that clock only starts once the plumbing is in place:

• the Azure Migrate appliance deployed as a VMware OVA (one instance scales to roughly 10,000 VMs);
• a read-only vCenter account — and for dependency and software inventory, that account also needs Guest Operations rights plus valid in-guest credentials loaded into the appliance, with VMware Tools running on the guests;
• outbound connectivity from the appliance to Azure.

The shortcut — importing an RVTools export or the CSV template — produces a rough sizing in an afternoon, but with no dependency map, no software inventory, and no performance-confidence rating. It's a way to start the business case, not a substitute for letting the appliance watch real load.

The anatomy of an AVS bill

After the wrong-baseline mistake, the second most common costing error is quoting the host price as the all-in number. It never is. Here's what actually reaches the invoices — and note the two separate names in the "billed by" column:

For rough orientation, a reserved instance runs roughly 38–43% below PAYG at one year and 60–63% below at three. The host SKUs:

Usable vSAN lands well below raw once the FTT/RAID policy is applied. Pull exact rates from the Azure pricing calculator for your region and offer, and a Broadcom quote for the cores.

The subscription trap that stalls programs

The Gen2 Decision You Make Once

Azure VMware Solution now ships in two private cloud generations. The VMware components — vCenter, ESXi, NSX — are identical between them. The difference is the network architecture, and it matters more than it sounds.

The CAF's guidance is one line, and it's the important one: "Make the generation decision early. Moving between generations requires workload migration." This is not a setting you toggle later — getting it wrong means doing the migration twice.

The Shared Responsibility Line — and Where It Cuts You

Microsoft operates and maintains the Azure infrastructure and the VMware platform: provisioning, hardware maintenance, and updating ESXi and vCenter. That's real operational load lifted off your team.

What stays yours: applications, VMs, operating systems, data, security policy, compliance, backup — and this is the one that surprises people — monitoring consumption and scaling host capacity to meet demand while balancing performance, resilience, and cost.

In an owned datacenter, running out of headroom is a slow, visible problem: someone notices the cluster is full and starts a six-week procurement. In AVS, adding a host is an API call — which is exactly the risk. A poorly-governed AVS environment scales its own bill. The classic failure mode: a "temporary" capacity add to survive a quarter-end becomes permanent because nobody owns the decision to scale it back down.

The Adoption Sequence

Whether you land on Azure VMware Solution, native Azure, or a sequenced mix, the CAF's five-phase adoption path is the same. The first two phases are the decision work — they fit inside a renewal window. The rest is delivery, measured in months. Work it in order:

What This Means for Your Next Budget Review

The board question isn't "did you migrate VMware." It's "what did this commit us to, and for how long."

A platform owner who has done the work walks in with three things: the fully-loaded comparison — AVS against the real cost of staying, not against native VM list price; a one-line answer to "why not just refactor" that names the renewal clock and the workloads that can't move yet; and a dated modernization backlog that turns AVS from a destination into a bridge with an exit.

Here is that comparison in the shape it should reach the board — three honest options, not a foregone conclusion:

The hybrid column wins for most estates because it's the only one that hits an immovable lease date and avoids paying the AVS-plus-Broadcom premium on workloads with no VMware dependency. It's also the hardest to run — two operating models through the transition — which is why the modernization backlog has to be funded, not aspirational.

Azure VMware Solution is a genuinely good answer to a specific question: we need out of this datacenter faster than we can re-architect, and the team's VMware skills are worth preserving. If that's your question, it's the right tool, and the CAF gives you a clean adoption path.

If it's not your question — if the estate is small, or modernization is already funded and scheduled — then paying AVS host rates to keep running vSphere is the expensive version of not deciding. The renewal quote forced the decision. Make it on purpose.

Ready to operationalize your Azure journey?

If a VMware renewal is forcing a datacenter-exit decision and you need the fully-loaded AVS-vs-native comparison, the Gen2 landing zone design, and a modernization backlog the board will sign off on — that's the conversation worth having.