Skip to content

Commit 0d2b674

Browse files
Merge pull request #242957 from cherylmc/s2s-device
update
2 parents e4344b7 + e12c7f7 commit 0d2b674

File tree

9 files changed

+14
-17
lines changed

9 files changed

+14
-17
lines changed

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

Lines changed: 1 addition & 1 deletion
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: 04/10/2023
9+
ms.date: 06/23/2023
1010

1111
---
1212

96.4 KB
Loading
-38.2 KB
Loading
147 KB
Loading

includes/vpn-gateway-add-gw-pip-portal-include.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
author: cherylmc
33
ms.service: vpn-gateway
44
ms.topic: include
5-
ms.date: 02/17/2023
5+
ms.date: 06/23/2023
66
ms.author: cherylmc
77

88
# The numbers in this include are correct. They add on to sections in multiple articles that are already numbered.

includes/vpn-gateway-add-gw-portal-include.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
author: cherylmc
33
ms.service: vpn-gateway
44
ms.topic: include
5-
ms.date: 02/17/2023
5+
ms.date: 06/23/2023
66
ms.author: cherylmc
77
---
88

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
author: cherylmc
66
ms.service: vpn-gateway
77
ms.topic: include
8-
ms.date: 09/14/2022
8+
ms.date: 06/23/2023
99
ms.author: cherylmc
1010
ms.custom: include file
1111
---
@@ -20,8 +20,8 @@
2020
* **Name:** Specify a name for your local network gateway object.
2121
* **Endpoint:** Select the endpoint type for the on-premises VPN device - **IP address** or **FQDN (Fully Qualified Domain Name)**.
2222
* **IP address**: If you have a static public IP address allocated from your Internet service provider for your VPN device, select the IP address option and fill in the IP address as shown in the example. This 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, but you'll need to go back and replace your placeholder IP address with the public IP address of your VPN device. Otherwise, Azure won't be able to connect.
23-
* **FQDN**: If you have a dynamic public IP address that could change after certain period of time, often determined by your Internet service provider, 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 will resolve the FQDN to determine the public IP address to connect to.
24-
* **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 will route 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*.
23+
* **FQDN**: If you have a dynamic public IP address that could change after certain period of time, often determined by your Internet service provider, 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.
24+
* **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*.
2525

2626
> [!NOTE]
2727
>

includes/vpn-gateway-basic-vnet-rm-portal-include.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ author: cherylmc
33
ms.author: cherylmc
44
ms.service: vpn-gateway
55
ms.topic: include
6-
ms.date: 06/06/2023
6+
ms.date: 06/23/2023
77
---
88

99
1. Sign in to the [Azure portal](https://portal.azure.com).
@@ -20,17 +20,15 @@ ms.date: 06/06/2023
2020
- **Name**: Enter the name for your virtual network.
2121
- **Region**: Select the location for your VNet. The location determines where the resources that you deploy to this VNet will live.
2222

23-
1. Select **Security** to advance to the Security tab. For this exercise, leave the default values.
23+
1. Select **Security** to advance to the Security tab. For this exercise, leave the default values for all the services on this page.
2424

25-
- **Azure Bastion**: Disable
26-
- **Azure Firewall**: Disable
27-
- **Azure DDoS Network Protection**: Disable
2825
1. Select **IP Addresses** to advance to the IP Addresses tab. On the **IP Addresses** tab, configure the settings.
2926

30-
- **IPv4 address space**: By default, an address space is automatically created. You can select the address space and adjust it to reflect your own values. You can also add more address spaces by selecting the box below the existing address space and specifying the values for the additional address space. For example, you can change the IPv4 address field to **10.1.0.0/16** from the default values that are automatically populated.
31-
- **+ Add 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, then select **Add** at the bottom of the page to add the values.
27+
- **IPv4 address space**: By default, an address space is automatically created. You can select the address space and adjust it to reflect your own values. You can also add a different address space and remove the default that was automatically created. For example, you can specify the starting address as **10.1.0.0** and specify the address space size as **/16**, then **Add** that address space.
28+
- **+ Add subnet**: If you use the default address space, a default subnet is created automatically. If you change the address space, add a new subnet within that address space. Select **+ Add subnet** to open the **Add subnet** window. Configure the following settings, then select **Add** at the bottom of the page to add the values.
3229
- **Subnet name**: Example: **FrontEnd**.
33-
- **Subnet address range**: The address range for this subnet. For example, **10.1.0.0/24**.
30+
- **Subnet address range**: The address range for this subnet. For example, **10.1.0.0** and **/24**.
3431

32+
1. Review the **IP addresses** page and remove any address spaces or subnets that you don't need.
3533
1. Select **Review + create** to validate the virtual network settings.
3634
1. After the settings have been validated, select **Create** to create the virtual network.

includes/vpn-gateway-cross-premises.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,9 @@
55
author: cherylmc
66
ms.service: vpn-gateway
77
ms.topic: include
8-
ms.date: 04/29/2022
8+
ms.date: 06/23/2023
99
ms.author: cherylmc
1010
ms.custom: include file
1111
---
1212
> [!NOTE]
13-
>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.
14-
>
13+
> 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.

0 commit comments

Comments
 (0)