You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/azure/intro-to-azure-vpn-gateway/includes/1-introduction.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ You're responsible for networking at Adatum, a home maintenance, security, and a
4
4
5
5
Adatum has a large number of remote workers who use laptop computers to interact with these applications. Because the VMs that host the applications are connected to the Adatum on-premises internal network, these remote workers use a third-party VPN to connect to that internal network to access these applications. Users at Adatum's main office make direct connections to the applications. The applications don't require significant amounts of bandwidth to operate successfully and are resilient to fluctuations in latency.
6
6
7
-
You want to ensure that remote workers are able to securely connect to these applications when the migration to Azure is complete. You also want to ensure that workers connected to Adatum's internal network are able to connect to the applications without concern about their network traffic being intercepted. In future, Adatum is also likely to deploy more subnets on its virtual networks, and to also deploy more IaaS workloads on virtual networks around the world. The possibility of an expansion of virtual networks and subnets should be incorporated into any solution that you decide upon.
7
+
You want to ensure that remote workers are able to securely connect to these applications when the migration to Azure is complete. You also want to ensure that workers connected to Adatum's internal network are able to connect to the applications without concern about their network traffic being intercepted. In the future, Adatum is also likely to deploy more subnets on its virtual networks, and to also deploy more IaaS workloads on virtual networks around the world. The possibility of an expansion of virtual networks and subnets should be incorporated into any solution that you decide upon.
8
8
9
9
This module explains what Azure VPN Gateway does, how it works, and when you should choose to use Azure VPN Gateway as a solution to meet your organization's needs.
Copy file name to clipboardExpand all lines: learn-pr/azure/intro-to-azure-vpn-gateway/includes/2-what-is-azure-vpn-gateway.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
An Azure VPN gateway is a specific type of virtual network gateway that is used to send and receive encrypted traffic between an Azure virtual network and an on-premises location over the public Internet. Azure VPN gateways can also be used to connect separate Azure virtual networks using an encrypted tunnel across the Microsoft network backbone.
2
2
3
-
:::image type="content" source="../images/vpn-gateway-network-structure.png" alt-text="Diagram that shows how Azure V P N Gateway works with the on-premises network.":::
3
+
:::image type="content" source="../images/vpn-gateway-network-structure.png" alt-text="Diagram that shows how Azure VPN Gateway works with the on-premises network.":::
4
4
5
5
Azure VPN Gateway supports both point-to-site and site-to-site connections:
6
6
7
7
-**Point-to-site VPN connection**: A point-to-site VPN connection can be used to connect a single computer to an Azure virtual network. A P2S connection is established by starting it from the client computer. This type of VPN connection is commonly used by remote workers with portable computers.
8
8
-**Site-to-site VPN connection**: A site-to-site VPN connection allows you to connect one network to another network with traffic between the two networks passing across an encrypted VPN tunnel. This type of VPN connection is commonly used to connect on-premises sites to Azure or Azure virtual networks to each other.
9
9
10
-
:::image type="content" source="../images/vpn-connection-types.png" alt-text="Diagram that depicts the types of connections Azure V P N Gateway supports.":::
10
+
:::image type="content" source="../images/vpn-connection-types.png" alt-text="Diagram that depicts the types of connections Azure VPN Gateway supports.":::
11
11
12
12
Depending on the SKU chosen, Azure VPN gateways support:
Copy file name to clipboardExpand all lines: learn-pr/azure/intro-to-azure-vpn-gateway/includes/3-how-vpn-gateway-works.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ You can deploy only one VPN gateway in each Azure virtual network. Even though y
5
5
6
6
## VPN gateway types
7
7
8
-
When you configure a virtual network gateway, you select a setting that specifies the gateway type. The gateway type determines how the virtual network gateway will be used and the actions that the gateway will take. The gateway type `Vpn` specifies that the type of virtual network gateway created is a `VPN gateway`. This distinguishes it from an ExpressRoute gateway, which uses a different gateway type. An Azure virtual network can have two virtual network gateways: one VPN gateway and one ExpressRoute gateway.
8
+
When you configure a virtual network gateway, you select a setting that specifies the gateway type. The gateway type determines how the virtual network gateway will be used and the actions that the gateway will take. The gateway type `Vpn` specifies that the type of virtual network gateway created is a `VPN gateway`. This distinguishes it from an ExpressRoute gateway, which uses a different gateway type. An Azure virtual network can have two virtual network gateways, one VPN gateway and one ExpressRoute gateway.
9
9
10
10
There are two types of Azure VPN gateways:
11
11
@@ -18,8 +18,8 @@ Policy-based VPN gateways require that you specify a fixed set of IP addresses o
18
18
19
19
Key features of policy-based VPN gateways in Azure include:
20
20
21
-
- Support for IKEv1 only
22
-
- Use of static routing
21
+
- Support for IKEv1 only.
22
+
- Use of static routing.
23
23
24
24
The source and destination of the tunneled networks are declared in the VPN policy and don't need to be declared in routing tables. Use policy-based VPNs only in specific scenarios that require them, such as for compatibility with legacy on-premises VPN devices.
25
25
@@ -36,11 +36,11 @@ Use a route-based VPN gateway if you need any of the following types of connecti
36
36
37
37
Key features of route-based VPN gateways in Azure include:
38
38
39
-
- Supports IKEv2
40
-
- Uses any-to-any (wildcard) traffic selectors
41
-
- Can use dynamic routing protocols, where routing/forwarding tables direct traffic to different IPsec tunnels
39
+
- Supports IKEv2.
40
+
- Uses any-to-any (wildcard) traffic selectors.
41
+
- Can use dynamic routing protocols, where routing/forwarding tables direct traffic to different IPsec tunnels.
42
42
43
-
When configured to use dynamic routing, the source and destination networks are not statically defined because they are in policy-based VPNs, or even in route-based VPNs with static routing. Instead, data packets are encrypted based on network routing tables that are created dynamically using routing protocols such as Border Gateway Protocol (BGP).
43
+
When configured to use dynamic routing, the source and destination networks are not statically defined because they are in policy-based VPNs or even in route-based VPNs with static routing. Instead, data packets are encrypted based on network routing tables that are created dynamically using routing protocols such as Border Gateway Protocol (BGP).
44
44
45
45
Azure VPN gateways only support the use pre-shared key method of authentication. Both route-based and policy-based types also rely on Internet Key Exchange (IKE) in either version 1 or version 2 and Internet Protocol Security (IPsec). IKE is used to set up a security association (an agreement of the encryption) between two endpoints. This association is then passed to the IPsec suite, which encrypts and decrypts data packets encapsulated in the VPN tunnel.
46
46
@@ -64,7 +64,7 @@ The following Azure resources need to be present before you can deploy an operat
64
64
-**Virtual network**: An Azure virtual network with enough address space for the additional subnet that you'll need for the VPN gateway. The address space for this virtual network must not overlap with the on-premises network to which you'll be connecting.
65
65
-**GatewaySubnet**: A subnet called GatewaySubnet for the VPN gateway. Requires at least a /27 address mask. This subnet cannot be used for any other services.
66
66
-**Public IP address**: A Basic-SKU dynamic public IP address if using a non-zone-aware gateway. This address provides a public-routable IP address as the target for your on-premises VPN device. This IP address is dynamic, but it won't change unless you delete and re-create the VPN gateway.
67
-
-**Local network gateway**: Create a local network gateway to define the on-premises network's configuration: where the VPN gateway will connect and to what it will connect. This configuration includes the on-premises VPN device's public IPv4 address and the on-premises routable networks. This information is used by the VPN gateway to route packets that are destined for on-premises networks through the IPsec tunnel.
67
+
-**Local network gateway**: Create a local network gateway to define the on-premises network's configuration, where the VPN gateway will connect and to what it will connect. This configuration includes the on-premises VPN device's public IPv4 address and the on-premises routable networks. This information is used by the VPN gateway to route packets that are destined for on-premises networks through the IPsec tunnel.
68
68
69
69
When these prerequisite components are present, you can create the virtual network gateway to route traffic between the virtual network and the on-premises datacenter or other virtual networks. After the virtual network gateway is deployed, you can then create a connection resource to create a logical connection between the VPN gateway and the local network gateway:
0 commit comments