Merge pull request #289187 from aybatra/patch-25

Update virtual-wan-user-groups-considerations.md

Author: JamesJBarnett

includes/virtual-wan-user-groups-considerations.md

@@ -6,7 +6,15 @@ ms.service: azure-virtual-wan
 ms.topic: include
 ---
 
-* The maximum number of groups that can be referenced by a single P2S VPN gateway is 90. The maximum number of policy/group members (criteria used to identify which group a connecting user is a part of) in groups assigned to a gateway is 390. However, if a group is assigned to multiple connection configurations on the same gateway, this group and its members are counted multiple times towards the limits. For example, if there's a policy group with 10 members that is assigned to three VPN connection configurations on the gateway. This configuration would count as three groups with 30 total members as opposed to one group with 10 members. The total number of concurrent users connecting to a gateway is limited by the gateway scale unit and the number of IP addresses allocated to each user group and not the number of policy/group members associated with a gateway.
+* Maximum Groups: A single P2S VPN gateway can reference up to **90 groups.**
+
+* Maximum Members: The total number of policy/group members across all groups assigned to a gateway is **390**.
+  
+* Multiple Assignments: If a group is assigned to multiple connection configurations on the same gateway, it and its members are counted multiple times.
+  Example: A policy group with 10 members assigned to three VPN connection configurations counts as three groups with 30 members, not one group with 10 members.
+  
+* Concurrent Users: The total number of concurrent users is determined by the gateway’s scale unit and the number of IP addresses allocated to each user group.
+It is **not** determined by the number of policy/group members associated with the gateway.
 
 * Once a group has been created as part of a VPN server configuration, the name and default setting of a group can't be modified.