Skip to content

Commit 06ccd73

Browse files
authored
Merge pull request #124803 from mrstruck/patch-1
Update faq.md - Azure Virtual Network Manager
2 parents b335e3c + e9a9883 commit 06ccd73

File tree

1 file changed

+5
-0
lines changed
  • articles/virtual-network-manager

1 file changed

+5
-0
lines changed

articles/virtual-network-manager/faq.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -95,6 +95,11 @@ No. Azure Virtual Network Manager doesn't store any customer data.
9595

9696
No. Azure Virtual Network Manager doesn't currently support that capability. If you need to move an instance, you can consider deleting it and using the Azure Resource Manager template to create another one in another location.
9797

98+
### Can I move a subscription with an Azure Virtual Network Manager to another tenant?
99+
Yes, but there are some considerations to keep in mind:
100+
- The target tenant cannot have an Azure Virtual Network Manager created.
101+
- The spokes virtual networks in the network group may lose their reference when changing tenants, thus losing connectivity to the hub vnet. To resolve this, after moving the subscription to another tenant, you must manually add the spokes vnets to the network group of Azure Virtual Network Manager.
102+
98103
### How can I see what configurations are applied to help me troubleshoot?
99104

100105
You can view Azure Virtual Network Manager settings under **Network Manager** for a virtual network. The settings show both connectivity and security admin configurations that are applied. For more information, see [View configurations applied by Azure Virtual Network Manager](how-to-view-applied-configurations.md).

0 commit comments

Comments
 (0)