<\/h2>\n<\/div>\n
<\/p>\n
60,000 ft: View from Microsoft Global Cloud Network<\/strong><\/h1>\n <\/p>\n
Office 365 is a distributed Software delivered via the cloud, -as-a-Service (SaaS). Outlook, Word, PowerPoint, Skype are some of the well-known application services delivered by O 365. These services run on the client system which connects them to servers; e.g Exchange Server hosted in Microsoft Cloud. The client-server service relies on the communication between the\u00a0user\/client system in branch locations and the servers residing in Microsoft cloud. As a result, the degree QoE depends on two factors:<\/p>\n
<\/p>\n
a) Network reliability<\/em><\/strong><\/p>\nb) The latency between Office 365 clients and service front doors.<\/em><\/strong><\/p>\n <\/p>\n
Network reliability and latency result from various factors. For example, first, the branch user traffic passes through DNS resolution. This DNS server generally, resides in the enterprise data center (DC). The traffic then travels via the datacenter again. This is because the egress is via a proxy server. The traffic also goes through NATing and the same path is followed back while getting the ingress from Office 365 based services hosted in Cloud, along with some trust issues and checking the pockets (read as packets) before allowing inside the network.<\/p>\n
<\/p>\n
The ideal scenario would be to have the least amount of noise on the way to reach the Microsoft Global Network. Below are recommendations from Microsoft which will help enterprises to optimize Office 365 network performance.<\/p>\n
<\/p>\n
\n- Identify Office 365 network traffic.<\/li>\n
- Allow local egress of Office 365 network traffic from each location where client systems connect to Office 365.<\/li>\n
- Allow Office 365 traffic to bypass proxies and packet inspection devices.<\/li>\n<\/ul>\n
<\/p>\n
After analyzing the\u00a0Office 365 Network Connectivity Principles<\/a>, we can come to the\u00a0conclusion that Office 365 can do with a better Network Architecture than the traditional Hub-Spoke model.<\/div>\n <\/p>\n
<\/p>\n
105 ft: Tulip Data Center, Bangalore India – One of the largest in the world.<\/strong><\/h2>\n <\/p>\n
Traditionally, enterprises steered Office 365 traffic from the branch to enterprise datacenter using MPLS. In DC, the traffic was backhauled for Inspection, proxying and several other operations. Once done, the application traffic was then steered to the Microsoft Global Network via any Internet connection. However, this approach is flawed.<\/p>\n
<\/p>\n
Following the traditional networking approach enterprises are sending all the traffic from branch including Office 365 over “traditional” MPLS links to the Datacenter where a large number of operations (Inspection and proxying etc.) on application traffic is done and then sent to Microsoft Global Network via any Internet connection.<\/p>\n
<\/p>\n
Now, let us explain where this approach is flawed.<\/p>\n
\n- First things first, your traditional MPLS is being used extensively and as users are getting added to your organizations, demand to increase the width of MPLS pipe aka bandwidth is digging a hole in your IT budget!<\/li>\n
- Second, your users keep complaining about the performance issues, they often compare the performance with their personal computers and personal emails (no datacenter there!)<\/li>\n
- Third, your enterprise applications suffer, and you get more user complaints on the enterprise apps’ performance.
\nFourth, your IT team is struggling to solve these performance issues and end up adding more of the traditional and investment-heavy MPLS to your IT expense<\/li>\n<\/ul>\n <\/p>\n
<\/p>\n
15 ft: Branch Office<\/strong><\/h2>\n <\/p>\n
The significant point of view here would be from the users. Users expect high speed, high performance which leads to a better experience of the overall application.<\/p>\n
<\/p>\n
<\/p>\n
![\"\"](\"https:\/\/lavellenetworks.com\/lavellenetworks_blogs\/wp-content\/uploads\/2020\/02\/O365_Blog_Banner-768x384-1-300x150.jpg\")
<\/p>\n
Below Sea Level: Broadband Optical Fiber Connections<\/strong><\/p>\n <\/p>\n
<\/p>\n
Broadband has always been used in the traditional approach. Remember Datacenter will egress the Office 365 traffic via any internet connection? Broadband always had the ability to take traffic directly from branch to Microsoft Global Network and its benefits include<\/span>:<\/p>\n <\/p>\n
\n- Optimal performance by optimizing route length.<\/li>\n
- Dynamic routing to the nearest Office 365 entry point.<\/li>\n
- Reducing the load on corporate network Infrastructure aka Precious!<\/li>\n
- And the jackpot- it knows Office 365 traffic creates secure connections on both ends by leveraging client endpoint security and cloud security features.<\/li>\n<\/ol>\n
<\/h2>\n<\/h2>\nScaleAOn Level: Best view of the network that one can have!<\/b><\/span><\/h2>\n <\/p>\n
<\/p>\n
![\"\"](\"https:\/\/lavellenetworks.com\/lavellenetworks_blogs\/wp-content\/uploads\/2020\/02\/Things-you-need-to-know-about-Office-365-From-Networks-Perspective-Blog-Banner_1-768x353-1-300x138.jpg\")
<\/p>\n
<\/p>\n
<\/p>\n
For the last 5 years, Lavelle Networks has prioritized making the application experience better than ever from the network perspective. A thorough analysis was done, considering all the relevant levels and their perspectives to provide connectivity experience that is in the best interest of users.<\/p>\n
<\/p>\n
b) The latency between Office 365 clients and service front doors.<\/em><\/strong><\/p>\n <\/p>\n Network reliability and latency result from various factors. For example, first, the branch user traffic passes through DNS resolution. This DNS server generally, resides in the enterprise data center (DC). The traffic then travels via the datacenter again. This is because the egress is via a proxy server. The traffic also goes through NATing and the same path is followed back while getting the ingress from Office 365 based services hosted in Cloud, along with some trust issues and checking the pockets (read as packets) before allowing inside the network.<\/p>\n <\/p>\n The ideal scenario would be to have the least amount of noise on the way to reach the Microsoft Global Network. Below are recommendations from Microsoft which will help enterprises to optimize Office 365 network performance.<\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n Traditionally, enterprises steered Office 365 traffic from the branch to enterprise datacenter using MPLS. In DC, the traffic was backhauled for Inspection, proxying and several other operations. Once done, the application traffic was then steered to the Microsoft Global Network via any Internet connection. However, this approach is flawed.<\/p>\n <\/p>\n Following the traditional networking approach enterprises are sending all the traffic from branch including Office 365 over “traditional” MPLS links to the Datacenter where a large number of operations (Inspection and proxying etc.) on application traffic is done and then sent to Microsoft Global Network via any Internet connection.<\/p>\n <\/p>\n Now, let us explain where this approach is flawed.<\/p>\n <\/p>\n <\/p>\n <\/p>\n The significant point of view here would be from the users. Users expect high speed, high performance which leads to a better experience of the overall application.<\/p>\n <\/p>\n <\/p>\n Below Sea Level: Broadband Optical Fiber Connections<\/strong><\/p>\n <\/p>\n <\/p>\n Broadband has always been used in the traditional approach. Remember Datacenter will egress the Office 365 traffic via any internet connection? Broadband always had the ability to take traffic directly from branch to Microsoft Global Network and its benefits include<\/span>:<\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n For the last 5 years, Lavelle Networks has prioritized making the application experience better than ever from the network perspective. A thorough analysis was done, considering all the relevant levels and their perspectives to provide connectivity experience that is in the best interest of users.<\/p>\n <\/p>\n\n
105 ft: Tulip Data Center, Bangalore India – One of the largest in the world.<\/strong><\/h2>\n
\n
\nFourth, your IT team is struggling to solve these performance issues and end up adding more of the traditional and investment-heavy MPLS to your IT expense<\/li>\n<\/ul>\n15 ft: Branch Office<\/strong><\/h2>\n
<\/p>\n\n
<\/h2>\n
<\/h2>\n
ScaleAOn Level: Best view of the network that one can have!<\/b><\/span><\/h2>\n
<\/p>\n