Azure VMware Solution’s license-included retirement has more than one deadline. Pay-as-you-go deployments must transition by October 31, 2026; reserved benefits can end earlier than the August 30, 2027 retirement if the reservation expires first.
Use the date attached to the actual entitlement
Microsoft's updated customer announcement distinguishes license-included PayGo from eligible reserved instances. Its current licensing reference adds the crucial rule: an expiring reservation loses its included-license benefits when it expires, even before August 30, 2027.
The reference requires portable VCF for new deployments from November 1, 2025 and transition of existing license-included PayGo by October 31, 2026. The historical sales cutoff in the announcement is October 15, 2025. Those dates address different eligibility and sales conditions; they are not interchangeable deadlines for every node.
For an original example, consider a reservation ending March 31, 2027. The later August retirement does not extend it for another five months. Inventory the actual reservation end date alongside the licensing model before choosing the procurement schedule.
Register the cores used by the private cloud
Portable VCF is registered per AVS private cloud. The configuration guide requires the deployed BYOL core count, not the entire entitlement if some of it is used elsewhere. Registration does not replace Azure host-capacity approval.
An original arithmetic example uses five AV36 hosts, each with 36 cores. If two remain covered by active license-included reservations and three use BYOL, the private cloud has 180 deployed cores but 108 BYOL cores to register. This example assumes those two included entitlements remain valid; it is not an account-specific licensing determination.
Reconcile the registration whenever hosts or coverage change. Across private clouds, the sum of registered cores must stay within the purchased entitlement. Firewall add-ons have separate rules, so the base VCF count is not automatically the answer for every optional feature.
A managed-service continuation, with administrative work
Microsoft documents conversion of an existing private cloud without workload interruption. This does not mean there is nothing to do: obtain the appropriate subscription, register its details and confirm the portal's resulting status. The guide also documents exchanging an included-license reservation for the corresponding BYOL reservation.
The key distinction for cost is the Azure infrastructure charge versus the separately purchased VCF subscription. A lower Azure line item alone does not establish a lower combined bill. Compare the same capacity, duration and included features across the whole offer.
The old article's relative claims about having “fourteen months” remaining were inconsistent with its publication date. Absolute deadlines and the earliest actual entitlement expiry provide a more reliable planning basis.
Differentiate PayGo and active RI deadlines, include earlier reservation expiry, current portal registration and per-private-cloud BYOL core counting.