![]() ![]() ![]() 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. For information about optimizing Microsoft 365 worldwide tenant performance for users in China, see Microsoft 365 performance optimization for China users.For information about how to configure Stream and live events in VPN environments, see Special considerations for Stream and live events in VPN environments. ![]() For guidance on securing Teams media traffic in VPN split tunneling environments, see Securing Teams media traffic for VPN split tunneling.For a detailed list of VPN split tunneling scenarios, see Common VPN split tunneling scenarios for Microsoft 365.For an overview of using VPN split tunneling to optimize Microsoft 365 connectivity for remote users, see Overview: VPN split tunneling for Microsoft 365.This article is part of a set of articles that address Microsoft 365 optimization for remote users.
0 Comments
|