Merge pull request MicrosoftDocs#1913 from FrankSiegemund/movefix

Clarify that a virtual network cannot move when it has a resource nav…

Author: jomolnar

articles/azure-resource-manager/resource-group-move-resources.md

@@ -113,7 +113,9 @@ For now, the services that enable moving to both a new resource group and subscr
 * Virtual Machines - Does not support move to a new subscription when its certificates are stored in a Key Vault
 * Virtual Machines (classic) - see [Classic deployment limitations](#classic-deployment-limitations)
 * Virtual Machine Scale Sets
-* Virtual Networks - Currently, a peered Virtual Network cannot be moved until VNet peering has been disabled. Once disabled, the Virtual Network can be moved successfully and the VNet peering can be enabled.
+* Virtual Networks - Currently, a peered Virtual Network cannot be moved until VNet peering has been disabled. Once disabled, the Virtual Network can be moved successfully and the VNet peering can be enabled. In addition, 
+a Virtual Network cannot be moved to a different subscription if the Virtual Network contains any subnet with resource navigation links. For example, a Virtual Network subnet has a resource navigation link when a Microsoft.Cache
+redis resource is deployed into this subnet.
 * VPN Gateway