Skip to content

Commit 4e81b9f

Browse files
authored
Merge pull request #187243 from cherylmc/s2s-fresh
format
2 parents bbea294 + 9672450 commit 4e81b9f

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

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

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: cherylmc
66
ms.author: cherylmc
77
ms.service: vpn-gateway
88
ms.topic: tutorial
9-
ms.date: 07/21/2021
9+
ms.date: 02/02/2022
1010

1111
---
1212

@@ -31,7 +31,7 @@ In this tutorial, you learn how to:
3131
* An Azure account with an active subscription. If you don't have one, [create one for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
3232
* Make sure you have a compatible VPN device and someone who is able to configure it. For more information about compatible VPN devices and device configuration, see [About VPN Devices](vpn-gateway-about-vpn-devices.md).
3333
* Verify that you have an externally facing public IPv4 address for your VPN device.
34-
* If you are unfamiliar with the IP address ranges located in your on-premises network configuration, you need to coordinate with someone who can provide those details for you. When you create this configuration, you must specify the IP address range prefixes that Azure will route to your on-premises location. None of the subnets of your on-premises network can over lap with the virtual network subnets that you want to connect to.
34+
* If you're unfamiliar with the IP address ranges located in your on-premises network configuration, you need to coordinate with someone who can provide those details for you. When you create this configuration, you must specify the IP address range prefixes that Azure will route to your on-premises location. None of the subnets of your on-premises network can over lap with the virtual network subnets that you want to connect to.
3535

3636
## <a name="CreatVNet"></a>Create a virtual network
3737

@@ -86,11 +86,11 @@ You can view the gateway public IP address on the **Overview** page for your gat
8686

8787
:::image type="content" source="./media/tutorial-create-gateway-portal/address.png" alt-text="Overview page":::
8888

89-
To see additional information about the public IP address object, click the name/IP address link next to **Public IP address**.
89+
To see additional information about the public IP address object, select the name/IP address link next to **Public IP address**.
9090

9191
## <a name="LocalNetworkGateway"></a>Create a local network gateway
9292

93-
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 will 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.
93+
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.
9494

9595
Create a local network gateway using the following values:
9696

@@ -133,28 +133,28 @@ Create a connection using the following values:
133133

134134
### <a name="addconnect"></a>Add additional connections to the gateway
135135

136-
You can add additional connections, provided that none of the address spaces overlap between connections.
136+
You can add additional connections if none of the address spaces overlap between connections.
137137

138138
1. To add an additional connection, navigate to the VPN gateway, then select **Connections** to open the Connections page.
139139
1. Select **+Add** to add your connection. Adjust the connection type to reflect either VNet-to-VNet (if connecting to another VNet gateway), or Site-to-site.
140-
1. If you are connecting using Site-to-site and you have not already created a local network gateway for the site you want to connect to, you can create a new one.
140+
1. If you're connecting using Site-to-site and you haven't already created a local network gateway for the site you want to connect to, you can create a new one.
141141
1. Specify the shared key that you want to use, then select **OK** to create the connection.
142142

143143
### <a name="resize"></a>Resize a gateway SKU
144144

145-
There are specific rules regarding resizing vs. changing a gateway SKU. In this section, we will resize the SKU. For more information, see [Gateway settings - resizing and changing SKUs](vpn-gateway-about-vpn-gateway-settings.md#resizechange).
145+
There are specific rules regarding resizing vs. changing a gateway SKU. In this section, we'll resize the SKU. For more information, see [Gateway settings - resizing and changing SKUs](vpn-gateway-about-vpn-gateway-settings.md#resizechange).
146146

147147
[!INCLUDE [resize a gateway](../../includes/vpn-gateway-resize-gw-portal-include.md)]
148148

149149
### <a name="reset"></a>Reset a gateway
150150

151-
Resetting an Azure VPN gateway is helpful if you lose cross-premises VPN connectivity on one or more Site-to-Site VPN tunnels. In this situation, your on-premises VPN devices are all working correctly, but are not able to establish IPsec tunnels with the Azure VPN gateways.
151+
Resetting an Azure VPN gateway is helpful if you lose cross-premises VPN connectivity on one or more Site-to-Site VPN tunnels. In this situation, your on-premises VPN devices are all working correctly, but aren't able to establish IPsec tunnels with the Azure VPN gateways.
152152

153153
[!INCLUDE [reset a gateway](../../includes/vpn-gateway-reset-gw-portal-include.md)]
154154

155155
### <a name="additional"></a>Additional configuration considerations
156156

157-
S2S configurations can be customized in a variety of ways. For more information, see the following articles:
157+
S2S configurations can be customized in a variety ways. For more information, see the following articles:
158158

159159
* For information about BGP, see the [BGP Overview](vpn-gateway-bgp-overview.md) and [How to configure BGP](vpn-gateway-bgp-resource-manager-ps.md).
160160
* For information about forced tunneling, see [About forced tunneling](vpn-gateway-forced-tunneling-rm.md).
@@ -175,7 +175,7 @@ these resources using the following steps:
175175

176176
## Next steps
177177

178-
Once you have configured a S2S connection, you can add a P2S connection to the same gateway.
178+
Once you've configured a S2S connection, you can add a P2S connection to the same gateway.
179179

180180
> [!div class="nextstepaction"]
181181
> [Point-to-Site VPN connections](vpn-gateway-howto-point-to-site-resource-manager-portal.md)

0 commit comments

Comments
 (0)