Skip to content

Commit 68e1cbe

Browse files
committed
freshness review
1 parent ace07a5 commit 68e1cbe

File tree

5 files changed

+12
-12
lines changed

5 files changed

+12
-12
lines changed

articles/virtual-wan/site-to-site-powershell.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ author: cherylmc
88
ms.service: azure-virtual-wan
99
ms.custom: devx-track-azurepowershell
1010
ms.topic: how-to
11-
ms.date: 06/15/2023
11+
ms.date: 03/27/2025
1212
ms.author: cherylmc
1313
---
1414
# Create a site-to-site connection to Azure Virtual WAN using PowerShell
@@ -64,7 +64,7 @@ $virtualHub = New-AzVirtualHub -VirtualWan $virtualWan -ResourceGroupName "TestR
6464

6565
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.
6666

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.
6868

6969
```azurepowershell-interactive
7070
$virtualHub = Get-AzVirtualHub -ResourceGroupName "TestRG" -Name "Hub1"
@@ -84,7 +84,7 @@ In this section, you create a site-to-site VPN gateway in the same location as t
8484

8585
## <a name="site"></a>Create a site and connections
8686

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.
8888

8989
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.
9090

@@ -102,7 +102,7 @@ In this section, you create sites that correspond to your physical locations and
102102
$vpnSiteLink2 = New-AzVpnSiteLink -Name "TestSite1Link2" -IpAddress "15.25.35.55" -LinkProviderName "SomeTelecomProvider2" -LinkSpeedInMbps "100"
103103
```
104104

105-
1. Create the VPN site, referencing the variables of the VPN site links you just created.
105+
1. Create the VPN site, referencing the variables of the VPN site links you created.
106106

107107
If you closed Azure Cloud Shell or your connection timed out, redeclare the virtual WAN variable:
108108

@@ -127,7 +127,7 @@ In this section, you create sites that correspond to your physical locations and
127127

128128
Connect your VPN site to the hub site-to-site VPN gateway using the [New-AzVpnConnection](/powershell/module/az.network/new-azvpnconnection) cmdlet.
129129

130-
1. Before running the command, you may need to redeclare the following variables:
130+
1. Before running the command, you might need to redeclare the following variables:
131131

132132
```azurepowershell-interactive
133133
$virtualWan = Get-AzVirtualWAN -ResourceGroupName "TestRG" -Name "TestVWAN1"
@@ -143,7 +143,7 @@ Connect your VPN site to the hub site-to-site VPN gateway using the [New-AzVpnCo
143143

144144
## Connect a VNet to your hub
145145

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.
147147

148148
### Create a virtual network
149149

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn about using user groups to assign IP addresses from specific
55
author: cherylmc
66
ms.service: azure-virtual-wan
77
ms.topic: concept-article
8-
ms.date: 07/31/2023
8+
ms.date: 03/27/2025
99
ms.author: cherylmc
1010

1111
---
@@ -68,13 +68,13 @@ This section lists configuration requirements and limitations for user groups an
6868

6969
## Use cases
7070

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.
7272

7373
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.
7474

7575
* 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.
7676

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.
7878

7979
## Next steps
8080

articles/virtual-wan/virtual-wan-ipsec.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: virtual-wan
66
author: cherylmc
77
ms.service: azure-virtual-wan
88
ms.topic: conceptual
9-
ms.date: 07/28/2023
9+
ms.date: 03/27/2025
1010
ms.author: cherylmc
1111
#Customer intent: As a Virtual WAN software-defined connectivity provider, I want to know the IPsec policies
1212
---

includes/virtual-wan-ipsec-custom-include.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
author: cherylmc
66
ms.service: azure-virtual-wan
77
ms.topic: include
8-
ms.date: 09/12/2023
8+
ms.date: 03/27/2025
99
ms.author: cherylmc
1010
ms.custom: include file
1111
---

includes/virtual-wan-ipsec-include.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
author: cherylmc
66
ms.service: azure-virtual-wan
77
ms.topic: include
8-
ms.date: 12/07/2021
8+
ms.date: 03/27/2025
99
ms.author: cherylmc
1010
ms.custom: include file
1111
---

0 commit comments

Comments
 (0)