Merge pull request #106354 from cherylmc/vnet

portal

Author: megvanhuygen

articles/vpn-gateway/create-routebased-vpn-gateway-portal.md

@@ -7,7 +7,7 @@ author: cherylmc
 
 ms.service: vpn-gateway
 ms.topic: article
-ms.date: 09/24/2019
+ms.date: 03/03/2020
 ms.author: cherylmc
 ---
 
@@ -19,7 +19,7 @@ The steps in this article will create a VNet, a subnet, a gateway subnet, and a
 
 ## <a name="vnet"></a>Create a virtual network
 
-[!INCLUDE [create-gateway](../../includes/vpn-gateway-create-virtual-network-portal-include.md)]
+[!INCLUDE [Create a virtual network](../../includes/vpn-gateway-basic-vnet-rm-portal-include.md)]
 
 ## <a name="gwvalues"></a>Configure and create the gateway
 

articles/vpn-gateway/vpn-gateway-howto-site-to-site-resource-manager-portal.md

@@ -7,7 +7,7 @@ author: cherylmc
 
 ms.service: vpn-gateway
 ms.topic: conceptual
-ms.date: 01/10/2020
+ms.date: 03/03/2020
 ms.author: cherylmc
 
 ---
@@ -57,7 +57,7 @@ The examples in this article use the following values. You can use these values
 
 ## <a name="CreatVNet"></a>1. Create a virtual network
 
-[!INCLUDE [Create a virtual network](../../includes/vpn-gateway-create-virtual-network-portal-include.md)]
+[!INCLUDE [Create a virtual network](../../includes/vpn-gateway-basic-vnet-rm-portal-include.md)]
 
 ## <a name="VNetGateway"></a>2. Create the VPN gateway
 

includes/media/vpn-gateway-basic-vnet-rm-portal-include/addresses.png

@@ -5,14 +5,14 @@
  author: cherylmc
  ms.service: vpn-gateway
  ms.topic: include
- ms.date: 02/25/2020
+ ms.date: 03/03/2020
  ms.author: cherylmc
  ms.custom: include file
 ---
 You can create a VNet with the Resource Manager deployment model and the Azure portal by following these steps. For more information about virtual networks, see [Virtual Network overview](../articles/virtual-network/virtual-networks-overview.md).
 
 >[!NOTE]
->For the VNet to connect to an on-premises location, coordinate with your on-premises network administrator to carve out an IP address range that you can use specifically for this virtual network. If a duplicate address range exists on both sides of the VPN connection, traffic will route in an unexpected way. Additionally, if you want to connect this VNet to another VNet, the address space cannot overlap with other VNet. Plan your network configuration accordingly.
+>When using a virtual network as part of a cross-premises architecture, be sure to coordinate with your on-premises network administrator to carve out an IP address range that you can use specifically for this virtual network. If a duplicate address range exists on both sides of the VPN connection, traffic will route in an unexpected way. Additionally, if you want to connect this virtual network to another virtual network, the address space cannot overlap with the other virtual network. Plan your network configuration accordingly.
 >
 >
 
@@ -23,21 +23,31 @@ You can create a VNet with the Resource Manager deployment model and the Azure p
 1. Select **Virtual Network** from the **Marketplace** results.
 
    ![Select virtual network](./media/vpn-gateway-basic-vnet-rm-portal-include/marketplace-results.png "Locate virtual network resource page")
-1. On the **Virtual Network** page, click **Create**.
+1. On the **Virtual Network** page, select **Create**.
 
-   ![virtual network page](./media/vpn-gateway-basic-vnet-rm-portal-include/vnet-click-create.png "Click Create")
-1. Once you click create, the **Create virtual network** page opens.
+   ![virtual network page](./media/vpn-gateway-basic-vnet-rm-portal-include/vnet-click-create.png "Select Create")
+1. Once you select **Create**, the **Create virtual network** page opens.
+1. On the **Basics** tab, configure **Project details** and **Instance details** VNet settings.
 
-   ![Create virtual network page](./media/vpn-gateway-basic-vnet-rm-portal-include/create-virtual-network-page.png "Create virtual network page")
-1. On the **Create virtual network** page, configure the VNet settings. When you fill in the fields, the red exclamation mark becomes a green check mark when the characters you enter in the field are validated. Some values are autofilled, which you can replace with your own values:
+   ![Basics tab](./media/vpn-gateway-basic-vnet-rm-portal-include/basics.png "Basics tab") When you fill in the fields, you see a green check mark when the characters you enter in the field are validated. Some values are autofilled, which you can replace with your own values:
 
-   - **Name**: Enter the name for your virtual network.
-   - **Address space**: Enter the address space. If you have multiple address spaces to add, enter your first address space here. You can add additional address spaces later, after you create the VNet. If your configuration requires IPv6 address space, check the checkbox to enter that information.
    - **Subscription**: Verify that the subscription listed is the correct one. You can change subscriptions by using the drop-down.
-   - **Resource group**: Select an existing resource group, or create a new one by entering a name for your new resource group. If you're creating a new group, name the resource group according to your planned configuration values. For more information about resource groups, see [Azure Resource Manager overview](../articles/azure-resource-manager/management/overview.md#resource-groups).
-   - **Location**: Select the location for your VNet. The location determines where the resources that you deploy to this VNet will live.
-   - **Subnet**: Add the subnet **Name** and subnet **Address range**. You can add additional subnets later, after you create the VNet.
-   - **DDos protection**: Select **Basic**, unless you want to use the Standard service.
-   - **Service endpoints**: You can leave this setting as **Disabled**, unless your configuration specifies this setting.
-   - **Firewall**: You can leave this setting as **Disabled**, unless your configuration specifies this setting.
-1. Click **Create** to begin the virtual network deployment.
+   - **Resource group**: Select an existing resource group, or click **Create new** to create a new one. For more information about resource groups, see [Azure Resource Manager overview](../articles/azure-resource-manager/management/overview.md#resource-groups).
+   - **Name**: Enter the name for your virtual network.
+   - **Region**: Select the location for your VNet. The location determines where the resources that you deploy to this VNet will live.
+
+1. On the **IP Addresses** tab, configure the values. The values shown in the examples below are for demonstration purposes. Adjust these values according to the settings that you require.
+
+   ![IP addresses tab](./media/vpn-gateway-basic-vnet-rm-portal-include/addresses.png "IP addresses tab")  
+   - **IPv4 address space**: By default, an address space is automatically created. You can click the address space to adjust it to reflect your own values. You can also add additional address spaces.
+   - **IPv6**: If your configuration requires IPv6 address space, select the **Add IPv6 address space** box to enter that information.
+   - **Subnet**: If you use the default address space, a default subnet is created automatically. If you change the address space, you need to add a subnet. Select **+ Add subnet** to open the **Add subnet** window. Configure the following settings and then select **Add** to add the values:
+      - **Subnet name**: In this example, we named the subnet "FrontEnd".
+      - **Subnet address range**: The address range for this subnet.
+
+1. On the **Security** tab, at this time, leave the default values:
+
+   - **DDos protection**: Basic
+   - **Firewall**: Disabled
+1. Select **Review + create** to validate the virtual network settings.
+1. After the settings have been validated, select **Create**.