Skip to content

Commit 2a05e99

Browse files
Learn Editor: Update native-internet-connectivity-design-considerations.md
1 parent 13cb227 commit 2a05e99

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/azure-vmware/native-internet-connectivity-design-considerations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Internet connectivity using Azure Firewall is similar to the way Azure virtual n
3232
1. Define an Azure route table with a 0.0.0.0/0 route pointing to the next-hop type Virtual Appliance with the next-hop IP address of the Azure Firewall private IP or IP of the Network Virtual Appliance.
3333
1. Associate the route table to the Azure VMware Solution specific virtual network subnets named “avs-nsx-gw” and “avs-nsx-gw-1”, which are part of the virtual network associated with private cloud.
3434

35-
1. Associate the route table to the Azure VMware Solution specific virtual network subnet named "avs-services", required for management appliances, including vCenter, NSX and HCX Manager to communicate outbound.
35+
1. Associate the route table to the Azure VMware Solution specific virtual network subnet named "avs-mgmt", required for management appliances, including vCenter, NSX and HCX Manager to communicate outbound.
3636

3737
>[!Note]
3838
>The Azure route tables (UDR), associated with private cloud uplink subnets, and private cloud VNet need to be in the same Azure resource group.

0 commit comments

Comments
 (0)