You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-network-manager/faq.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,7 +67,7 @@ VNets in mesh are automatically in sync. IP prefixes will be updated automatical
67
67
68
68
### How do I verify a mesh topology is configured and applied?"?
69
69
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.
71
71
72
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?
0 commit comments