Azure ExpressRoute for Office 365

Learn how Azure ExpressRoute is used with Office 365 and how to plan the network implementation project that will be required if you are deploying Azure ExpressRoute for use with Office 365. Infrastructure and platform services running in Azure will often benefit by addressing network architecture and performance considerations. We recommend ExpressRoute for Azure in these cases. Software as a Service offerings like Office 365 and Dynamics 365 have been built to be accessed securely and reliably via the Internet. Accordingly, we only recommend ExpressRoute for these applications in specific scenarios. You can read about Internet performance and security and when you might consider Azure ExpressRoute for Office 365 in the article Network connectivity to Office 365.

Note: If you want to enable Microsoft Peering for use with Azure ExpressRoute for Office 365 you need to work with your Microsoft Sales Account Team to review and approve the request. Until your Azure subscription has been approved, attempting to enable Microsoft Peering will return an error message.

You can now add a direct network connection to Office 365 for selected Office 365 network traffic. Azure ExpressRoute offers a direct connection, predictable performance, and comes with an uptime SLA of 99.9% for the Microsoft networking components. An internet connection is still required for workloads that are not supported over Azure ExpressRoute.

Azure ExpressRoute for Office 365

In addition to internet connectivity, some customers may choose to route a subset of their Office 365 network traffic over a direct connection that offers predictability and a 99.9% uptime SLA for the Microsoft networking components. Azure ExpressRoute provides customers this dedicated network connection to Office 365 and other Microsoft cloud services.

Regardless of whether you have an existing MPLS WAN, ExpressRoute can be added to your network architecture in one of three ways, through a supported cloud exchange co-location provider, an Ethernet point-to-point connection provider, or through an MPLS connection provider. See what providers are available in your region. The direct ExpressRoute connection will enable connectivity to the applications outlined in What do I get when I sign-up below. Network traffic for all other applications and services will continue to traverse the internet.

Consider the following high level network diagram which shows a typical Office 365 customer connecting to Microsoft’s datacenters over the internet for access to all Microsoft applications such as Office 365, Windows Update, and TechNet. Customers use a similar network path regardless of whether they’re connecting from an on-premises network or from an independent internet connection.

Office 365 network connectivity

Now look at the updated diagram which depicts an Office 365 customer who uses both the internet and ExpressRoute to connect to Office 365. Notice that some connections such as Public DNS and Content Delivery Network nodes still require the public Internet connection. Also notice the customers users who are not located in their ExpressRoute connected building are connecting over the Internet.

Office 365 connectivity with ExpressRoute

Still want more information? Learn how to manage your network traffic with Azure ExpressRoute for Office 365 and learn how to configure Azure ExpressRoute for Office 365.

(Back to top)

Office 365 customers with at least 500 purchased Office 365 seats who are implementing ExpressRoute can acquire the required ExpressRoute Premium Add-on at no additional expense via the new Azure ExpressRoute SKU for eligible Office 365 customers. This SKU includes all Premium Add-on features, allowing customers to enable Office 365 over ExpressRoute with a single ExpressRoute SKU, priced equivalently to the ExpressRoute Standard offering. Please contact your Microsoft account manager for more details. Office 365 customers that don’t qualify for this offer will be required to purchase the premium service based on published price.

The following table lists the Office 365 services that are supported over ExpressRoute. Please review the Office 365 endpoints article to understand which network requests for these applications require internet connectivity.

Applications included

Exchange Online1

Exchange Online Protection1


Skype for Business Online1

SharePoint Online1

OneDrive for Business1

Project Online1

Portal and shared1

Azure Active Directory1

AAD Connect1

Office Online1

1Each of these applications have internet connectivity requirements not supported over ExpressRoute, see the Office 365 endpoints article for more information.

The services that aren’t included with ExpressRoute for Office 365 are Office 365 ProPlus client downloads, On-premises Identity Provider Sign-In, and Office 365 (operated by 21 Vianet) service in China.

(Back to top)

Implementing ExpressRoute requires the involvement of network and application owners and requires careful planning to determine the new network routing architecture, bandwidth requirements, where security will be implemented, high availability, and so on. To implement ExpressRoute, you must;

  1. Fully understand the need ExpressRoute satisfies in your Office 365 connectivity planning. Understand what applications will use the internet or ExpressRoute and fully plan your network capacity, security, and high availability needs in the context of using both the internet and ExpressRoute for Office 365 traffic.

  2. Determine the egress and peering locations for both internet and ExpressRoute traffic1.

  3. Determine the capacity required on the internet and ExpressRoute connections.

  4. Have a plan in place for implementing security and other standard perimeter controls1.

  5. Have a valid Microsoft Azure account to subscribe to ExpressRoute.

  6. Select a connectivity model and an approved provider. Keep in mind, customers can select multiple connectivity models or partners and the partner doesn’t need to be the same as your existing network provider.

  7. Validate deployment prior to directing traffic to ExpressRoute.

  8. Optionally implement QoS and evaluate regional expansion.

1Important performance considerations. Decisions here can dramatically impact latency which is a critical for applications such as Skype for Business.

For additional references, use our routing guide in addition to the ExpressRoute documentation.

To purchase ExpressRoute for Office 365, you’ll need to work with one or more approved providers to provision the desired number and size circuits with an ExpressRoute Premium subscription. There are no additional licenses to purchase from Office 365.

Ready to sign-up for ExpressRoute for Office 365?

(Back to top)

See Also

Network connectivity to Office 365

Routing with ExpressRoute for Office 365

Network planning with ExpressRoute for Office 365

Implementing ExpressRoute for Office 365

Using BGP communities in ExpressRoute for Office 365 scenarios (preview)

Media Quality and Network Connectivity Performance in Skype for Business Online

Office 365 performance tuning using baselines and performance history

Performance troubleshooting plan for Office 365

Office 365 URLs and IP address ranges

Office 365 network and performance tuning

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!