Skip to content

Commit 012cf33

Browse files
committed
updated url
1 parent 09c1fcd commit 012cf33

File tree

1 file changed

+1
-1
lines changed
  • articles/virtual-network-manager

1 file changed

+1
-1
lines changed

articles/virtual-network-manager/faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ VNets in mesh are automatically in sync. IP prefixes will be updated automatical
6767

6868
### How do I verify a mesh topology is configured and applied?"?
6969

70-
Please refer to the documentation [How to view applied configurations](how-to-view-applied-configurations). A mesh topology is not a VNet peering, so you cannot see mesh connectivity in peering.
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.
7171

7272
### 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?
7373

0 commit comments

Comments
 (0)