Merge pull request #51278 from Tbohunek/patch-1

Describe error The remote virtual network lacks a gateway

Author: ktoliver

articles/virtual-network/virtual-network-troubleshoot-peering-issues.md

@@ -231,6 +231,15 @@ To resolve this issue, delete the peering from both virtual networks, and then r
 
 To resolve this issue, configure the virtual network peering under **Azure Databricks**, and then specify the target virtual network by using **Resource ID**. For more information, see [Peer a Databricks virtual network to a remote virtual network](https://docs.azuredatabricks.net/administration-guide/cloud-configurations/azure/vnet-peering.html#id2).
 
+### The remote virtual network lacks a gateway
+
+This issue occurs when you peer virtual networks from different tenants and later want to configure `Use Remote Gateways`. A limitation of the Azure portal is that it can't validate the presence of a virtual network gateway in another tenant's virtual network.
+
+There are two ways to resolve the issue:
+
+ * Delete the peerings and activate the `Use Remote Gateways` option when you create a new peering.
+ * Use PowerShell or CLI, instead of the Azure portal, to enable `Use Remote Gateways`.
+
 ## Next steps
 
 * [Troubleshooting connectivity problems between Azure VMs](https://docs.microsoft.com/azure/virtual-network/virtual-network-troubleshoot-connectivity-problem-between-vms)