Merge pull request #224841 from erjosito/patch-10

Clarifying the statement about the default route

Author: prmerger-automator[bot]

articles/azure-vmware/concepts-network-design-considerations.md

@@ -33,11 +33,11 @@ Use either 2-byte or 4-byte public ASN numbers, and make sure that they're compa
 ## Management VMs and default routes from on-premises
 
 > [!IMPORTANT]
-> Azure VMware Solution management virtual machines (VMs) won't honor a default route from on-premises.
+> Azure VMware Solution management virtual machines (VMs) won't honor a default route from on-premises for RFC1918 destinations.
 
-If you're routing back to your on-premises networks by using only a default route advertised toward Azure, vCenter Server and NSX-T Manager VMs won't be compatible with that route.
+If you're routing back to your on-premises networks by using only a default route advertised toward Azure, traffic from vCenter Server and NSX-T Manager VMs towards on-premises destinations with private IP addresses won't follow that route.
 
-To reach vCenter Server and NSX-T Manager, provide specific routes from on-premises to allow traffic to have a return path to those networks.
+To reach vCenter Server and NSX-T Manager from on-premises, provide specific routes to allow traffic to have a return path to those networks. For example, advertise the RFC1918 summaries (10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16).
 
 ## Default route to Azure VMware Solution for internet traffic inspection