Skip to content

Commit e2b9015

Browse files
authored
Update concept-connectivity-configuration.md
1 parent 5ab28e6 commit e2b9015

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

articles/virtual-network-manager/concept-connectivity-configuration.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,11 +45,16 @@ When you create a mesh topology or enable direct connectivity in a hub-and-spoke
4545
> [!NOTE]
4646
> A virtual network can be part of up to two connected groups, meaning it can be part of up to two mesh topologies.
4747
48+
### Enable high-scale connectivity in Azure Virtual Network Manager connected groups
49+
50+
Azure Virtual Network Manager's high-scale connectivity feature in connected group feature empowers you to extend your network capacity. To you this feature, please register the preveiw feature "AllowHighScaleConnectedGroup" (you can find it with the Display Name of "Enable High Scale Connected Group
51+
".) This feature allows a connected group in the supported regions to contain up to 5,000 virtual networks.
52+
4853
### Enable high-scale private endpoints in Azure Virtual Network Manager connected groups
4954

5055
[!INCLUDE [virtual-network-manager-high-scale-preview](../../includes/virtual-network-manager-high-scale-preview.md)]
5156

52-
Azure Virtual Network Manager's high-scale connected group feature empowers you to extend your network capacity. Use the following steps to enable this feature to support up to 2,000 private endpoints across the connected group.
57+
Azure Virtual Network Manager's high-scale private endpoint feature in connected group feature empowers you to extend your network capacity. Use the following steps to enable this feature to support up to 20,000 private endpoints across the connected group.
5358

5459
#### Prepare each virtual network in the connected group
5560

0 commit comments

Comments
 (0)