freshness check

cherylmc · cherylmc · commit a9d0c06592e8 · 2025-03-10T11:32:38.000-04:00
diff --git a/articles/virtual-wan/TOC.yml b/articles/virtual-wan/TOC.yml
@@ -12,6 +12,7 @@
   - name: About Virtual WAN pricing
     href: pricing-concepts.md
   - name: Quickstarts
+    expanded: true
     items:
     - name: Configure a site-to-site connection
       href: virtual-wan-site-to-site-portal.md
diff --git a/articles/virtual-wan/virtual-wan-site-to-site-portal.md b/articles/virtual-wan/virtual-wan-site-to-site-portal.md
@@ -5,7 +5,7 @@ description: Learn how to use Azure Virtual WAN to create a site-to-site VPN con
 author: cherylmc
 ms.service: azure-virtual-wan
 ms.topic: tutorial
-ms.date: 12/12/2024
+ms.date: 03/10/2025
 ms.author: cherylmc
 # Customer intent: As someone with a networking background, I want to connect my local site to my VNets using Virtual WAN and I don't want to go through a Virtual WAN partner.
 ---
@@ -29,7 +29,7 @@ In this tutorial you learn how to:
 > * View or edit your VPN gateway
 
 > [!NOTE]
-> If you have many sites, you typically would use a [Virtual WAN partner](https://aka.ms/virtualwan) to create this configuration. However, you can create this configuration yourself if you are comfortable with networking and proficient at configuring your own VPN device.
+> If you have many sites, you typically would use a [Virtual WAN partner](https://aka.ms/virtualwan) to create this configuration. However, you can create this configuration yourself if you're comfortable with networking and proficient at configuring your own VPN device.
 >
 
 ## Prerequisites
@@ -62,7 +62,7 @@ In this section, you configure site-to-site connectivity settings, and then crea
 
 In this section, you create a site. Sites correspond to your physical locations. Create as many sites as you need. These sites contain your on-premises VPN device endpoints.
 
-For example, if you have a branch office in NY, a branch office in London, and a branch office in LA, you'd create three separate sites. You can create up to 1000 sites per virtual hub in a virtual WAN. If you have multiple virtual hubs, you can create 1000 per each virtual hub.
+For example, if you have a branch office in NY, a branch office in London, and a branch office in LA, you'd create three separate sites. You can create up to 1,000 sites per virtual hub in a virtual WAN. If you have multiple virtual hubs, you can create 1000 per each virtual hub.
 
 If you have a Virtual WAN partner CPE device, check with them to learn about their automation to Azure. Typically, automation implies a simple click experience to export large-scale branch information into Azure, and setting up connectivity from the CPE to Azure Virtual WAN VPN gateway. For more information, see [Automation guidance from Azure to CPE partners](virtual-wan-configure-automation-providers.md).
 
@@ -98,7 +98,7 @@ Use the VPN device configuration file to configure your on-premises VPN device.
 
 The device configuration file contains the settings to use when configuring your on-premises VPN device. When you view this file, notice the following information:
 
-* **vpnSiteConfiguration -** This section denotes the device details set up as a site connecting to the virtual WAN. It includes the name and public IP address of the branch device.
+* **vpnSiteConfiguration -** This section denotes the device details configured as a site connecting to the virtual WAN. It includes the name and public IP address of the branch device.
 * **vpnSiteConnections -** This section provides information about the following settings:
 
     * **Address space** of the virtual hub(s) virtual network.<br>Example:
@@ -117,7 +117,7 @@ The device configuration file contains the settings to use when configuring your
         "Instance0":"104.45.18.186"
         "Instance1":"104.45.13.195"
         ```
-    * **Vpngateway connection configuration details** such as BGP, preshared key etc. The PSK is the preshared key that is automatically generated for you. You can always edit the connection in the **Overview** page for a custom PSK.
+    * **Vpngateway connection configuration details** such as BGP, preshared key, etc. The PSK is the preshared key that is automatically generated for you. You can always edit the connection in the **Overview** page for a custom PSK.
   
 ### Example device configuration file
 
@@ -227,7 +227,7 @@ The device configuration file contains the settings to use when configuring your
 ### <a name="vpn-device"></a>Configuring your VPN device
 
 > [!NOTE]
-> If you are working with a Virtual WAN partner solution, VPN device configuration automatically happens. The device controller obtains the configuration file from Azure and applies to the device to set up connection to Azure. This means you don't need to know how to manually configure your VPN device.
+> If you're working with a Virtual WAN partner solution, VPN device configuration automatically happens. The device controller obtains the configuration file from Azure and applies to the device to set up connection to Azure. This means you don't need to know how to manually configure your VPN device.
 >
 
 If you need instructions to configure your device, you can use the instructions on the [VPN device configuration scripts page](~/articles/vpn-gateway/vpn-gateway-about-vpn-devices.md#configscripts) with the following caveats:
diff --git a/includes/virtual-wan-before-include.md b/includes/virtual-wan-before-include.md
@@ -1,7 +1,7 @@
 ---
 author: cherylmc
 ms.author: cherylmc
-ms.date: 04/11/2022
+ms.date: 03/10/2025
 ms.service: azure-virtual-wan
 ms.topic: include
 ---
@@ -10,16 +10,18 @@ ms.topic: include
 
 * You have a virtual network to which you want to connect.
 
-   * Verify that none of the subnets of your on-premises networks overlap with the virtual networks that you want to connect to.
-   * To create a virtual network in the Azure portal, see the [Quickstart](../articles/virtual-network/quick-create-portal.md) article.
+  * Verify that none of the subnets of your on-premises networks overlap with the virtual networks that you want to connect to.
+  * To create a virtual network in the Azure portal, see the [Quickstart](../articles/virtual-network/quick-create-portal.md) article.
 
-* Your virtual network must not have any existing virtual network gateways. 
+    [!INCLUDE [Virtual network values](virtual-wan-virtual-network-example-values.md)]
 
-   * If your virtual network already has gateways (VPN or ExpressRoute), you must remove all of the gateways before proceeding.
-   * This configuration requires that virtual networks connect to the Virtual WAN hub gateway only.
+* Your virtual network must not have any existing virtual network gateways.
+
+  * If your virtual network already has gateways (VPN or ExpressRoute), you must remove all of the gateways before proceeding.
+  * This configuration requires that virtual networks connect to the Virtual WAN hub gateway only.
 
 * Decide the IP address range that you want to use for your virtual hub private address space. This information is used when configuring your virtual hub. A virtual hub is a virtual network that is created and used by Virtual WAN. It's the core of your Virtual WAN network in a region. The address space range must conform the certain rules:
 
-   * The address range that you specify for the hub can't overlap with any of the existing virtual networks that you connect to.
-   * The address range can't overlap with the on-premises address ranges that you connect to.
-   * If you're unfamiliar with the IP address ranges located in your on-premises network configuration, coordinate with someone who can provide those details for you.
+  * The address range that you specify for the hub can't overlap with any of the existing virtual networks that you connect to.
+  * The address range can't overlap with the on-premises address ranges that you connect to.
+  * If you're unfamiliar with the IP address ranges located in your on-premises network configuration, coordinate with someone who can provide those details for you.
diff --git a/includes/virtual-wan-virtual-network-example-values.md b/includes/virtual-wan-virtual-network-example-values.md
@@ -0,0 +1,16 @@
+---
+ms.author: cherylmc
+author: cherylmc
+ms.date: 03/10/2025
+ms.service: azure-virtual-wan
+ms.topic: include
+---
+
+In this exercise, we used the following example values to create the virtual network. You can modify these values when you create your own virtual network.
+
+| Parameter | Value |
+| --- | --- |
+| Resource Group | TestRG |
+| Name | VNet1 |
+| Location/Region | East US |
+| IPv4 address space | 10.11.0.0/16 |
