| title | description | documentationcenter | services | author | manager | editor | ms.assetid | ms.service | ms.devlang | ms.topic | ms.tgt_pltfrm | ms.workload | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Prerequisites for Azure ExpressRoute adoption | Microsoft Docs |
This page provides a list of requirements to be met before you can order an Azure ExpressRoute circuit. |
na |
expressroute |
cherylmc |
timlt |
f872d25e-acfd-405d-9d1b-dcb9f323a2ff |
expressroute |
na |
get-started-article |
na |
infrastructure-services |
06/30/2017 |
cherylmc |
To connect to Microsoft cloud services using ExpressRoute, you need to verify that the following requirements listed in the following sections have been met.
[!INCLUDE expressroute-office365-include]
- A valid and active Microsoft Azure account. This account is required to set up the ExpressRoute circuit. ExpressRoute circuits are resources within Azure subscriptions. An Azure subscription is a requirement even if connectivity is limited to non-Azure Microsoft cloud services, such as Office 365 services and Dynamics 365.
- An active Office 365 subscription (if using Office 365 services). For more information, see the Office 365 specific requirements section of this article.
- You can 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 is not an ExpressRoute connectivity partner, you can still connect to the Microsoft cloud through a cloud exchange provider.
- Redundant connectivity: there is no redundancy requirement on physical connectivity between you and your provider. Microsoft does require redundant BGP sessions to be set up between Microsoft’s routers and the peering routers, even when you have just one physical connection to a cloud exchange.
- Routing: depending on how you connect to the Microsoft Cloud, you or your provider need to set up and manage the BGP sessions for routing domains. Some Ethernet connectivity provider or cloud exchange provider may offer BGP management as a value-add service.
- NAT: Microsoft only accepts public IP addresses through Microsoft peering. If you are using private IP addresses in your on-premises network, you or your provider need to translate the private IP addresses to the public IP addresses using the NAT.
- QoS: Skype for Business has various services (for example; voice, video, text) that require differentiated QoS treatment. You and your provider should follow the QoS requirements.
- Network Security: consider network security when connecting to the Microsoft Cloud via ExpressRoute.
If you plan to enable Office 365 on ExpressRoute, review the following documents for more information about Office 365 requirements.
- Overview of ExpressRoute for Office 365
- Routing with ExpressRoute for Office 365
- Office 365 URLs and IP address ranges
- Network planning and performance tuning for Office 365
- Network bandwidth calculators and tools
- Office 365 integration with on-premises environments
- ExpressRoute on Office 365 advanced training videos
If you plan to enable Dynamics 365 on ExpressRoute, review the following documents for more information about Dynamics 365
- For more information about ExpressRoute, see the ExpressRoute FAQ.
- Find an ExpressRoute connectivity provider. See ExpressRoute partners and peering locations.
- Refer to requirements for Routing, NAT, and QoS.
- Configure your ExpressRoute connection.