In this article:
- Overview
- Audience
- Prerequisites
- What is Azure ExpressRoute
- Azure ExpressRoute Peering
- Lumen Cloud Connect Connectivity Options
- Procedure to Configure Lumen Cloud Connect
- Azure ExpressRoute resources
- Support
Overview
The purpose of this document is to provide an overview of Lumen Cloud Connect and Azure ExpressRoute with references for further details.
Audience
Users plan to order Lumen Cloud Connect to connect to their Azure environment.
Prerequisites
None
What is ExpressRoute and ExpressRoute Direct
Microsoft Azure ExpressRoute lets you create private connections between Microsoft datacenters and the infrastructure that’s in a co-location environment. ExpressRoute connections offer higher security, more reliability, faster speeds and predictable latencies than typical connections over the Internet. In some cases, using ExpressRoute connections to transfer data between your on-premises network and Azure can also yield significant cost benefits.
Azure offers circuit bandwidths from 50 Mbps to 10 Gbps (50Mbps, 100Mbps, 200 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, 5Gbps, and 10 Gbps).
Azure compute services, namely virtual machines (IaaS) and virtual networks (VNets) deployed within a virtual network can be connected through the Azure Private Peering domain.
PaaS Services such as Azure Storage, SQL databases and Web Apps are offered on public IP addresses. You can privately connect to services hosted on public IP addresses, including VIPs of your cloud services, through the Microsoft Peering routing domain. You can connect the Microsoft Peering domain to your extranet and connect to all Azure services on their public IP addresses from your WAN without having to connect through the Internet.
Similar to ExpressRoute, ExpressRoute Direct provides the ability to connect directly to Azure at peering locations. ExpressRoute Direct provides dual 10Gbps or 100 Gbps, which supports Active/Active connectivity at scale. ExpressRoute Direct can be divided into a combination of circuits based on available SKUs.
Azure ExpressRoute Peering
Peering Comparison
Private Peering | Microsoft Peering | |
---|---|---|
Max. # prefixes supported per peering | 4000 by default, 10000 with ExpressRoute Premium | 200 |
IP address ranges supported | Any valid IP address within your WAN | Public IP addresses owned by you or your connectivity provider |
AS Number requirements | Private and public AS numbers. You must own the public AS number if you choose to use one | Private and public AS numbers. However, you must prove ownership of public IP addresses |
IP protocols supported | IPv4, IPv6 (preview) | IPv4, IPv6 |
Routing Interface IP addresses | RFC1918 and public IP addresses | Public IP addresses registered to you in routing registries |
MD5 Hash support | Yes | Yes |
Microsoft Peering now supports Azure Public (PaaS) services
-
Microsoft has announced they are combining both their PaaS/SaaS services over a single pair of BGP Peers (Microsoft Peering)
-
Before April 1, 2018, ExpressRoute had three peering connections:
- Azure Private (IaaS) peering for connecting to Azure Vnets
- Azure Public (PaaS) peering to reach Azure PaaS services
- Microsoft Peering (SaaS) for Office 365 and Dynamics 365
-
To simplify ExpressRoute management and configuration Microsoft has merged Azure Public routes into the Microsoft Peering connection
- Customers can now access Azure PaaS and Microsoft SaaS services via the Microsoft peering connection
- Customers no longer have to have 3 separate peering types to MSFT (Public / Private / MSFT Peering), but rather 2 peering types going forward (Private / MSFT Peering)
- Refer to this Microsoft document to move Public peering to Microsoft peering.
- Customers can now access Azure PaaS and Microsoft SaaS services via the Microsoft peering connection
-
Note: While customers can receive all PaaS/SaaS services over MSFT Peering, the Office365 service still requires customers to apply for approval directly with Microsoft to enable the Office365 service via ExpressRoute. All other services can be accessed via the MSFT Peering VLAN without a prior approval.
-
Please reference to Azure ExpressRoute for Office 365 and Network connectivity to Office 365 for additional guidance and direction from Microsoft.
Lumen Cloud Connect for Microsoft ExpressRoute
There are different connectivity options to connect to Microsoft Azure, the current options are listed below:
Cloud Provider | Microsoft® Azure |
---|---|
Connection Type | ExpressRoute |
Wavelength (Layer 1) | :heavy_check_mark: ExpressRoute Direct |
Ethernet (Layer 2) | :heavy_check_mark: |
IP VPN (Layer 3) | :heavy_check_mark: |
Dynamic Connections | :heavy_check_mark: |
For On-Ramps locations, please refer to the maps.
To learn more on how Lumen Cloud Connect can connect your company to Microsoft Azure, please visit the Product page or consult with your account team.
Azure ExpressRoute resources
Support
- For issues related to Lumen Cloud Connect Services, please open a Lumen Support ticket by visiting customer support or through the Lumen Support website.