| title | Azure ExpressRoute: Prerequisites |
|---|---|
| description | This page provides a list of requirements to be met before you can order an Azure ExpressRoute circuit. It includes a checklist. |
| services | expressroute |
| author | duongau |
| ms.service | azure-expressroute |
| ms.topic | concept-article |
| ms.date | 03/23/2026 |
| ms.author | duau |
To connect to Microsoft cloud services using ExpressRoute, ensure the following requirements are met:
[!INCLUDE expressroute-office365-include]
- A valid and active Microsoft Azure account is required to set up the ExpressRoute circuit. ExpressRoute circuits are resources within Azure subscriptions. An Azure subscription is necessary even if connectivity is limited to non-Azure Microsoft cloud services, such as Microsoft 365.
- The Microsoft.Network resource provider must be registered in your Azure subscription. This requirement is automatically satisfied if a virtual network already exists in the subscription. If not, you must register it before you can create an ExpressRoute circuit or view available peering locations.
- An active Microsoft 365 subscription is needed if using Microsoft 365 services. For more information, see the Microsoft 365 specific requirements section of this article.
- Before using ExpressRoute Direct, you must first enroll your subscription using Azure PowerShell commands.
- Work with an ExpressRoute connectivity partner to connect to the Microsoft cloud. You can set up a connection between your on-premises network and Microsoft in three ways.
- If your provider isn't an ExpressRoute connectivity partner, you can still connect to the Microsoft cloud through a cloud exchange provider.
- Redundancy at each peering location: Microsoft requires redundant BGP sessions between Microsoft's routers and the peering routers on each ExpressRoute circuit, even with just one physical connection to a cloud exchange.
- Redundancy for Disaster Recovery: Microsoft strongly recommends setting up at least two ExpressRoute circuits in different peering locations to avoid a single point of failure.
- Routing: Depending on your connection method to the Microsoft Cloud, you or your provider needs to set up and manage the BGP sessions for routing domains. Some Ethernet connectivity providers or cloud exchange providers might offer BGP management as a value-added service.
- NAT: Microsoft only accepts public IP addresses through Microsoft peering. If using private IP addresses in your on-premises network, you or your provider needs to translate them to public IP addresses using NAT.
- QoS: Skype for Business services (e.g., voice, video, text) requires differentiated QoS treatment. Follow the QoS requirements with your provider.
- Network Security: Consider network security when connecting to the Microsoft Cloud via ExpressRoute.
If you plan to use Microsoft 365 with ExpressRoute, review the following resources for detailed requirements and guidelines:
- Azure ExpressRoute for Microsoft 365
- High availability and failover with ExpressRoute
- Microsoft 365 URLs and IP address ranges
- Network planning and performance tuning for Microsoft 365
- Network and migration planning for Microsoft 365
- Microsoft 365 integration with on-premises environments
- Stay up to date with Office 365 IP Address changes
- For more information about ExpressRoute, see the ExpressRoute FAQ.
- Find an ExpressRoute connectivity provider. See ExpressRoute partners and peering locations.
- Review Azure Well-architected Framework for ExpressRoute to learn about best practices for designing and implementing ExpressRoute.
- Refer to requirements for Routing, NAT, and QoS.
- Configure your ExpressRoute connection: