Merge pull request #301900 from MSFT-FrankLpnsk/Vnet-Conn

[Virtual WAN] Update to include Cross Tenant VNet Connection docs and improvement to FAQ

Author: prmerger-automator[bot]

articles/virtual-wan/howto-connect-vnet-hub-powershell.md

@@ -17,6 +17,7 @@ Before you create a connection, be aware of the following:
 
 * A virtual network can only be connected to one virtual hub at a time.
 * In order to connect it to a virtual hub, the remote virtual network can't have a gateway (ExpressRoute or VPN) or RouteServer.
+* To connect a cross-tenant remote virtual network to the virtual hub, refer to [Connect cross-tenant virtual networks to a Virtual WAN hub](cross-tenant-vnet.md).
 
 * Some configuration settings, such as **Propagate static route**, can only be configured in the Azure portal at this time. See the [Azure portal](howto-connect-vnet-hub.md) version of this article for steps.
 

articles/virtual-wan/howto-connect-vnet-hub.md

@@ -17,9 +17,10 @@ Before you create a connection, be aware of the following:
 
 * A virtual network can only be connected to one virtual hub at a time.
 * In order to connect it to a virtual hub, the remote virtual network can't have a gateway (ExpressRoute or VPN) or RouteServer.
+* To create a cross-tenant virtual network connection to the virtual hub, refer to [Connect cross-tenant virtual networks to a Virtual WAN hub](cross-tenant-vnet.md)
 
 > [!IMPORTANT]
-> If VPN gateways are present in the virtual hub, this operation as well as any other write operation on the connected VNet can cause disconnection to Point-to-site clients as well as reconnection of site-to-site tunnels and BGP sessions.
+> * If VPN gateways are present in the virtual hub, this operation as well as any other write operation on the connected VNet can cause disconnection to Point-to-site clients as well as reconnection of site-to-site tunnels and BGP sessions.
 
 ## Add a connection