Merge pull request #86580 from tfitzmac/0826move

failed state moved

Author: PRMerger18

articles/azure-resource-manager/move-limitations/networking-move-limitations.md

@@ -18,10 +18,6 @@ When moving a virtual network, you must also move its dependent resources. For V
 
 To move a virtual machine with a network interface card, you must move all dependent resources. Move the virtual network for the network interface card, all other network interface cards for the virtual network, and the VPN gateways.
 
-## State of dependent resources
-
-If the source or target resource group contains a virtual network, the states of all dependent resources for the virtual network are checked during the move. If any of those resources are in a failed state, the move is blocked. For example, if a virtual machine that uses the virtual network has failed, the move is blocked. The move is blocked even when the virtual machine isn't one of the resources being moved and isn't in one of the resource groups for the move. To avoid this problem, move your resources to a resource group that doesn't have a virtual network.
-
 ## Peered virtual network
 
 To move a peered virtual network, you must first disable the virtual network peering. Once disabled, you can move the virtual network. After the move, reenable the virtual network peering.

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

@@ -31,8 +31,6 @@ There are some important steps to do before moving a resource. By verifying thes
    * [Recovery Services move guidance](../backup/backup-azure-move-recovery-services-vault.md?toc=/azure/azure-resource-manager/toc.json)
    * [Virtual Machines move guidance](./move-limitations/virtual-machines-move-limitations.md)
 
-   If the destination resource group contains a virtual network, the state of its dependent resources can block the move, even when those resources aren't involved in the move. For more information, see [Networking move guidance](./move-limitations/virtual-network-move-limitations.md).
-
 1. The source and destination subscriptions must be active. If you have trouble enabling an account that has been disabled, [create an Azure support request](../azure-supportability/how-to-create-azure-support-request.md). Select **Subscription Management** for the issue type.
 
 1. The source and destination subscriptions must exist within the same [Azure Active Directory tenant](../active-directory/develop/quickstart-create-new-tenant.md). To check that both subscriptions have the same tenant ID, use Azure PowerShell or Azure CLI.

articles/azure-resource-manager/troubleshoot-move.md

@@ -38,7 +38,9 @@ When possible, break large moves into separate move operations. Resource Manager
 
 ## Resource not in succeeded state
 
-If you get an error message that indicates a resource can't be moved because it isn't in a succeeded state, it may actually be a dependent resource that is blocking the move. See [State of dependent resources](./move-limitations/networking-move-limitations.md#state-of-dependent-resources).
+When you get an error message that indicates a resource can't be moved because it isn't in a succeeded state, it may actually be a dependent resource that is blocking the move.
+
+If the source or target resource group contains a virtual network, the states of all dependent resources for the virtual network are checked during the move. If any of those resources are in a failed state, the move is blocked. For example, if a virtual machine that uses the virtual network has failed, the move is blocked. The move is blocked even when the virtual machine isn't one of the resources being moved and isn't in one of the resource groups for the move. To avoid this problem, move your resources to a resource group that doesn't have a virtual network.
 
 ## Next steps