You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this section, you create a site-to-site VPN gateway in the same location as the referenced virtual hub. When you create the VPN gateway, you specify the scale units that you want. It takes about 30 minutes for the gateway to create.
66
66
67
-
1. If you closed Azure Cloud Shell or your connection timed out, you may need to declare the variable again for $virtualHub.
67
+
1. If you closed Azure Cloud Shell or your connection timed out, you might need to declare the variable again for $virtualHub.
@@ -84,7 +84,7 @@ In this section, you create a site-to-site VPN gateway in the same location as t
84
84
85
85
## <aname="site"></a>Create a site and connections
86
86
87
-
In this section, you create sites that correspond to your physical locations and the connections. These sites contain your on-premises VPN device endpoints, you can create up to 1000 sites per virtual hub in a virtual WAN. If you have multiple hubs, you can create 1000 per each of those hubs.
87
+
In this section, you create sites that correspond to your physical locations and the connections. These sites contain your on-premises VPN device endpoints. You can create up to 1,000 sites per virtual hub in a virtual WAN. If you have multiple hubs, you can create 1000 per each of those hubs.
88
88
89
89
1. Set the variable for the VPN gateway and for the IP address space that is located on your on-premises site. Traffic destined for this address space is routed to your local site. This is required when BGP isn't enabled for the site.
90
90
@@ -102,7 +102,7 @@ In this section, you create sites that correspond to your physical locations and
@@ -143,7 +143,7 @@ Connect your VPN site to the hub site-to-site VPN gateway using the [New-AzVpnCo
143
143
144
144
## Connect a VNet to your hub
145
145
146
-
The next step is to connect the hub to the VNet. If you created a new resource group for this exercise, you typically won't already have a virtual network (VNet) in your resource group. The steps below help you create a VNet if you don't already have one. You can then create a connection between the hub and your VNet.
146
+
The next step is to connect the hub to the virtual network (VNet). If you created a new resource group for this exercise, you typically won't already have a VNet in your resource group. The following steps help you create a VNet if you don't already have one. You can then create a connection between the hub and your VNet.
Copy file name to clipboardExpand all lines: articles/virtual-wan/user-groups-about.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Learn about using user groups to assign IP addresses from specific
5
5
author: cherylmc
6
6
ms.service: azure-virtual-wan
7
7
ms.topic: concept-article
8
-
ms.date: 07/31/2023
8
+
ms.date: 03/27/2025
9
9
ms.author: cherylmc
10
10
11
11
---
@@ -68,13 +68,13 @@ This section lists configuration requirements and limitations for user groups an
68
68
69
69
## Use cases
70
70
71
-
Contoso corporation is composed of multiple functional departments, such as Finance, Human Resources and Engineering. Contoso uses Azure Virtual WAN to allow remote workers (users) to connect to the virtual WAN and access resources hosted on-premises or in a virtual network connected to the virtual WAN hub.
71
+
Contoso corporation is composed of multiple functional departments, such as Finance, Human Resources, and Engineering. Contoso uses Azure Virtual WAN to allow remote workers (users) to connect to the virtual WAN and access resources hosted on-premises or in a virtual network connected to the virtual WAN hub.
72
72
73
73
However, Contoso has internal security policies where users from the Finance department can only access certain databases and virtual machines, and users from Human Resources have access to other sensitive applications.
74
74
75
75
* Contoso can configure different user groups for each of their functional departments. This ensures users from each department are assigned IP addresses from a department-level predefined address pool.
76
76
77
-
* Contoso's network administrator can then configure Firewall rules, network security groups (NSG) or access control lists (ACLs) to allow or deny certain users access to resources based on their IP addresses.
77
+
* Contoso's network administrator can then configure Firewall rules, network security groups (NSG), or access control lists (ACLs) to allow or deny certain users access to resources based on their IP addresses.
0 commit comments