Skip to content

Commit b08b6dc

Browse files
Merge pull request #314677 from yash177-maker1/docs-editor/native-internet-connectivity-d-1776139328
Update native-internet-connectivity-design-considerations.md
2 parents 2afe30c + e017a98 commit b08b6dc

1 file changed

Lines changed: 7 additions & 4 deletions

File tree

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

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -29,15 +29,18 @@ Internet connectivity using Azure Firewall is similar to the way Azure virtual n
2929
## Steps:
3030

3131
1. Have or create Azure Firewall or a third-party Network Virtual Appliance in the virtual network local to the private cloud or in the peered virtual network.
32-
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.
33-
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.
32+
2.
33+
3. Adjust the existing 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.
3434

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.
35+
4. Define an Azure user defined route 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.
36+
37+
5. 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.
38+
39+
6. Have necessary firewall rules to allow traffic to and from the internet.
3640

3741
>[!Note]
3842
>The Azure route tables (UDR), associated with private cloud uplink subnets, and private cloud VNet need to be in the same Azure resource group.
3943
40-
4. Have necessary firewall rules to allow traffic to and from the internet.
4144

4245
## Related topics
4346
- [Connectivity to an Azure Virtual Network](native-network-connectivity.md)

0 commit comments

Comments
 (0)