Skip to content

Commit bd4e402

Browse files
author
Michael Bender
committed
FAQ update - connected groups vs. peering
1 parent 3172461 commit bd4e402

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
@@ -90,7 +90,7 @@ Should a regional outage occur, all configurations applied to current resources
9090

9191
Yes, you can choose to override and delete an existing peering already created, or allow them to coexist with those created by Azure Virtual Network Manager.
9292

93-
### How do connected groups differ from Virtual Network Peering?
93+
### How do connected groups differ from virtual network peering regarding establishing connectivity between virtual networks?
9494

9595
In Azure, VNet peering and connected groups are two methods of establishing connectivity between virtual networks (VNets). While VNet peering works by creating a 1:1 mapping between each peered VNet, connected groups use a new construct that establishes connectivity without such a mapping. In a connected group, all virtual networks are connected without individual peering relationships. For example, if VNetA, VNetB, and VNetC are part of the same connected group, connectivity is enabled between each VNet without the need for individual peering relationships.
9696

0 commit comments

Comments
 (0)