Merge pull request #216350 from wtnlee/patch-50

Update user-groups-create.md

Author: prmerger-automator[bot]

articles/virtual-wan/user-groups-create.md

@@ -113,7 +113,8 @@ Before beginning, make sure you've configured a virtual WAN that uses one or mor
 1. Every address pool specified on the gateway. Address pools are split into two address pools and assigned to each active-active instance in a point-to-site VPN gateway pair. These split addresses should show up in the effective route table. For example, if you specify 10.0.0.0/24, you should see two /25 routes in the effective route table. If this isn't the case, try changing the address pools defined on the gateway.
 1. Make sure all point-to-site VPN connection configurations are associated to the defaultRouteTable and propagate to the same set of route tables. This should be configured automatically if you're using portal, but if you're using REST, PowerShell or CLI, make sure all propagations and associations are set appropriately.
 1. If you're using the Azure VPN client, make sure the Azure VPN client installed on user devices are the latest version.
+1. If you're using Azure Active Directory authentication, please make sure the tenant URL input in the server configuration (`https://login.microsoftonline.com/<tenant ID>`) does **not** end in a `\`. If the URL is input to end with `\`, the Gateway will not be able to properly process Azure Active Directory user groups and all users will be assigned to the default group. To remediate, please modify the server configuration to remove the trailing `\` and modify the address pools configured on the gateway to apply the changes to the gateway. This is a known issue that will be fixed in a later relase.
 
 ## Next steps
 
-* For more information about user groups, see [About user groups and IP address pools for P2S User VPNs](user-groups-about.md).
+* For more information about user groups, see [About user groups and IP address pools for P2S User VPNs](user-groups-about.md).