Configuring a Microsoft Azure ExpressRoute Direct Connection
Megaport offers two types of connection to ExpressRoute: you can order virtual cross-connections to the Microsoft cloud through Megaport or you can connect directly to the Microsoft cloud through point-to-point Ethernet links (ExpressRoute Direct).
Connecting through a VXC is described in Connecting to Microsoft Azure ExpressRoute. This topic describes ExpressRoute Direct.
With ExpressRoute Direct through Megaport, you can take advantage of the functionality of ExpressRoute and connect directly to the global Microsoft backbone. Key features of ExpressRoute Direct through Megaport include:
- Dual 10 Gbps connectivity, which supports Active/Active connectivity at scale
- Data Ingestion into services like Storage and Cosmos DB
- Physical isolation for industries that require dedicated and isolated connectivity
- Granular control of circuit distribution
- Dedicated capacity on the Microsoft network
With ExpressRoute Direct, you provision an ExpressRoute port in the Azure console and work with Megaport to set up a physical cross connect from the ExpressRoute port to a Megaport at the same data center. You extend your deployment by using a private VXC and you can connect the Megaport in the Azure-enabled data center to a second Megaport in a different data center.
Through Megaport, you can connect with ExpressRoute physical port pairs of 10 Gbps and you can have multiple virtual circuits. Circuits can be 1, 2, 5, or 10 Gbps with subscribed bandwidth of 20 Gbps.
For complete technical requirements, port details, and SLAs, see the Microsoft topic About ExpressRoute Direct.
To create an ExpressRoute Direct connection
- Provision a ExpressRoute port in the Azure console and designate Megaport as the vendor.
- Download a LOA from Azure.
- Provision a Megaport in the same data center as the ExpressRoute port.
- Contact your Megaport account manager to set up a physical cross connect from the ExpressRoute port to the Megaport.
- Configure a private VXC to connect the Megaport attached to the ExpressRoute port to a second Megaport in a different data center.
This connection is not set up exclusively through the Megaport portal, but instead requires direct coordination with your Megaport account manager.