Skip to content

Commit 2404a19

Browse files
author
Jill Grant
authored
Merge pull request #270500 from rvandenbedem/patch-5
Update move-azure-vmware-solution-across-regions.md
2 parents bed097e + e1e7cb0 commit 2404a19

File tree

2 files changed

+6
-4
lines changed

2 files changed

+6
-4
lines changed

articles/azure-vmware/move-azure-vmware-solution-across-regions.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article describes how to move Azure VMware Solution resources
44
ms.custom: "subject-moving-resources, engagement-fy23"
55
ms.topic: how-to
66
ms.service: azure-vmware
7-
ms.date: 2/23/2024
7+
ms.date: 3/28/2024
88

99
# Customer intent: As an Azure service administrator, I want to move my Azure VMware Solution resources from Azure Region A to Azure Region B.
1010
---
@@ -18,9 +18,9 @@ You can move Azure VMware Solution resources to a different region for several r
1818

1919
This article helps you plan and migrate Azure VMware Solution from one Azure region to another, such as Azure region A to Azure region B.
2020

21-
The diagram shows the recommended ExpressRoute connectivity between the two Azure VMware Solution environments. An HCX site pairing and service mesh are created between the two environments. The HCX migration traffic and Layer-2 extension moves (depicted by the red line) between the two environments. For VMware recommended HCX planning, see [Planning an HCX Migration](https://vmc.techzone.vmware.com/vmc-solutions/docs/deploy/planning-an-hcx-migration#section1).
21+
The diagram shows the recommended ExpressRoute connectivity between the two Azure VMware Solution environments. An HCX site pairing and service mesh are created between the two environments. The HCX migration traffic and Layer-2 extension moves (depicted by the purple line) between the two environments. For VMware recommended HCX planning, see [Planning an HCX Migration](https://vmc.techzone.vmware.com/vmc-solutions/docs/deploy/planning-an-hcx-migration#section1).
2222

23-
:::image type="content" source="media/move-across-regions/move-ea-csp-across-regions-2.png" alt-text="Diagram showing ExpressRoute Global Reach communication between the source and target Azure VMware Solution environments." border="false":::
23+
:::image type="content" source="media/move-across-regions/move-ea-csp-across-regions-2.png" alt-text="Diagram showing ExpressRoute Global Reach communication between the source and target Azure VMware Solution environments." border="false" lightbox="media/move-across-regions/move-ea-csp-across-regions-2.png":::
2424

2525
>[!NOTE]
2626
>You don't need to migrate any workflow back to on-premises because the traffic will flow between the private clouds (source and target):
@@ -29,7 +29,7 @@ The diagram shows the recommended ExpressRoute connectivity between the two Azur
2929
3030
The diagram shows the connectivity between both Azure VMware Solution environments.
3131

32-
:::image type="content" source="media/move-across-regions/move-ea-csp-across-regions-connectivity-diagram.png" alt-text="Diagram showing communication between the source and target Azure VMware Solution environments." border="false":::
32+
:::image type="content" source="media/move-across-regions/move-ea-csp-across-regions-connectivity-diagram.png" alt-text="Diagram showing communication between the source and target Azure VMware Solution environments." border="false" lightbox="media/move-across-regions/move-ea-csp-across-regions-connectivity-diagram.png":::
3333

3434
In this article, walk through the steps to:
3535

articles/azure-vmware/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -69,6 +69,8 @@ items:
6969
href: architecture-storage.md
7070
- name: Migrate
7171
href: architecture-migrate.md
72+
- name: Well Architected Framework
73+
href: https://learn.microsoft.com/azure/well-architected/azure-vmware/
7274
- name: Cloud Adoption Framework
7375
items:
7476
- name: Azure VMware Solution landing zone accelerator

0 commit comments

Comments
 (0)