![]() Essentially this is the traffic that we need to take special care of and is also the traffic that will put incredible pressure on traditional network paths and VPN infrastructure. This small group of endpoints accounts for around 70% - 80% of the volume of traffic to the Microsoft 365 service including the latency sensitive endpoints such as those for Teams media. There are currently just four URLS and 20 IP subnets that need to be optimized. In the Microsoft 365 URLs and IP address ranges article, Microsoft clearly identifies the key endpoints you need to optimize and categorizes them as Optimize. The diagram below illustrates how the recommended VPN split tunnel solution works: In this article, you'll find the simple steps required to migrate your VPN client architecture from a VPN forced tunnel to a VPN forced tunnel with a few trusted exceptions, VPN split tunnel model #2 in Common VPN split tunneling scenarios for Microsoft 365. In most cases, this can be effectively achieved within hours and is then scalable to other workloads as requirements demand and time allows. An equivalent or even superior security model can be applied at different layers to remove the need to secure all traffic at the egress of the corporate network. These steps adjust the legacy VPN approach for a few defined endpoints that bypass bottlenecked VPN servers. Microsoft's recommended strategy for optimizing remote worker's connectivity is focused on rapidly mitigating problems and providing high performance with a few simple steps.
0 Comments
Leave a Reply. |