The One Thing Destroying Office 365 Deployments - and How to Fix It - Part 1
September 11, 2018

Wilfried van Haeren
Edgeworx Solutions

Share this

Market exuberance for Office 365 has inspired business mandates to adopt the cloud-hosted collaboration and productivity suite without regards to the underlying chaos. While multi-location organizations are virtualizing, operating models haven’t necessarily changed. This partial transformation that excludes automation and simplification of the network puts Office 365 deployments (and other software-as-a-service offerings) in danger of failing.

Take banking as an example — IT must design an architecture that can support the varying needs of thousands of branch locations and multiple divisions. Where the consumers at the branches might require online banking and informational video streaming, the trading division (a much smaller subset of the organization that typically makes the bulk of the revenue) will need their applications prioritized.

To achieve this, IT may start to build an overlay network, relaying this blend of application services across the plain old data network and continuing to rely on backhauling. In these situations, when a customer wants to complete a large money transfer or open an account, the data packets of this application may cross an entire continent before going back to a cloud provisioning center that is next-door. Unnecessary travel isn’t just inefficient in cost, bandwidth, and response time — it’s where chaos is born, and impacts application performance and end-user response time through increased latency during transfer.

Chaos Takes Many Forms, But Always Creates the Same Challenges

Chaos isn’t limited to backhauling or using generic devices to route traffic. Instead, it can include:

■ Stacking physical hardware appliances with different network functions in an attempt to enforce business policies at the branch edge of the network

■ Running a separate infrastructure for important business functions

■ Using connectivity that was chosen based on price, rather than performance and agility

■ A network platform lacking orchestration or automation capabilities

Regardless of the exact network configuration, chaos consistently creates the following challenges when attempting to deploy Office 365:

Poor Performance and End-User Experience - Long and inefficient traffic patterns add latency and diminish the user experience. Additionally, without any orchestration or automation there is no distinction between transactional or bulk application types for appropriate performance and availability controls.

Increased Costs - While on the surface, replacing legacy desktop applications appears to be a cost reduction, deploying Office 365 on existing architecture without fine-grained application policy and bandwidth controls leads to increasing connectivity costs to manage the application demands.

Diminished Visibility - The complexity of chaos can lead to confusion or clouding of current bandwidth usage, unimportant traffic traveling across an expensive MPLS connection, and overprovisioning to combat poor performance that is unrelated to bandwidth.

Read The One Thing Destroying Office 365 Deployments - and How to Fix It - Part 2, covering how SD-WAN tames Office 365 chaos.

Wilfried van Haeren is CTO at Edgeworx Solutions
Share this

The Latest

January 17, 2019

APMdigest invited industry experts to predict how Cloud will evolve and impact application performance and business in 2019. Part 3, the final installment, covers monitoring and managing application performance in the Cloud ...

January 16, 2019

APMdigest invited industry experts to predict how Cloud will evolve and impact application performance and business in 2019. Part 2 covers multi-cloud, hybrid cloud, serverless and more ...

January 15, 2019

As a continuation of the list of 2019 predictions, APMdigest invited industry experts to predict how Cloud will evolve and impact application performance and business in 2019 ...

January 14, 2019

APMdigest invited industry experts to predict how Network Performance Management (NPM) and related technologies will evolve and impact business in 2019 ...

January 11, 2019

I would like to highlight some of the predictions made at the start of 2018, and how those have panned out, or not actually occurred. I will review some of the predictions and trends from APMdigest's 2018 APM Predictions. Here is Part 2 ...

January 10, 2019

I would like to highlight some of the predictions made at the start of 2018, and how those have panned out, or not actually occurred. I will review some of the predictions and trends from APMdigest's 2018 APM Predictions ...

January 09, 2019

I sat down with Stephen Elliot, VP of Management Software and DevOps at IDC, to discuss where the market is headed, how legacy vendors will need to adapt, and how customers can get ahead of these trends to gain a competitive advantage. Part 2 of the interview ...

January 08, 2019

Monitoring and observability requirements are continuing to adapt to the rapid advances in public cloud, containers, serverless, microservices, and DevOps and CI/CD practices. As new technology and development processes become mainstream, enterprise adoption begins to increase, bringing its own set of security, scalability, and manageability needs. I sat down with Stephen Elliot, VP of Management Software and DevOps at IDC, to discuss where the market is headed, how legacy vendors will need to adapt, and how customers can get ahead of these trends to gain a competitive advantage ...

December 20, 2018

APMdigest invited industry experts to predict how APM and related technologies will evolve and impact business in 2019. Part 6 covers the Internet of Things (IoT) ...

December 19, 2018

APMdigest invited industry experts to predict how APM and related technologies will evolve and impact business in 2019. Part 5 covers the evolution of ITOA and its impact on the IT team ...