Cloud Costs
Microsoft is killing license-included Azure VMware Solution (AVS), the version where vCenter, vSphere, vSAN, and NSX licensing all came bundled into the Azure bill. Sales stop October 31, 2026. Anyone still on it has until August 30, 2027 to move to "bring your own license" or lose access. The forcing function behind it: Broadcom no longer sells VMware as standalone products, only as VMware Cloud Foundation bundles, and it's cut off hyperscalers from reselling licenses independently. Broadcom has been upfront that it's fine with smaller customers walking, that's the point of the squeeze.
I kept thinking “we have heard this cost visibility, cloud tagging and attribution story one too many times.” For me, the game changing moment was when Aran began talking about reducing risk, proactive planning, and creating a secondary marketplace.
Why this hits harder than a normal price hike: License-included AVS was the affordable on-ramp for small and mid-sized teams to run VMware in Azure without negotiating a VCF contract with Broadcom directly. Take that away, and the math changes fast. Every team on AVS now has to pick one of three doors: eat the VCF bundle pricing, migrate to a different virtualization platform, or use this as the excuse to finally get off VMware and rearchitect those workloads as native Azure compute. A lot of teams are going to pick door three over the next year, and that's where things get interesting for FinOps.
The trap hiding inside "let's just migrate to native Azure": Rearchitecting a VMware environment into native Azure VMs is exactly the situation where teams overcommit. You're mid-migration, you don't know your real instance mix yet, sizing is still shifting, and Azure's discounting still rewards committing early with Reserved Instances or Savings Plans. Commit now based on a lift-and-shift instance count, and you're locked in for one to three years against a workload profile that's about to change again once the migration settles.
Where Archera comes in: Guaranteed Commitments let you take the Reserved Instance or Savings Plan discount as soon as you need it, without betting a full one- or three-year term on numbers you're still guessing at mid-migration. On Azure, that guarantee works as a Rebate Guarantee: the commitment stays in your account, and if it turns out you overcommitted once your post-migration footprint settles, Archera pays you back for the underused portion. You get the discount now, and a way out if your migration doesn't land where you expected.
Bottom line: Microsoft's deadline is forcing a decision that a lot of Azure VMware shops didn't ask for. If that decision turns into a migration, don't let a rushed cost estimate turn into a rushed commitment. Lock in the savings, keep the hedge.
Migrating off VMware and rethinking your Azure commitments? Archera's free to use, and it'll show you what a Guaranteed Commitment looks like on your actual usage, before you sign anything for one to three years. Book a demo
.svg)
.svg)
.svg)
.svg)
.svg)
