Public Preview: You can now migrate VMware management VMs from their host cluster to a different cluster within the same private cloud. To migrate management VMs, you must have at least two clusters in your private cloud, and the destination cluster must be a workload cluster. This operation transitions the target workload cluster to a management cluster, and the source management cluster becomes a workload cluster.

The VMware Engine ve2 node type is now available in the following additional region:

• Los Angeles, USA, North America (us-west2-b)

The VMware Engine ve2 node type is now available in the following additional region:

• Paris, France, Europe (europe-west9-b)

The VMware Engine ve2 node type is now available in the following additional region:

• Osaka, Japan, Asia Pacific (asia-northeast2)

Stretched private clouds capable of hosting both ve1 and ve2 node-family clusters are now available in the following regions:

• Sydney, Australia, Asia Pacific (australia-southeast1-a, australia-southeast1-b)
• Frankfurt, Germany, Europe (europe-west3-a, europe-west3-b)

While a stretched private cloud can contain mixed node families, each individual stretched cluster must be comprised of nodes from the same family type.

Private clouds capable of hosting both ve1 and ve2 node-family clusters are available in the following additional regions:

• London, England, Europe (europe-west2-a, europe-west2-b)
• São Paulo, Brazil, South America (southamerica-east1-a)
• Dallas, Texas, North America (us-south1-b)

While a private cloud can contain mixed node families, each individual cluster must be comprised of nodes from the same family type.

VMware Engine introduces enhancements to simplify using external NFS datastores. External NFS datastores let you scale storage independently of compute resources for your VMware workloads. You can use Filestore or Google Cloud NetApp Volumes as external NFS datastores for ESXi hosts in Google Cloud VMware Engine. For more information, see NFS datastores overview.

VMware Engine ve2 nodes are now available in the Milan, Italy (europe-west8-b) zone in the Milan, Italy, Europe region (europe-west8).

VMware Engine now supports private clouds with mixed node families (ve1 and ve2). While a private cloud can contain mixed node families, each cluster within that private cloud must contain nodes of the same type. This feature is available in the following regions and zones:

• Ashburn, North America (us-east4-a, us-east4-b)
• Iowa, North America (us-central1-a)
• Montreal, North America (northamerica-northeast1-a)
• Sydney, Australia (australia-southeast1-a, australia-southeast1-b)
• Frankfurt, Europe (europe-west3-a, europe-west3-b)
• Santiago, South America (southamerica-west1-b)

VMware Engine ve2 nodes are now available in the Dallas, Texas, North America region (us-south1-b).

VMware Engine ve2 nodes are now available in the Tokyo, Japan region (asia-northeast1-a).

VMware Engine ve2 nodes are now available in the London, England, Europe (europe-west2-b) zone in the London, England, Europe region (europe-west2).

VMware Engine ve1 nodes are now available in the Mumbai, India (asia-south1-b) zone in the Mumbai region (asia-south1).

This is to notify you about upcoming changes in licensing model with Google Cloud VMware Engine following Broadcom's recent announcement to move to a "bring your own" subscription model for VMware Cloud Foundation (VCF).

You can renew or add additional capacity of VMware Engine nodes with VCF-license included until October 15, 2025. After that, Google Cloud will not be able to sell new VMware Engine VCF license-included nodes. You can buy new VMware Engine BYOL nodes and use them with "bring your own" VCF subscriptions (purchased by you from Broadcom) for new capacity after October 15, 2025.

For any questions, please reach out to your Google Cloud sales team, who can help review your specific scenarios, discuss the implications of these changes for your organization, and help you manage this transition.

For more details, see the October 3, 2025 service announcement.

VMware Engine ve2 nodes are now available in the following additional region:

• Doha, Qatar (me-central1, v-zone-a)

All 3-year Committed Use Discounts (CUDs) for VMware Engine ve1 SKUs are now End-of-Sale across all regions where the service is available.

The following specific 3-year commitments are impacted by this change:

• 3-year commitment (monthly payments), Fully Licensed Pricing - "postpaid"
• 3-year commitment (upfront payments), Fully Licensed Pricing - "prepay"
• 3-year commitment (monthly payments), Fully Licensed convertible commitment - "postpaid"
• 3-year commitment (upfront payments), Fully Licensed convertible commitment - "prepay"
• 3-year commitment (monthly payments), Portable License Pricing - "postpaid"
• 3-year commitment (upfront payments), Portable License Pricing - "prepay"
• 3-year commitment (monthly payments), Protected License Pricing - "postpaid"
• 3-year commitment (upfront payments), Protected License Pricing - "prepay"

Refer to VMware Engine node types for the regional availability of ve1 SKUs.

VMware Engine ve2 nodes are now available in the following additional region and zone:

• The Milan, Italy, Europe region (europe-west8-a).
• The Melbourne, Australia (australia-southeast2-b) zone in the Melbourne, Australia region (australia-southeast2).

You can now use Privileged Access Manager (PAM) to accelerate the deletion of "soft deleted" private clouds. For more information, see the documentation on how to delete a private cloud.

VMware Engine ve2 nodes are now available in the London, England, Europe region (europe-west2-a).

VMware Engine v2 nodes are now available in the Santiago, Chile (southamerica-west1-b) zone in the Santiago region (southamerica-west1) region.

VMware Engine ve2 nodes are now available in the Dammam, KSA (me-central2) region.

VMware Engine ve2 nodes are now available in the São Paulo, Brazil (southamerica-east1-c) zone in the São Paulo region (southamerica-east1).

When upgrading to Windows Server 2022 or newer images on your GCVE private clouds, you can use a combination of Windows Server BYOL for Windows Server 2019 and earlier images and on-demand licensing for Google-provided Windows Server 2022. For more information, see Use a combination of BYOL and on-demand Windows Server licenses from Google.

VMware Engine single-node private clouds, created after June 4th 2025, will no longer delete after 60 days. All single-node private clouds will have no time limit. Single-node private clouds have limitations to SLA, patching, and upgrades.

VMware Engine ve2 nodes are now available in Toronto, Canada (northamerica-northeast2).

VMware Engine ve2 nodes are now available in the following additional region:

• Melbourne, Australia (australia-southeast2-a)

All new VMware Engine private clouds now deploy with the following versions:

• VMware vSphere version 8.0 update 3
• NSX-T 4.2.1.2

Existing private clouds will be upgraded starting June 2025. See Service announcements for more details on the contents of this update.

VMware Engine ve2 nodes are available in Montreal, Canada (northamerica-northeast1).

Google Cloud VMware Engine now supports 24 ve2 node types, enabling precise and efficient environment sizing. See VMware Engine node types for full details.

VMware Engine is integrated with Google Cloud Essential Contacts for email notifications. Automatic emails are sent to the appropriate Essential Contacts notification categories for service-impacting events. For more information, see Overview of VMware Engine monitoring.