Your Azure VMware Solution renewal came up this month. It was priced as always: license included, one line, nothing to negotiate. Then a trade press headline about the Azure VMware Solution retirement appeared, and the quote no longer looked simple.
Microsoft is not shutting AVS down. It is shutting down the version where the license comes bundled into the bill. October 31, 2026, is the deadline for pay-as-you-go customers running that model. August 30, 2027, is the deadline for anyone still holding a license-included reserved instance. Neither date is far enough away to ignore this quarter.
Azure VMware Solution Retirement Starts with the License-Included Model
Azure VMware Solution bundles vSphere, vSAN, NSX, and vCenter licenses into what you pay Microsoft. That bundle is what’s retiring, not the service itself. Microsoft stopped selling new deployments that way back in October 2025. What changed this month is the deadline for everyone who already had one.
If you’re renewing or expanding AVS this quarter, this isn’t a future problem. It’s the renewal sitting in front of you right now, priced against a model that’s already on its way out. Ten weeks is not a planning window. It’s a deadline. This is already showing up in renewal conversations happening right now. The clients asking the sharpest questions are the ones who assumed Azure had already solved this for them.
Pay-as-you-go customers on license-included AVS have until October 31, 2026. After that, they need a portable VCF subscription bought directly from Broadcom. Customers on a license-included reserved instance get longer, until August 30, 2027. Miss either date, and the license underneath your private cloud runs out.
Broadcom set this rule, not Microsoft. A VCF subscription has to be purchased directly from Broadcom to run on any hyperscaler. Microsoft is just the last major cloud to lock in a hard retirement date for its bundled version.
Microsoft’s own guidance says the bring-your-own version prices lower than the old bundle. That’s true, and it’s not the full comparison. You’re now paying Microsoft for infrastructure and Broadcom for the license. Two invoices, negotiated separately, on two different renewal clocks.
Google closed the same door on VMware Engine, on nearly the same schedule. AWS never offered a bundled version to retire in the first place. Microsoft held onto its bundled model a little longer than Google did. That gave AVS customers extra runway most VMware-on-hyperscaler customers never got. That runway is what’s ending now.
The Broadcom Exit You Thought Azure Gave You
Here’s the part worth saying out loud. A lot of clients moved VMware into Azure for one reason: to escape Broadcom’s on-premises VCF pricing. Bundle the license into the Azure bill, let Microsoft own the relationship, skip Broadcom entirely. That was the pitch, and it worked, until this week.
Here’s what makes this different: The license-included model was never a Broadcom exit. It was a Broadcom deferral, with Microsoft absorbing the relationship on your behalf. Once Microsoft retires that model, the deferral ends and the relationship comes back to you. A blended Azure invoice hid the vendor relationship. It never removed it. Broadcom still gets a check either way. The difference now is who cuts it, and what leverage you carry into that conversation.
Broadcom’s reseller channel has room to move on transition credits and trial incentives for customers switching to VCF BYOL. Most AVS customers don’t know to ask for it. The same negotiating posture applies whether Broadcom bills you directly or through a reseller.
One client of ours moved its entire on-premises VMware estate into Azure to escape Broadcom’s post-acquisition pricing. That move now sits on the same BYOL clock as every AVS customer who never left. The infrastructure decision succeeded. The vendor decision underneath it didn’t change.
That’s the sharper read on this announcement. You end up negotiating with Broadcom either way. The only question this date answers is when, not whether.
Know exactly what your VMware-on-Azure exposure looks like before you renew. We’ll map your AVS footprint against the new BYOL deadlines and show you exactly where the Broadcom negotiation actually starts.
Book a licensing review call
What We’re Seeing in Engagements Right Now: this is the first Azure VMware Solution retirement call we’ve had this quarter.
That client moved its full on-premises VMware estate into Azure to escape Broadcom’s post-acquisition pricing. Their reserved instance predates the October 15, 2025 cutoff, which pushes their real deadline to August 30, 2027. Nobody on that account had priced a direct Broadcom negotiation into the original Azure business case.
What to Verify Before Your Next Renewal Conversation
Before you sign an AVS renewal or expansion this quarter, get four things confirmed. None of these are hard to answer, but almost nobody has asked them yet. Is your AVS deployment pay-as-you-go or a reserved instance, and which deadline applies to you? If it’s a reserved instance, was it purchased before or after October 15, 2025?
Has anyone modeled a direct Broadcom VCF subscription against what you pay Microsoft today for the bundled version? If moving to Azure was meant to escape Broadcom’s pricing, has that assumption been checked against what actually changed? Renewal conversations that treat this as a technicality are the ones that get surprised at the anniversary date.
Want a second look at your AVS footprint before this quarter’s renewal? That’s what the call below is for.
The retirement date is not the real risk here. The assumption that Azure already solved your Broadcom problem is. This is not a wait-and-see item. Pricing it out after the deadline hits is the expensive way to learn the answer. Microsoft retired the packaging. It did not retire the vendor. You were always going to negotiate with Broadcom. The only thing that changed this week is how much longer you got to pretend otherwise.
