Skip to content

Commit 257fa59

Browse files
Merge pull request #291528 from mbender-ms/patch-990819
virtual network manager - Update faq.md
2 parents b4a233f + 7186f39 commit 257fa59

File tree

1 file changed

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

1 file changed

+19
-5
lines changed

articles/virtual-network-manager/faq.md

Lines changed: 19 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,9 @@ services: virtual-network-manager
55
author: mbender-ms
66
ms.service: azure-virtual-network-manager
77
ms.topic: faq
8-
ms.date: 01/30/2024
8+
ms.date: 11/25/2024
99
ms.author: mbender
10-
ms.custom:
11-
- references_regions
12-
- engagement-fy23
13-
- ignite-2023
10+
ms.custom: reference_regions
1411
---
1512

1613
# Azure Virtual Network Manager FAQ
@@ -51,6 +48,7 @@ You can deploy and manage an Azure Virtual Network Manager instance and configur
5148
* [Azure portal](./create-virtual-network-manager-portal.md)
5249
* [Azure CLI](./create-virtual-network-manager-cli.md)
5350
* [Azure PowerShell](./create-virtual-network-manager-powershell.md)
51+
* [ARM Template](./create-virtual-network-manager-template.md)
5452
* [Terraform](./create-virtual-network-manager-terraform.md)
5553

5654
## Technical
@@ -59,6 +57,22 @@ You can deploy and manage an Azure Virtual Network Manager instance and configur
5957

6058
Yes, a virtual network can belong to more than one Azure Virtual Network Manager instance.
6159

60+
### Can spoke VNets be connected to a VWAN hub while in a mesh topology so that those spoke VNets can communicate directly?
61+
62+
Yes, spoke VNets can connect to VWAN hubs while in the mesh group. Those VNets in the mesh group have direct connectivity.
63+
64+
### Will operations to the IP prefixes in VNETs that are a part of the Azure Virtual Network Manager mesh propagate automatically?
65+
66+
VNets in mesh are automatically in sync. IP prefixes will be updated automatically. This means that traffic within the mesh will work even after there are changes in IP prefixes in VNets in the mesh.
67+
68+
### How do I verify a mesh topology is configured and applied?"?
69+
70+
Please refer to the documentation [How to view applied configurations](/azure/virtual-network-manager/how-to-view-applied-configurations?branch=main). A mesh topology is not a VNet peering, so you cannot see mesh connectivity in peering.
71+
72+
### What happens if the region where the Azure Virtual Network Manager is created is down? Does it affect deployed configurations or only prevent configuration changes?
73+
74+
Only the ability to change configurations will be impacted. Once Azure Virtual Network Manager has programmed the configuration after you commit the configuration, it will continue to operate. For example, if the Azure Virtual Network Manager instance is created in region 1 and the mesh topology is established in region 2, the mesh in region 2 will continue to function even if region 1 becomes unavailable.
75+
6276
### What is a global mesh network topology?
6377

6478
A global mesh allows for virtual networks across regions to communicate with one another. The effects are similar to how global virtual network peering works.

0 commit comments

Comments
 (0)