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: articles/expressroute/expressroute-introduction.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
---
2
-
title: Introduction to ExpressRoute | Microsoft Docs
3
-
description: This page provides an overview of the ExpressRoute service, including how an ExpressRoute connection works.
2
+
title: 'ExpressRoute Overview: Extend your on-premises network to Azure over a dedicated private connection | Microsoft Docs'
3
+
description: This ExpressRoute Technical Overview explains how an ExpressRoute connection works to extend your on-premises network to Azure over a dedicated private connection.
4
4
documentationcenter: na
5
5
services: expressroute
6
6
author: cherylmc
7
-
manager: carmonm
7
+
manager: timlt
8
8
editor: ''
9
9
10
10
ms.assetid: fd95dcd5-df1d-41d6-85dd-e91d0091af05
@@ -13,14 +13,14 @@ ms.devlang: na
13
13
ms.topic: get-started-article
14
14
ms.tgt_pltfrm: na
15
15
ms.workload: infrastructure-services
16
-
ms.date: 10/10/2016
16
+
ms.date: 01/24/2017
17
17
ms.author: cherylmc
18
18
19
19
---
20
20
# ExpressRoute technical overview
21
21
Microsoft Azure ExpressRoute lets you extend your on-premises networks into the Microsoft cloud over a dedicated private connection facilitated by a connectivity provider. With ExpressRoute, you can establish connections to Microsoft cloud services, such as Microsoft Azure, Office 365, and CRM Online. Connectivity can be from an any-to-any (IP VPN) network, a point-to-point Ethernet network, or a virtual cross-connection through a connectivity provider at a co-location facility. ExpressRoute connections do not go over the public Internet. This allows ExpressRoute connections to offer more reliability, faster speeds, lower latencies, and higher security than typical connections over the Internet.
@@ -48,7 +48,7 @@ You can integrate your WAN with the Microsoft cloud. IPVPN providers (typically
48
48
49
49
Connectivity providers can offer one or more connectivity models. You can work with your connectivity provider to pick the model that works best for you.
Copy file name to clipboardExpand all lines: articles/vpn-gateway/vpn-gateway-about-vpngateways.md
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: About cross-premises Azure VPN connections | Microsoft Docs
3
-
description: Learn about VPN Gateway connections for Azure Virtual Networks.
2
+
title: 'VPN Gateway Overview: Create cross-premises VPN connections to Azure virtual networks | Microsoft Docs'
3
+
description: This VPN Gateway Overview explains the ways to connect to Azure virtual networks using a VPN connection over the Internet. Included are diagrams of basic connection configurations.
4
4
services: vpn-gateway
5
5
documentationcenter: na
6
6
author: cherylmc
@@ -14,7 +14,7 @@ ms.devlang: na
14
14
ms.topic: get-started-article
15
15
ms.tgt_pltfrm: na
16
16
ms.workload: infrastructure-services
17
-
ms.date: 01/23/2017
17
+
ms.date: 01/24/2017
18
18
ms.author: cherylmc
19
19
20
20
---
@@ -53,12 +53,12 @@ Use the diagrams and descriptions to help select the connection topology to matc
53
53
### Site-to-Site
54
54
A Site-to-Site (S2S) VPN gateway connection is a connection over IPsec/IKE (IKEv1 or IKEv2) VPN tunnel. This type of connection requires a VPN device located on-premises that has a public IP address assigned to it and is not located behind a NAT. S2S connections can be used for cross-premises and hybrid configurations.
You can create and configure a VPN gateway connection between your VNet and multiple on-premises networks. When working with multiple connections, you must use a RouteBased VPN type (dynamic gateway for classic VNets). Because a VNet can only have one VPN gateway, all connections through the gateway share the available bandwidth. This is often called a "multi-site" connection.

75
+

76
76
77
77
#### Connections between deployment models
78
78
Azure currently has two deployment models: classic and Resource Manager. If you have been using Azure for some time, you probably have Azure VMs and instance roles running in a classic VNet. Your newer VMs and role instances may be running in a VNet created in Resource Manager. You can create a connection between the VNets to allow the resources in one VNet to communicate directly with resources in another.
@@ -86,7 +86,7 @@ You may be able to use VNet peering to create your connection, as long as your v
86
86
## Point-to-Site
87
87
A Point-to-Site (P2S) VPN gateway connection allows you to create a secure connection to your virtual network from an individual client computer. P2S is a VPN connection over SSTP (Secure Socket Tunneling Protocol). P2S connections do not require a VPN device or a public-facing IP address to work. You establish the VPN connection by starting it from the client computer. This solution is useful when you want to connect to your VNet from a remote location, such as from home or a conference, or when you only have a few clients that need to connect to a VNet. P2S connections can be used in conjunction with S2S connections through the same VPN gateway, provided that all of the configuration requirements for both connections are compatible.
@@ -101,7 +101,7 @@ ExpressRoute is a direct, dedicated connection from your WAN (not over the publi
101
101
102
102
You can configure a Site-to-Site VPN as a secure failover path for ExpressRoute, or use Site-to-Site VPNs to connect to sites that are not part of your network, but that are connected through ExpressRoute. Notice that this requires two virtual network gateways for the same virtual network, one using -GatewayType Vpn, and the other using -GatewayType ExpressRoute.
0 commit comments