หมายเหตุ
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลอง ลงชื่อเข้าใช้หรือเปลี่ยนไดเรกทอรีได้
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลองเปลี่ยนไดเรกทอรีได้
ExpressRoute facilitates the creation of private connections between your on-premises networks and Azure workloads in a designated peering locations. These locations are colocation facilities housing Microsoft Enterprise Edge (MSEE) devices, serving as the gateway to Microsoft's network.
Within the peering location, two types of connections can be established:
ExpressRoute circuit - an ExpressRoute circuit consist of two logical connections between your on-premises network and Azure. These connections are made through a pair of physical links provided by an ExpressRoute partner, such as AT&T, Verizon, Megaport, Equinix, among others.
ExpressRoute Direct - ExpressRoute Direct is a dedicated and private connection between your on-premises network and Azure, eliminating the need for partner provider involvement. It enables the direct connection of your routers to the Microsoft global network using dual 10G or 100G Ports.
The standard ExpressRoute configuration is set up with a pair of links to enhance the reliability of your ExpressRoute connection. This setup is designed to provide redundancy and improves the availability of your ExpressRoute connections during hardware failures, maintenance events, or other unforeseen incidents within the peering locations. However, you should note that these redundant connections don't provide resilience against certain events. These events could disrupt or isolate the edge location where the MSEE devices are located. Such disruptions could potentially lead to a complete loss of connectivity from your on-premises networks to your cloud services.
ExpressRoute Metro
ExpressRoute Metro is a high-resiliency configuration designed to provide multi-site redundancy. This configuration allows you to benefit from a dual-homed setup that facilitates diverse connections to two distinct ExpressRoute peering locations within a city. The high resiliency configuration benefits from the redundancy across the two peering locations to offer higher availability and resilience for your connectivity from your on-premises to resources in Azure.
Key features of ExpressRoute Metro include:
- Dual-homed connections to two distinct ExpressRoute peering locations within the same city.
- Increased availability and resiliency for your ExpressRoute Circuits at the same cost as a standard Circuit.
- Seamless connectivity from your on-premises environment to Azure resources through an ExpressRoute Circuit with the assistance of a connectivity provider or with ExpressRoute Direct (Dual 10G or 100G ports)
The following diagram allows for a comparison between the standard ExpressRoute circuit and a ExpressRoute Metro circuit.
ExpressRoute Metro locations
| Metro location | Location address | Zone | Local Azure Region | ER Direct | Service Provider |
|---|---|---|---|---|---|
| Amsterdam Metro | Equinix AM5 Digital Realty AMS8 |
1 | West Europe | ✓ | Colt DE-CIX Digital Realty Equinix euNetworks Eurofiber GTT Megaport NL-IX SURF |
| Atlanta Metro | Equinix AT1 Digital Realty ATL14 |
1 | ✗ | ✓ | Centurylink Cloud Connect1 Equinix Megaport |
| Auckland Metro | Vocus VDCAKL01 Spark MDR |
2 | New Zealand North | ✓ | |
| Brussels Metro | Digital Realty BR4 LCL Brussels North |
1 | Belgium Central | ✓ | Belnet Colt Eurofiber Megaport |
| Chicago Metro | Equinix CH1 CoreSite CH1 |
1 | North Central US | ✓ | CenturyLink Cloud Connect Cox Communication1 Crown Castle Digital Realty Equinix Megaport Zayo Dynamiclink |
| Copenhagen Metro | Digital Realty CPH1 Global Connect Copenhagen |
1 | Denmark East | ✓ | GlobalConnect1 Megaport |
| Dallas Metro | Equinix DA6 Digital Realty DFW10 |
1 | ✗ | ✓ | Centurylink Cloud Connect1 Equinix Megaport Zayo Dynamiclink |
| Dammam Metro | Center3 DDC352 MIS AL ANWAR |
3 | ✗ | ✓ | |
| Doha Metro | Meeza MV2 Ooredoo QDC5 |
3 | Qatar central | ✓ | |
| Dublin Metro | Equinix DB3 Digital Realty DUB02 |
1 | North Europe | ✓ | Colt Equinix Megaport |
| Hong Kong Metro | Equinix HK1 iAdvantage MEGA-i |
2 | East Asia | ✓ | Megaport1 |
| Frankfurt Metro | Digital Realty FRA11 Equinix FR7 |
1 | Germany West Central | ✓ | Colt1 DE-CIX Equinix Megaport Proximus NXT Luxembourg |
| Jakarta Metro | NeutraDC HDC NTT GDC |
2 | Indonesia Central | ✓ | DCI Indonesia Telin1 XL Axiata1 |
| Johannesburg Metro | Teraco JT1 Africa DAta Centres JHB1ADC |
3 | South Africa North | ✓ | Liquid Telecom OpenAccessDC1 |
| Kuala Lumpur Metro | TT Dotcom menara Telekom TM One KVDC |
2 | Malaysia West | ✓ | |
| Madrid Metro | Equinix MD2 Digital Realty MAD1 |
1 | Spain Central | ✓ | 1-IX.EU1 Colt DE-CIX Equinix Megaport Telefonica1 |
| Melbourne Metro | NextDC MEL01 Equinix ME1/2 |
2 | Australia Southeast | ✓ | Internet Association of Australia1 Megaport Next DC |
| Milan Metro | Irideos Milan Data4Italy Milan |
1 | Italy North | ✓ | Colt De-cix Equinix Megaport Retelit1 Telecom Italia Sparkle Telia Carrier (Arelion)1 |
| Mumbai Metro | STT LVSB Nxtra Data |
2 | West India | ✓ | |
| New York Metro | Equinix NY5 165 Halsey Street |
1 | ✗ | ✓ | Centurylink Cloud Connect1 DE-CIX Equinix Megaport |
| Paris Metro | Digital Realty PAR5 Equinix PA4 |
1 | France Central | ✓ | Colt Digital Realty Equinix1 Megaport |
| Phoenix Metro | EdgeConnex POR01 PhoenixNAP |
1 | West US 3 | ✓ | Centurylink Cloud Connect1 Megaport |
| Oslo Metro | DigiPlex Ulven Bulk Data IX |
2 | Norway East | ✓ | Colt1 GlobalConnect Telenor Secure Cloud Connect1 |
| Silicon Valley Metro | Equinix SV10 CoreSite SV7 |
1 | West US | ✓ | Centurylink Cloud Connect1 Equinix1 Megaport Zayo Dynamiclink |
| Singapore Metro | Global Switch Tai Seng Equinix SG1 |
2 | Southeast Asia | ✓ | Colt DE-CIX Equinix IX Reach MegaPOP (Singtel) Megaport Singtel International |
| Stockholm Metro | Equinix SK1 Digital Realty STO6 |
1 | Sweden Central | ✓ | De-cix1 GlobalConnect1 Megaport1 Telia Carrier (Arelion) |
| Sydney Metro | Equinix SY2 NextDC S1 |
2 | Australia East | ✓ | Megaport Next DC |
| Taipei Metro | Chief Telecom Chunghwa Telecom Co. Ltd |
2 | Taiwan North | ✓ | Chunghwa Telecom1 |
| Tokyo Metro | Equinix TY4 AtTokyo CC1 |
2 | Japan East | ✓ | Equinix1 IIJ Smart Hub1 IIJ1 Megaport1 NTT Communication Flexible Interconnect1 NTT Communication Flexible Interocnnect premium1 TATA Communications1 |
| Toronto Metro | Cologix TOR1 Allied King West |
1 | Canda Central | ✓ | Megaport Sprint Zayo1 |
| Vienna Metro | Digital Realty VIE1 NTT GDC |
1 | Austria East | ✓ | A1 Telekom Austria Colt Next Layer GMBH Telia Carrier (Arelion) |
| Zurich Metro | Digital Realty ZUR2 Equinix ZH5 |
1 | Switzerland North | ✓ | BICS Colt Digital Realty Megaport Orange1 Swisscom |
| Washington DC Metro | Equinix DC6 CoreSite VA3 |
1 | East US East US 2 |
✓ | Centurylink Cloud Connect1 Equinix Megaport Sprint Zayo Dynamiclink |
1 These service providers will be available in the future. While they are listed under the peering location, circuit creation is expected to fail until the providers become active.
Note
The naming convention for Metro sites will utilize City and City2 to denote the two unique peering locations within the same metropolitan region. As an illustration, Amsterdam and Amsterdam2 are indicative of the two separate peering locations within the metropolitan area of Amsterdam. In the Azure portal, these locations will be referred to as Amsterdam Metro.
Configure ExpressRoute Metro
Create an ExpressRoute Metro circuit
You can create an ExpressRoute Metro circuit in the Azure portal in any of the metropolitan areas. Within the portal, specify one of the Metro peering locations and the corresponding service provider supported in that location. For more information, see Create an ExpressRoute circuit.
Create a Metro ExpressRoute Direct
A Metro ExpressRoute Direct port can be created in the Azure portal. Within the portal, specify one of the Metro peering locations. For more information, see Create an ExpressRoute Direct.
One you provisioned the Metro ExpressRoute Direct ports, you can download the LOA (Letter of Authorization), obtain the Meet-Me-Room details, and extend your physical cross-connects.
Migrate from an existing Expressroute circuit to a Metro circuit
If you want to migrate from an existing ExpressRoute circuit, create a new ExpressRoute Metro circuit. Then, follow the steps for circuit migration to transition from the existing standard ExpressRoute circuit to the ExpressRoute Metro circuit.
Next steps
- Review ExpressRoute partners and peering locations to understand the available ExpressRoute partners and peering locations.
- Review ExpressRoute pricing to understand the costs associated with ExpressRoute.
- Review Design architecture for ExpressRoute resiliency to understand the design considerations for ExpressRoute.