Merge pull request #280237 from cherylmc/local

update

Author: JamesJBarnett

articles/vpn-gateway/add-remove-site-to-site-connections.md

@@ -5,7 +5,7 @@ titleSuffix: Azure VPN Gateway
 author: cherylmc
 ms.service: vpn-gateway
 ms.topic: how-to
-ms.date: 10/25/2023
+ms.date: 07/08/2024
 ms.author: cherylmc
 
 ---
@@ -33,11 +33,9 @@ Verify the following items:
 
 ## <a name="local"></a>Create a local network gateway
 
-Create a local network gateway that represents the branch or location you want to connect to.
+The local network gateway is a specific object deployed to Azure that represents your on-premises location (the site) for routing purposes. You give the site a name by which Azure can refer to it, then specify the IP address of the on-premises VPN device to which you'll create a connection. You also specify the IP address prefixes that will be routed through the VPN gateway to the VPN device. The address prefixes you specify are the prefixes located on your on-premises network. If your on-premises network changes or you need to change the public IP address for the VPN device, you can easily update the values later.
 
-The local network gateway is a specific object that represents your on-premises location (the site) for routing purposes. You give the site a name by which Azure can refer to it, then specify the IP address of the on-premises VPN device to which you'll create a connection. You also specify the IP address prefixes that will be routed through the VPN gateway to the VPN device. The address prefixes you specify are the prefixes located on your on-premises network. If your on-premises network changes or you need to change the public IP address for the VPN device, you can easily update the values later.
-
-In this example, we create a local network gateway using the following values.
+Create a local network gateway using the following example values:
 
 * **Name:** Site1
 * **Resource Group:** TestRG1
@@ -56,9 +54,7 @@ Site-to-site connections to an on-premises network require a VPN device. In this
 
 ## <a name="configure"></a>Configure a connection
 
-Create a site-to-site VPN connection between your virtual network gateway and your on-premises VPN device.
-
-Create a connection using the following values:
+Create a site-to-site VPN connection between your virtual network gateway and your on-premises VPN device. In this section, we use the following example values:
 
 * **Local network gateway name:** Site1
 * **Connection name:** VNet1toSite1

articles/vpn-gateway/tutorial-site-to-site-portal.md

@@ -96,11 +96,7 @@ To view public IP addresses associated to your virtual network gateway, navigate
 
 ## <a name="LocalNetworkGateway"></a>Create a local network gateway
 
-The local network gateway is a specific object that represents your on-premises location (the site) for routing purposes. You give the site a name by which Azure can refer to it, and then specify the IP address of the on-premises VPN device to which you create a connection. You also specify the IP address prefixes that are routed through the VPN gateway to the VPN device. The address prefixes you specify are the prefixes located on your on-premises network. If your on-premises network changes or you need to change the public IP address for the VPN device, you can easily update the values later.
-
-
-> [!Note]
-> The local network gateway object is deployed in Azure, not to your on-premises location.
+The local network gateway is a specific object deployed to Azure that represents your on-premises location (the site) for routing purposes. You give the site a name by which Azure can refer to it, and then specify the IP address of the on-premises VPN device to which you create a connection. You also specify the IP address prefixes that are routed through the VPN gateway to the VPN device. The address prefixes you specify are the prefixes located on your on-premises network. If your on-premises network changes or you need to change the public IP address for the VPN device, you can easily update the values later.
 
 Create a local network gateway by using the following values:
 

includes/vpn-gateway-about-gwsubnet-portal-include.md

@@ -1,17 +1,11 @@
 ---
- title: include file
- description: include file
- services: vpn-gateway
- author: cherylmc
- ms.service: vpn-gateway
- ms.topic: include
- ms.date: 01/16/2024
- ms.author: cherylmc
- ms.custom: include file
+ms.author: cherylmc
+author: cherylmc
+ms.date: 07/08/2024
+ms.service: vpn-gateway
+ms.topic: include
 ---
 
 The virtual network gateway requires a specific subnet named **GatewaySubnet**. The gateway subnet is part of the IP address range for your virtual network and contains the IP addresses that the virtual network gateway resources and services use.
 
-When you create the gateway subnet, you specify the number of IP addresses that the subnet contains. The number of IP addresses needed depends on the VPN gateway configuration that you want to create. Some configurations require more IP addresses than others. It's best to specify /27 or larger (/26, /25, etc.) for your gateway subnet.
-
-If you see an error that specifies that the address space overlaps with a subnet, or that the subnet isn't contained within the address space for your virtual network, check your virtual network address range. You might not have enough IP addresses available in the address range you created for your virtual network. For example, if your default subnet encompasses the entire address range, there are no IP addresses left to create more subnets. You can either adjust your subnets within the existing address space to free up IP addresses or specify another address range and create the gateway subnet there.
+When you create the gateway subnet, you specify the number of IP addresses that the subnet contains. The number of IP addresses needed depends on the VPN gateway configuration that you want to create. Some configurations require more IP addresses than others. It's best to specify /27 or larger (/26, /25, etc.) for your gateway subnet.

includes/vpn-gateway-add-local-network-gateway-portal-include.md

@@ -1,35 +1,31 @@
 ---
- title: include file
- description: include file
- services: vpn-gateway
  author: cherylmc
  ms.service: vpn-gateway
  ms.topic: include
- ms.date: 04/16/2024
+ ms.date: 07/08/2024
  ms.author: cherylmc
- ms.custom: include file
 ---
-1. In the [Azure portal](https://portal.azure.com), in **Search resources, services, and docs (G+/)**, enter **local network gateway**. Locate **local network gateway** under **Marketplace** in the search results and select it to open the **Create local network gateway** page.
-1. On the **Create local network gateway page**, on the **Basics** tab, specify the values for your local network gateway.
 
-   :::image type="content" source="./media/vpn-gateway-add-local-network-gateway-portal-include/basics.png" alt-text="Screenshot that shows creating a local network gateway with IP address." lightbox ="./media/vpn-gateway-add-local-network-gateway-portal-include/basics.png" :::
+Configuration considerations:
+
+* VPN Gateway supports only one IPv4 address for each FQDN. If the domain name resolves to multiple IP addresses, VPN Gateway uses the first IP address returned by the DNS servers. To eliminate the uncertainty, we recommend that your FQDN always resolve to a single IPv4 address. IPv6 isn't supported.
+* VPN Gateway maintains a DNS cache that's refreshed every 5 minutes. The gateway tries to resolve the FQDNs for disconnected tunnels only. Resetting the gateway also triggers FQDN resolution.
+* Although VPN Gateway supports multiple connections to different local network gateways with different FQDNs, all FQDNs must resolve to different IP addresses.
+
+1. In the portal, go to **Local network gateways** and open the **Create local network gateway** page.
+1. On the **Basics** tab, specify the values for your local network gateway.
+
+   :::image type="content" source="./media/vpn-gateway-add-local-network-gateway-portal-include/basics.png" alt-text="Screenshot that shows creating a local network gateway with IP address." lightbox ="./media/vpn-gateway-add-local-network-gateway-portal-include/basics.png":::
 
    * **Subscription**: Verify that the correct subscription is showing.
    * **Resource group**: Select the resource group that you want to use. You can either create a new resource group or select one that you've already created.
-   * **Region**: Select the region where this object will be created. You might want to select the same location where your virtual network resides, but you aren't required to do so.
+   * **Region**: Select the region for this object. You might want to select the same location where your virtual network resides, but you aren't required to do so.
    * **Name**: Specify a name for your local network gateway object.
    * **Endpoint**: Select the endpoint type for the on-premises VPN device as **IP address** or **FQDN (Fully Qualified Domain Name)**.
       * **IP address**: If you have a static public IP address allocated from your internet service provider (ISP) for your VPN device, select the IP address option. Fill in the IP address as shown in the example. This address is the public IP address of the VPN device that you want Azure VPN Gateway to connect to. If you don't have the IP address right now, you can use the values shown in the example. Later, you must go back and replace your placeholder IP address with the public IP address of your VPN device. Otherwise, Azure can't connect.
       * **FQDN**: If you have a dynamic public IP address that could change after a certain period of time, often determined by your ISP, you can use a constant DNS name with a Dynamic DNS service to point to your current public IP address of your VPN device. Your Azure VPN gateway resolves the FQDN to determine the public IP address to connect to.
    * **Address space**: The address space refers to the address ranges for the network that this local network represents. You can add multiple address space ranges. Make sure that the ranges you specify here don't overlap with ranges of other networks that you want to connect to. Azure routes the address range that you specify to the on-premises VPN device IP address. *Use your own values here if you want to connect to your on-premises site, not the values shown in the example*.
 
-   > [!NOTE]
-   >
-   > * Azure VPN Gateway supports only one IPv4 address for each FQDN. If the domain name resolves to multiple IP addresses, VPN Gateway uses the first IP address returned by the DNS servers. To eliminate the uncertainty, we recommend that your FQDN always resolve to a single IPv4 address. IPv6 isn't supported.
-   > * VPN Gateway maintains a DNS cache that's refreshed every 5 minutes. The gateway tries to resolve the FQDNs for disconnected tunnels only. Resetting the gateway also triggers FQDN resolution.
-   > * Although the Azure VPN Gateway supports multiple connections to different Local Network Gateways with different FQDNs, all FQDNs must resolve to different IP addresses.
-   >  
-
 1. On the **Advanced** tab, you can configure BGP settings, if needed.
 1. After you specify the values, select **Review + create** at the bottom of the page to validate the page.
-1. Select **Create** to create the local network gateway object.
+1. Select **Create** to create the local network gateway object.