Skip to content

Commit c5e4955

Browse files
authored
Document limitation on moving Azure Virtual Network Manager
Added a limitation regarding the movement of Azure Virtual Network Manager instances between subscriptions.
1 parent ee6b411 commit c5e4955

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

articles/virtual-network-manager/concept-limitations.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,8 @@ This article provides an overview of the current limitations when you're using [
2929

3030
* In Azure China regions, using tags on resource groups and subscriptions in Azure Policy definitions for network group membership isn't currently supported.
3131

32+
* An Azure Virtual Network Manager instance cannot be moved from the existing subscription to another.
33+
3234
## Limitations for connected groups
3335

3436
* A virtual network can be peered with up to 1,000 virtual networks using Azure Virtual Network Manager's hub-and-spoke connectivity configuration, meaning you can peer up to 1,000 spoke virtual networks to a hub virtual network.

0 commit comments

Comments
 (0)