Skip to content

Commit b8e7fa5

Browse files
tfitzmactfitzmac
committed
added vnet dependency move
1 parent 96e78ef commit b8e7fa5

File tree

6 files changed

+32
-16
lines changed

6 files changed

+32
-16
lines changed

‎.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3290,6 +3290,11 @@
32903290
"redirect_url": "/azure/azure-portal/azure-portal-dashboards",
32913291
"redirect_document_id": false
32923292
},
3293+
{
3294+
"source_path": "articles/azure-resource-manager/move-limitations/virtual-network-move-limitations.md",
3295+
"redirect_url": "/azure/azure-resource-manager/move-limitations/networking-move-limitations",
3296+
"redirect_document_id": false
3297+
},
32933298
{
32943299
"source_path": "articles/azure-resource-manager/resource-manager-powershell-sas-token.md",
32953300
"redirect_url": "/azure/azure-resource-manager/secure-template-with-sas-token",

‎articles/azure-resource-manager/move-limitations/virtual-network-move-limitations.md renamed to ‎articles/azure-resource-manager/move-limitations/networking-move-limitations.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,27 @@
11
---
2-
title: Move Azure Virtual Networks resources to new subscription or resource group | Microsoft Docs
3-
description: Use Azure Resource Manager to move virtual networks to a new resource group or subscription.
2+
title: Move Azure Networking resources to new subscription or resource group | Microsoft Docs
3+
description: Use Azure Resource Manager to move virtual networks and other networking resources to a new resource group or subscription.
44
author: tfitzmac
55
ms.service: azure-resource-manager
66
ms.topic: conceptual
7-
ms.date: 07/09/2019
7+
ms.date: 08/19/2019
88
ms.author: tomfitz
99
---
1010

11-
# Move guidance for virtual networks
11+
# Move guidance for networking resources
1212

13-
This article describes how to move virtual networks for specific scenarios.
13+
This article describes how to move virtual networks and other networking resources for specific scenarios.
1414

1515
## Dependent resources
1616

1717
When moving a virtual network, you must also move its dependent resources. For VPN Gateways, you must move IP addresses, virtual network gateways, and all associated connection resources. Local network gateways can be in a different resource group.
1818

1919
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.
2020

21+
## State of dependent resources
22+
23+
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.
24+
2125
## Peered virtual network
2226

2327
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/move-support-resources.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Lists the Azure resource types that can be moved to a new resource
44
author: tfitzmac
55
ms.service: azure-resource-manager
66
ms.topic: reference
7-
ms.date: 7/9/2019
7+
ms.date: 07/09/2019
88
ms.author: tomfitz
99
---
1010

@@ -258,7 +258,7 @@ Jump to a resource provider namespace:
258258
| redis | Yes | Yes |
259259

260260
> [!IMPORTANT]
261-
> If the Azure Cache for Redis instance is configured with a virtual network, the instance can't be moved to a different subscription. See [Virtual Networks move limitations](./move-limitations/virtual-network-move-limitations.md).
261+
> If the Azure Cache for Redis instance is configured with a virtual network, the instance can't be moved to a different subscription. See [Virtual Networks move limitations](./move-limitations/networking-move-limitations.md).
262262
263263
## Microsoft.Cdn
264264
| Resource type | Resource group | Subscription |
@@ -760,7 +760,7 @@ Jump to a resource provider namespace:
760760
| webapplicationfirewallpolicies | Yes | Yes |
761761

762762
> [!IMPORTANT]
763-
> See [Virtual Networks move guidance](./move-limitations/virtual-network-move-limitations.md).
763+
> See [Networking move guidance](./move-limitations/networking-move-limitations.md).
764764
765765
## Microsoft.NotificationHubs
766766
| Resource type | Resource group | Subscription |

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

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Use Azure Resource Manager to move resources to a new resource grou
44
author: tfitzmac
55
ms.service: azure-resource-manager
66
ms.topic: conceptual
7-
ms.date: 07/09/2019
7+
ms.date: 08/19/2019
88
ms.author: tomfitz
99
---
1010

@@ -27,9 +27,11 @@ There are some important steps to do before moving a resource. By verifying thes
2727
* [App Services move guidance](./move-limitations/app-service-move-limitations.md)
2828
* [Azure DevOps Services move guidance](/azure/devops/organizations/billing/change-azure-subscription?toc=/azure/azure-resource-manager/toc.json)
2929
* [Classic deployment model move guidance](./move-limitations/classic-model-move-limitations.md) - Classic Compute, Classic Storage, Classic Virtual Networks, and Cloud Services
30+
* [Networking move guidance](./move-limitations/networking-move-limitations.md)
3031
* [Recovery Services move guidance](../backup/backup-azure-move-recovery-services-vault.md?toc=/azure/azure-resource-manager/toc.json)
3132
* [Virtual Machines move guidance](./move-limitations/virtual-machines-move-limitations.md)
32-
* [Virtual Networks move guidance](./move-limitations/virtual-network-move-limitations.md)
33+
34+
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).
3335

3436
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.
3537

@@ -92,10 +94,11 @@ There are some important steps to do before moving a resource. By verifying thes
9294
1. **For a move across subscriptions, the resource and its dependent resources must be located in the same resource group and they must be moved together.** For example, a VM with managed disks would require the VM and the managed disks to be moved together, along with other dependent resources.
9395

9496
If you're moving a resource to a new subscription, check to see whether the resource has any dependent resources, and whether they're located in the same resource group. If the resources aren't in the same resource group, check to see whether the resources can be consolidated into the same resource group. If so, bring all these resources into the same resource group by using a move operation across resource groups.
95-
96-
For more information, see [Scenario for move across subscriptions](#scenario-for-move-across-subscriptions).
97+
98+
For more information, see [Scenario for move across subscriptions](#scenario-for-move-across-subscriptions).
9799

98100
## Scenario for move across subscriptions
101+
99102
Moving resources from one subscription to another is a three-step process:
100103

101104
![cross-subscription move scenario](./media/resource-group-move-resources/cross-subscription-move-scenario.png)

‎articles/azure-resource-manager/toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -146,12 +146,12 @@
146146
href: /azure/devops/organizations/billing/change-azure-subscription?toc=/azure/azure-resource-manager/toc.json
147147
- name: Classic deployment
148148
href: ./move-limitations/classic-model-move-limitations.md
149+
- name: Networking
150+
href: ./move-limitations/networking-move-limitations.md
149151
- name: Recovery Services
150152
href: ../backup/backup-azure-move-recovery-services-vault.md?toc=/azure/azure-resource-manager/toc.json
151153
- name: Virtual Machines
152154
href: ./move-limitations/virtual-machines-move-limitations.md
153-
- name: Virtual Networks
154-
href: ./move-limitations/virtual-network-move-limitations.md
155155
- name: Tags
156156
items:
157157
- name: Tag resources

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

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Use Azure Resource Manager to move resources to a new resource grou
44
author: tfitzmac
55
ms.service: azure-resource-manager
66
ms.topic: conceptual
7-
ms.date: 07/09/2019
7+
ms.date: 08/19/2019
88
ms.author: tomfitz
99
---
1010

@@ -28,14 +28,18 @@ Some services require additional considerations when moving resources. If you're
2828
* [App Services](./move-limitations/app-service-move-limitations.md)
2929
* [Azure DevOps Services](/azure/devops/organizations/billing/change-azure-subscription?toc=/azure/azure-resource-manager/toc.json)
3030
* [Classic deployment model](./move-limitations/classic-model-move-limitations.md)
31+
* [Networking](./move-limitations/networking-move-limitations.md)
3132
* [Recovery Services](../backup/backup-azure-move-recovery-services-vault.md?toc=/azure/azure-resource-manager/toc.json)
3233
* [Virtual Machines](./move-limitations/virtual-machines-move-limitations.md)
33-
* [Virtual Networks](./move-limitations/virtual-network-move-limitations.md)
3434

3535
## Large requests
3636

3737
When possible, break large moves into separate move operations. Resource Manager immediately returns an error when there are more than 800 resources in a single operation. However, moving less than 800 resources may also fail by timing out.
3838

39+
## Resource not in succeeded state
40+
41+
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).
42+
3943
## Next steps
4044

4145
For commands to move resources, see [Move resources to new resource group or subscription](resource-group-move-resources.md).

0 commit comments

Comments
 (0)