5 Terrible Things You Should Not Do with Your SaaS/Office 365 Networking
April 18, 2017

Jason Lieblich
Exoprise

Share this

The move to cloud-based solutions like Office 365, Google Apps and others is one of the biggest fundamental changes IT professionals will undertake in the history of computing. Microsoft Office 365 already has >70 million paid subscriptions with a goal to have annualized revenue reach $20 BILLION by 2018.


The cost savings and productivity enhancements available to organizations are huge. But these savings and benefits can't be reaped without careful planning, network assessment, change management and continuous monitoring. Read on for things that you shouldn't do with your network in preparation for a move to one of these cloud providers.

1. Don't expect to keep the network the same as when everything was on-premise

Networks will need to change with the adoption of massive cloud-based services like Office 365. When all the traffic was on-premise, internal routers and network paths may have been burdened. Now that the traffic is largely external, it will stress the network differently and have different IT infrastructure dependencies. We call it "Service Delivery Chain."


You probably thought when you adopted cloud-based services like Office 365 everything was going to be easy — just give the user a browser — but that's not the case. The Service Delivery Chain — including Single-Sign-In, Azure AD, proxies, firewalls, gateways, etc. — complicates SaaS application delivery. Especially at the branch office, for mobile and telecommuters too. End-to-end application response, uptime and availability for apps like Exchange Online, SharePoint Online and Skype for Business Online needs to be tested and measured.

2. Don't expect to keep all the firewalls and proxies just like before - they will need to change

This is a common initial desire for many mid-to-large enterprises — they want to proxy all the traffic between services such as Office 365, G-Suite and their end-users — no matter where they are. This is often seen at the beginning of migration to the cloud but it doesn't usually last or not in its initial form.

Proxying all your traffic for these services requires additional investment. It's more than likely your proxies will not be able to handle the additional load that the shift to cloud services places on them. You should synthesize and load-test the various Office 365 apps and workloads prior to and during a migration to Office 365. And you should make sure that your testing tools support proxies, single sign-on and the entire Service Delivery Chain.

3. Don't assume just because you route everything centrally, you don't need to measure end-to-end

Enterprise's may have had their own MPLS-routed networks in place for years. They put it in place back in the good old days of Exchange 2003 ;-). Then they go and believe that a decade-old network design will survive the shift to cloud/SaaS. Often, coincidental with this old network design, is their desire that they only monitor their central network because "everything just routes through to one place".

Talk about head meeting sand. If you're only monitoring from one location on the network, then you will have no idea what the experience is for end-users on the other side.

Additionally, routing everything centrally can be slow, expensive and less fault tolerant then if you sent secure, SSL-traffic directly over the Internet for branch offices and remote workers. Office 365 and wide-scale SaaS adoption for an organization places different demands on a network end-to-end.

4. Don't wait for direct data center connections like ExpressRoute for Office 365 or Azure

ExpressRoute is a new data center connection type that Microsoft has begun offering for fast connectivity from your own routed and VPN'd LAN to Office 365 and Azure tenants. Other SaaS providers often offer something similar.

Direct data center connections like ExpressRoute are still in their infancy and remain expensive. Customers still must backhaul their traffic from branch offices and other locations through their private WAN, into and out of the ExpressRoute colocation. While it sounds like it could make things simpler and faster, it does make the Service Delivery Chain longer and more complex where lots could go wrong that affects end-user experience.

5. Don't assume the problem is just going to be with the provider

The assumption that only providers like Microsoft, Google or Amazon are going to have problems is NOT a good way to start an organization's journey to wide-scale adoption of cloud services. You will have outages along the way and even post migration. The outages will occur within your own networks, your ISPs, your proxies, your Single Sign-On providers — everywhere. But with the right end-to-end monitoring and management you'll be able to quantify them and their consequences and hold each of the parties accountable for the Service Level Agreements they are signing up for.

Jason Lieblich is Founder and President of Exoprise
Share this

The Latest

October 20, 2020

Although cost control/expense management remains top of mind, organizations are realizing the necessity of technology solutions to enable them to steer the business during these turbulent times, according to IDG's CIO Pandemic Business Impact Study ...

October 19, 2020

The COVID-19 pandemic has compressed six years of modernization projects into 6 months. According to a recent report, IT leaders have accelerated projects aimed at increasing productivity and business agility, improving application performance and end-user experience, and driving additional revenue through existing channels ...

October 15, 2020

There is no doubt that automation has become the key aspect of modern IT management. The end-user computing market is no exception. With a large and complex technology stack and a huge number of applications, EUC specialists need to handle an ever-increasing number of changes at an ever-increasing rate. Many IT organizations are starting to realize that they can no longer control the flow of changes. It is time to think about how to facilitate change ...

October 14, 2020

Starting this September, the lifespan of an SSL/TLS certificate has been limited to 398 days, a reduction from the previous maximum certificate lifetime of 825 days. With this change, everyone needs to more carefully monitor SSL certificate expiration and server characteristics ...

October 13, 2020

Nearly 6 in 10 responding organizations have accelerated their digital transformations due to the COVID-19 pandemic, according to The IBM Institute for Business Value study COVID-19 and the Future of Business ...

October 08, 2020

Two-thirds (67%) of those surveyed expect the sheer quantity of data to grow nearly five times by 2025, according to a new report from Splunk: The Data Age Is Here. Are You Ready? ...

October 07, 2020

Gaming introduced the world to a whole new range of experiences through augmented reality (AR) and virtual reality (VR). And consumers are really catching on. To unlock the potential of these platforms, enterprises must ensure massive amounts of data can be transferred quickly and reliably to ensure an acceptable quality of experience. As such, this means that enterprises will need to turn to a 5G infrastructure powered by an adaptive network ...

October 06, 2020

A distributed, remote workforce is the new business reality. How can businesses keep operations going smoothly and quickly resolve issues when IT staff is in San Jose, employee A is working remotely in Denver at their home and employee B is a salesperson still doing some road traveling? The key is an IT architecture that promotes and supports "self-healing" at the endpoint to take care of issues before they impact employees. The essential element to achieve this is hyper-automation ...

October 05, 2020

In Episode 10, Prem Naraindas, CEO of Katonic.ai, joins the AI+ITOPS Podcast to discuss how emerging technologies can make life better for ITOps ...

October 02, 2020

Sean McDermott on the AI+ITOPS Podcast: "AIOps is really about the processing of vast amounts of data and the ability to move into a more analytical, prescriptive and automated methodology."