Merge pull request #310608 from yash177-maker1/docs-editor/native-internet-connectivity-d-1768606642

Update native-internet-connectivity-design-considerations.md

Author: prmerger-automator[bot]

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

@@ -29,9 +29,11 @@ Internet connectivity using Azure Firewall is similar to the way Azure virtual n
 ## Steps:
 
 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.
-2. 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.
+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.
 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.
 
+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.
+
 >[!Note] 
 >The Azure route tables (UDR), associated with private cloud uplink subnets, and private cloud VNet need to be in the same Azure resource group.