Skip to content

Commit 3172461

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

File tree

1 file changed

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

1 file changed

+4
-0
lines changed

articles/virtual-network-manager/faq.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -90,6 +90,10 @@ 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?
94+
95+
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.
96+
9397
### How can I explicitly allow Azure SQL Managed Instance traffic before having deny rules?
9498

9599
Azure SQL Managed Instance has some network requirements. If your security admin rules can block the network requirements, you can use the below sample rules to allow SQLMI traffic with higher priority than the deny rules that can block the traffic of SQL Managed Instance.

0 commit comments

Comments
 (0)