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
+35-18Lines changed: 35 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,14 +3,15 @@ title: 'Azure ExpressRoute Overview: Connect over a private connection'
3
3
description: The ExpressRoute Technical Overview explains how an ExpressRoute connection works to extend your on-premises network to Azure over a private connection.
4
4
services: expressroute
5
5
author: duongau
6
-
7
6
ms.service: expressroute
8
7
ms.custom: ignite-2022
9
8
ms.topic: overview
10
-
ms.date: 10/05/2020
9
+
ms.date: 12/22/2022
11
10
ms.author: duau
12
11
---
12
+
13
13
# What is Azure ExpressRoute?
14
+
14
15
ExpressRoute lets you extend your on-premises networks into the Microsoft cloud over a private connection with the help of a connectivity provider. With ExpressRoute, you can establish connections to Microsoft cloud services, such as Microsoft Azure and Microsoft 365.
15
16
16
17
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 colocation facility. ExpressRoute connections don't go over the public Internet. This allows ExpressRoute connections to offer more reliability, faster speeds, consistent latencies, and higher security than typical connections over the Internet. For information on how to connect your network to Microsoft using ExpressRoute, see [ExpressRoute connectivity models](expressroute-connectivity-models.md).
@@ -36,12 +37,15 @@ For more information, see the [ExpressRoute FAQ](expressroute-faqs.md).
36
37
## Features
37
38
38
39
### Layer 3 connectivity
40
+
39
41
Microsoft uses BGP, an industry standard dynamic routing protocol, to exchange routes between your on-premises network, your instances in Azure, and Microsoft public addresses. We establish multiple BGP sessions with your network for different traffic profiles. More details can be found in the [ExpressRoute circuit and routing domains](expressroute-circuit-peerings.md) article.
40
42
41
43
### Redundancy
42
-
Each ExpressRoute circuit consists of two connections to two Microsoft Enterprise edge routers (MSEEs) at an [ExpressRoute Location](./expressroute-locations.md#expressroute-locations) from the connectivity provider/your network edge. Microsoft requires dual BGP connection from the connectivity provider/your network edge – one to each MSEE. You may choose not to deploy redundant devices/Ethernet circuits at your end. However, connectivity providers use redundant devices to ensure that your connections are handed off to Microsoft in a redundant manner. A redundant Layer 3 connectivity configuration is a requirement for our [SLA](https://azure.microsoft.com/support/legal/sla/) to be valid.
44
+
45
+
Each ExpressRoute circuit consists of two connections to two Microsoft Enterprise edge routers (MSEEs) at an [ExpressRoute Location](./expressroute-locations.md#expressroute-locations) from the connectivity provider or your network edge. Microsoft requires dual BGP connections from the connectivity provider or your network edge – one to each MSEE. You may choose not to deploy redundant devices/Ethernet circuits at your end. However, connectivity providers use redundant devices to ensure that your connections are handed off to Microsoft in a redundant manner.
43
46
44
47
### Connectivity to Microsoft cloud services
48
+
45
49
ExpressRoute connections enable access to the following services:
46
50
* Microsoft Azure services
47
51
* Microsoft 365 services
@@ -50,43 +54,52 @@ ExpressRoute connections enable access to the following services:
For a detailed list of services supported over ExpressRoute, visit the [ExpressRoute FAQ](expressroute-faqs.md) page.
57
+
For a detailed list of services supported over ExpressRoute, visit the [ExpressRoute FAQ](expressroute-faqs.md#microsoft-peering) page.
54
58
55
59
### Connectivity to all regions within a geopolitical region
56
-
You can connect to Microsoft in one of our [peering locations](expressroute-locations.md) and access regions within the geopolitical region.
57
60
58
-
For example, if you connect to Microsoft in Amsterdam through ExpressRoute. You'll have access to all Microsoft cloud services hosted in Northern and Western Europe. For an overview of the geopolitical regions, the associated Microsoft cloud regions, and corresponding ExpressRoute peering locations, see the [ExpressRoute partners and peering locations](expressroute-locations.md) article.
61
+
You can connect to Microsoft from one of our [peering locations](expressroute-locations.md) and access regions within the same geopolitical region.
62
+
63
+
For example, if you connect to Microsoft in Amsterdam through ExpressRoute. You'll have access to all of Microsoft cloud services hosted in North and West Europe. For an overview of the geopolitical regions, the associated Microsoft cloud regions, and corresponding ExpressRoute peering locations, see the [ExpressRoute partners and peering locations](expressroute-locations.md) article.
59
64
60
65
### Global connectivity with ExpressRoute Premium
61
-
You can enable [ExpressRoute Premium](expressroute-faqs.md) to extend connectivity across geopolitical boundaries. For example, if you connect to Microsoft in Amsterdam through ExpressRoute you'll have access to all Microsoft cloud services hosted in all regions across the world. You can also access services deployed in South America or Australia the same way you access North and West Europe regions. National clouds are excluded.
66
+
67
+
You can enable [ExpressRoute Premium](expressroute-faqs.md#expressroute-premium) to extend connectivity across geopolitical boundaries. If you connect to Microsoft in Amsterdam through ExpressRoute, you'll have access to all of Microsoft cloud services hosted in every region across the globe. For example, you'll have access to services deployed in West US or Australian East the same way you access North and West Europe regions. National clouds are excluded.
62
68
63
69
### Local connectivity with ExpressRoute Local
64
-
You can transfer data cost-effectively by enabling the [Local SKU](expressroute-faqs.md). With Local SKU, you can bring your data to an ExpressRoute location near the Azure region you want. With Local, Data transfer is included in the ExpressRoute port charge.
70
+
71
+
You can transfer data cost-effectively by enabling the [Local SKU](expressroute-faqs.md#expressroute-local). With Local SKU, you can bring your data to an ExpressRoute location near the Azure region you want. With Local, Data transfer is included in the ExpressRoute port charge.
65
72
66
73
For peering location and supported Azure local region, see [providers by locations](expressroute-locations-providers.md#partners).
67
74
68
75
### Across on-premises connectivity with ExpressRoute Global Reach
69
-
You can enable ExpressRoute Global Reach to exchange data across your on-premises sites by connecting your ExpressRoute circuits. For example, if you have a private data center in California connected to an ExpressRoute circuit in Silicon Valley and another private data center in Texas connected to an ExpressRoute circuit in Dallas. With ExpressRoute Global Reach, you can connect your private data centers together through these two ExpressRoute circuits. Your cross-data-center traffic will traverse through Microsoft's network.
76
+
77
+
You can enable ExpressRoute Global Reach to exchange data across your on-premises sites by connecting your ExpressRoute circuits. For example, if you have a private data center in California connected to an ExpressRoute circuit in Silicon Valley and another private data center in Texas connected to an ExpressRoute circuit in Dallas. With ExpressRoute Global Reach, you can connect your private data centers together through these two ExpressRoute circuits. Your cross data-center traffic will traverse through the Microsoft network.
70
78
71
79
For more information, see [ExpressRoute Global Reach](expressroute-global-reach.md).
80
+
72
81
### Rich connectivity partner ecosystem
73
-
ExpressRoute has a constantly growing ecosystem of connectivity providers and systems integrator partners. For the latest information, refer to [ExpressRoute partners and peering locations](expressroute-locations.md).
82
+
83
+
ExpressRoute has a constantly growing ecosystem of connectivity providers and systems integrator partners. For the latest information, see [ExpressRoute partners and peering locations](expressroute-locations.md).
74
84
75
85
### Connectivity to national clouds
76
-
Microsoft operates isolated cloud environments for special geopolitical regions and customer segments. Refer to the [ExpressRoute partners and peering locations](expressroute-locations.md) page for a list of national clouds and providers.
86
+
87
+
Microsoft operates isolated cloud environments for special geopolitical regions and customer segments. For a list of national clouds and providers, see [ExpressRoute partners and peering locations](expressroute-locations.md#national-cloud-environment).
77
88
78
89
### ExpressRoute Direct
90
+
79
91
ExpressRoute Direct provides customers the opportunity to connect directly into Microsoft’s global network at peering locations strategically distributed across the world. ExpressRoute Direct provides dual 100-Gbps connectivity, which supports Active/Active connectivity at scale.
80
92
81
93
Key features that ExpressRoute Direct provides include, but aren't limited to:
82
94
83
-
* Massive data ingestion into services like Azure Storage and Azure Cosmos DB
84
-
* Physical isolation for industries that are regulated and require dedicated and isolated connectivity, such as: Banking, Government, and Retail
85
-
* Granular control of circuit distribution based on business unit
95
+
* Massive data ingestion into services like Azure Storage and Azure Cosmos DB.
96
+
* Physical isolation for industries that are regulated and require dedicated and isolated connectivity. For example: banks, governments, and retails.
97
+
* Granular control of circuit distribution based on business unit.
86
98
87
99
For more information, see [About ExpressRoute Direct](./expressroute-erdirect-about.md).
88
100
89
101
### Bandwidth options
102
+
90
103
You can purchase ExpressRoute circuits for a wide range of bandwidths. The supported bandwidths are listed as followed. Be sure to check with your connectivity provider to determine the bandwidths they support.
91
104
92
105
* 50 Mbps
@@ -99,10 +112,12 @@ You can purchase ExpressRoute circuits for a wide range of bandwidths. The suppo
99
112
* 10 Gbps
100
113
101
114
### Dynamic scaling of bandwidth
102
-
You can increase the ExpressRoute circuit bandwidth (on a best effort basis) without having to tear down your connections. For more information, see [Modifying an ExpressRoute circuit](expressroute-howto-circuit-portal-resource-manager.md#modify).
115
+
116
+
You can increase the ExpressRoute circuit bandwidth without having to tear down your connections. For more information, see [Modifying an ExpressRoute circuit](expressroute-howto-circuit-portal-resource-manager.md#modify).
103
117
104
118
### Flexible billing models
105
-
You can pick a billing model that works best for you. Choose between the billing models listed as followed. For more information, see [ExpressRoute FAQ](expressroute-faqs.md).
119
+
120
+
You can select a billing model that works best for you:
106
121
107
122
***Unlimited data**. Billing is based on a monthly fee; all inbound and outbound data transfer is included free of charge.
108
123
***Metered data**. Billing is based on a monthly fee; all inbound data transfer is free of charge. Outbound data transfer is charged per GB of data transfer. Data transfer rates vary by region.
@@ -112,14 +127,16 @@ You can pick a billing model that works best for you. Choose between the billing
112
127
* Increased number of VNet links per ExpressRoute circuit from 10 to a larger limit, depending on the bandwidth of the circuit.
113
128
114
129
## FAQ
130
+
115
131
For frequently asked questions about ExpressRoute, see [ExpressRoute FAQ](expressroute-faqs.md).
116
132
117
133
## <aname="new"></a>What's new?
118
134
119
135
Subscribe to the RSS feed and view the latest ExpressRoute feature updates on the [Azure Updates](https://azure.microsoft.com/updates/?category=networking&query=ExpressRoute) page.
120
136
121
137
## Next steps
122
-
* Ensure that all prerequisites are met. See [ExpressRoute prerequisites](expressroute-prerequisites.md).
138
+
123
139
*[Learn module: Introduction to Azure ExpressRoute](/training/modules/intro-to-azure-expressroute).
0 commit comments