Skip to content

Commit 7a5c991

Browse files
committed
remove av36 verbiage
1 parent 04e30f9 commit 7a5c991

File tree

1 file changed

+2
-12
lines changed

1 file changed

+2
-12
lines changed

articles/azure-vmware/migrate-between-avs-private-clouds.md

Lines changed: 2 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,6 @@ ms.date: 07/01/2025
99

1010
# Migrate workloads between Azure VMware Solution private clouds
1111

12-
> [!NOTE]
13-
> On June 30, 2025, Microsoft has announced the end of sale for 3-year Reserved Instances for AV36 nodes, with AV36 node retirement on June 25, 2028. If you are using AV36 nodes currently, see [Migrate workloads to a new SKU as AV36 nodes retire](#migrate-workloads-to-a-new-sku-as-av36-nodes-retire) for guidance on planning your migration to our different Azure VMware Solution SKU offerings.
14-
1512
Azure VMware Solution customers often need to migrate workloads between private clouds in scenarios such as moving to a different Azure region, changing SKUs, or consolidating environments. You can use **VMware HCX** to perform these migrations seamlessly, using **similar steps to migrating workloads from on-premises environments to Azure VMware Solution**.
1613

1714
VMware HCX enables you to move workloads with minimal downtime, maintain consistent IP addressing if needed, and preserve operational continuity while modernizing or rebalancing your Azure VMware Solution environment.
@@ -51,13 +48,6 @@ The process for extending networks between two Azure VMware Solution environment
5148

5249
For detailed instructions, see [Extend networks using VMware HCX in Azure VMware Solution](configure-hcx-network-extension.md).
5350

54-
# Migrate workloads to a new SKU as AV36 nodes retire
55-
56-
Microsoft has announced the end of sale for 3-year Reserved Instances for **AV36 nodes on June 30, 2025**, with **AV36 node retirement on June 25, 2028**. To prepare for this change, you will need to transition your workloads from AV36-based private clouds to a new Azure VMware Solution SKU before the retirement date. The instructions outlined above will work to help you migrate your VMware workloads to a different SKU offering on Azure VMware Solution.
57-
58-
## What SKU is right for me?
59-
60-
[Fill this out].
61-
62-
51+
## Considerations when migrating to an Azure VMware Solution Generation 2 private cloud
6352

53+
Azure VMware Solution Generation 2 private clouds currently have functionality, networking, and integration limitations that may affect your migration plans. Review these limitations to ensure your deployment aligns with current capabilities. For details, see [Design considerations for Azure VMware Solution Generation 2 Private Clouds](native-network-design-consideration.md).

0 commit comments

Comments
 (0)