UPDATE DEC-16: The language on the support page linked in this blog has been changed so it no longer appears that it is “not recommended” and more so that customers need to learn, understand and design suitable network scenarios (which is ideal anyway) with ExpressRoute.

Increasingly a number of customers I speak to tell me they are planning to put in ExpressRoute as part of their Office 365 project.

What I have seen change over the past year is the attitude of “tell me about ExpressRoute” to being “oh yes, we’re getting ExpressRoute”.

Well this change to the Microsoft guidance might put the brakes on a lot of those deployments. If you look at the Azure ExpressRoute for Office 365 support page, you’ll see this key line buried in the first paragraph: “Azure ExpressRoute is not required or recommended for Office 365 except where mandated to use direct networking for regulatory purposes or where a network assessment for Skype for Business connectivity requires it”.

Note the key words in there are “not required or recommended” unless it is mandated or Skype needs it for quality purposes.

This does beg the question: why would you use ExpressRoute for Office 365 outside of it being mandated or needed for Cloud PBX? With Azure this makes common sense as you want it to be a logical extension of your network so that applications and virtual machines can easily see each other, and all traffic is “off net” (ie. unmetered). However, with Office 365 the desire is to have users working from wherever they are and not necessarily tied to the corporate network in order to access their services. Certainly having the best of both worlds is optimal – if you’re on the corporate network all traffic is off net and ideally faster, and when outside of the corporate network users access the service via the Internet.

So this change to guidance is something important that organisations need to take heed of as it’s no longer assumed you can simply get an ExpressRoute service to Office 365 just because you want it – you need to have a very good reason that can’t be debated.

6 comments

    • Loryan Strant

      Reply

      Unfortunately not – unless mandated (which you’d be hard pressed to get/find for QoS for those workloads).
      You might need to look at something like a Riverbed SteelHead WAN accelerator with the Office 365 license to help achieve better performance.

  1. matt

    Reply

    I was looking for the buried statement that said ExpressRoute was not recommended. And, I had heard it was being put on hold or discontinued. But, the statement you reference isn’t there. Can you confirm if the article has been changed since your post? Thanks very much in advance.

    • Loryan Strant

      Reply

      Looking at the support page it does look like it has been updated along with the messaging to be more gentle and guiding. 🙂

  2. Mary Chandran

    Reply

    Hi Loryan,

    We are in the process of procuring express route for office365.Your article is very helpful. Just a clarification does that mean using express route only for office 365 does not allow users to access from anywhere? Do they have to get to corporate network to access the Office365.Please note we are going for express route just for Office 365 no other VM or application is on Azure.

    Thanks,
    Mary

    • Loryan Strant

      Reply

      Hi Mary, the guidance has changed a bit since this article was published. In short the answer is no – people can still connect in via the Internet. My suggestion would be to speak to the provider who is delivering the ExpressRoute connectivity for your organisation and get the network designed correctly so that remote users aren’t necessarily traversing a VPN and then ExpressRoute to access Office 365 if they don’t need to be.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: