Why network performance is crucial for your Office 365 deployment Feb 11, 2019


It shouldn’t need to be said that the network performance is crucial when connecting to cloud services like Office 365. However, many organisations still have network infrastructure only focused on supporting user access to on-premises systems, especially those at the beginning of their journey to the cloud.

The user experience is crucial

Moving to Office 365 isn’t just about migration performance, or even raw bandwidth availability to upload and download files and email. It is also a shift in the way applications like Office interact with the storage they’re stored on and if you use services like Microsoft Teams, could support voice and video calls too.

Migrating to Exchange Online is a good place to start

One of the most widely adopted – and often starting point for an Office 365 migration is Exchange Online. Moving to Exchange Online is well understood – and thanks to Outlook’s capabilities to cache data, is slightly more forgiving of occasional network disruption than other services.
However, even when using Outlook, capabilities like checking availability, accessing Online Archives or Shared Mailboxes require low latency to maintain a good user experience, rather than simply having enough bandwidth available.

Always consider your network

Although OneDrive for Business as a sync client makes it possible to cache documents offline – when your users are online, Office 365 Pro Plus does require suitable network connectivity too. You may be caching your files locally, but when you open a document in Word, Excel or PowerPoint (for example), Office will by default expect to provide the capability for real-time editing of that document stored in SharePoint Online or OneDrive for Business. That means double clicking a file in Windows Explorer might provide a worse user experience than a local file share if the network has not been considered up-front.

Microsoft Teams brings in further technical considerations

Teams being the hub for a variety of Office 365 services means that any underlying performance issues could be further exaggerated too.
When you consider the Skype aspects of Teams – like calling and IM – you’ll need to ensure that the network connection quality is not only low-latency and provides enough bandwidth, but it’s also consistent, so that the user doesn’t suffer from issues like jitter. The last thing you’ll want is the CEO to be moved from the legacy on-premises phone system over to Teams and find they can’t make a reliable call.
But Teams isn’t only about Skype services. As a front door to SharePoint Online, you’ll also need to consider how co-authoring of documents in real time will perform too.
When a user edits a document in Teams, they’ll use Office Online by default, within the Teams client itself. This usually means that those same issues Office 365 Pro Plus might suffer from on a badly performing network connection will show in Teams as well.

Clear recommendations from Microsoft

Microsoft are clear and consistent about recommendations for network connectivity to Office 365. These days ExpressRoute is not recommended and instead, Microsoft have designed Office 365 in such a way that best performance is achieved by accessing the services over the Internet.
To do this, Microsoft peer their global network with a large number of ISPs and build out Office 365 service front doors within most regions. A service front door is a set of servers built within the region that process traffic for their specific services, like Exchange, SharePoint and Teams and optimise the traffic as soon as it enters the Microsoft Global Network.
This means that the sooner your client breaks out to the Internet, the sooner they’ll be more able to have a good experience with Office 365. Even if your Office 365 tenant is in Europe, but you have a user accessing Office 365 from North America, if they hit a service door close to their location, they are likely to have a good experience.
Conversely, when an organisation chooses to route Office 365 traffic over their existing WAN infrastructure and break out traffic to Office 365 from a central location – or worse – use a Proxy Server as well – the experience is often terrible for users.
Even with an optimal network, even the way DNS requests are served back to clients can affect performance. For example, if you service DNS requests from a single datacentre in the UK, your clients in mainland Europe might attempt to connect to UK Office 365 endpoints for Exchange Online, rather than the closest service front doors in-country.

Comments

Post a Comment

Popular posts from this blog

Microsoft Office E1 vs E3 vs E5

Microsoft Office 365  comes in three different flavors for Enterprise: E1, E3, and E5. With each successive level, you get more – but what is included, exactly? A lot of research was done to create this comparison. It will generate a score for each of the seven different versions of Office 365, plus provide a few other things to think about. Selecting the right Office 365 version is one of the most important steps before migrating over to the cloud. However, keep in mind that because these are subscription type licenses – you are never locked in on the license you choose. In essence, you can mix and match, downgrade or upgrade your licenses depending on your changing business needs. Microsoft Office E1 O365 E1 is the “lightest” version of the Enterprise level plans. The application and services included in E1 are: Email and Calendars via Microsoft Exchange, Enterprise Social with Yammer, communication and team sites with SharePoint, OneDrive for Business with 1TB clo...
Read more

New device modeling experience in Azure IoT Central

Image
On the Azure IoT Central team, we are constantly talking with our customers to understand how we can continue to provide more value. One of our top pieces of product feedback has been for a clearer device modeling experience that separates the device instance from the device template. Previously, viewing the device and editing the device template took place on the same page through an “Edit Template” button. This caused a lack of clarity between when you were making a change that applied to the device or if your changes were getting applied to all devices in that template. Recently we've begun a flighted rollout of a new device modeling experience that begins to directly address this feedback. For app builder roles, we have introduced a new “Device Templates” navigation tab that replaces the existing “Application Builder” tab, as well as updated the pattern in which you view or edit your device templates. To edit your device templates, you can visit the “Device Templates” tab ...
Read more

Microsoft Whiteboard: now more colorful and customizable than ever

Image
The Whiteboard team has been hard at work since our announcements at Ignite. A s we gather more and more feedback from our growing customer base, we’ve also been rolling out great new features, with more on the way soon. Let’s take a look at what’s changed. New pen colors and thicknesses Responding to popular demand, we’ve added 10 new pen colors and three more pen thicknesses, allowing Whiteboard users to express themselves more colorfully and boldly than ever. To access the new colors and thicknesses, click on the pen you have selected to pop up the palette. Background colors and gridlines Just like it’s great to have options for pen color, customizing the look and feel of the board itself can help your ideas stand out – and can make your boards more usable and readable as well. Whiteboard now offers nine options for board color and eight types of gridlines that can be used together or separately to customize your boards’ backgrounds. These options are selectable in...
Read more