Skip to content

Commit a9b319d

Browse files
authored
Update connect-multiple-private-clouds-same-region.md
Corrected VMware product name.
1 parent 10353d0 commit a9b319d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-vmware/connect-multiple-private-clouds-same-region.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Connect multiple Azure VMware Solution private clouds in the same region
33
description: Learn how to create a network connection between two or more Azure VMware Solution private clouds located in the same region.
44
ms.topic: how-to
5-
ms.date: 09/20/2021
5+
ms.date: 04/11/2022
66

77
#Customer intent: As an Azure service administrator, I want create a network connection between two or more Azure VMware Solution private clouds located in the same region.
88

@@ -28,7 +28,7 @@ The AVS Interconnect feature is available in all regions except for South Centra
2828
>[!NOTE]
2929
>The **AVS interconnect** feature doesn't check for overlapping IP space the way native Azure vNet peering does before creating the peering. Therefore, it's your responsibility to ensure that there isn't overlap between the private clouds.
3030
>
31-
>In Azure VMware Solution environments, it's possible to configure non-routed, overlapping IP deployments on NSX segments that aren't routed to Azure. These don't cause issues with the AVS Interconnect feature, as it only routes between the NSX T0 on each private cloud.
31+
>In Azure VMware Solution environments, it's possible to configure non-routed, overlapping IP deployments on NSX segments that aren't routed to Azure. These don't cause issues with the AVS Interconnect feature, as it only routes between the NSX-T Data Center T0 gateway on each private cloud.
3232
3333

3434
## Add connection between private clouds

0 commit comments

Comments
 (0)