This suggestion has two parts:
1. Use default route or forced tunneling on P2S client rather than split tunneling
2. Enable Azure VPN gateway as an forward proxy to the Internet
At this point, these will be considered as long term roadmap items.
Yushun [MSFT]Bhavesh Gajjar supported this idea ·
An error occurred while saving the commentBhavesh Gajjar commented
We recently deployed Azure Virtual WAN and are in the process of testing out the P2S VPN capabilities. So far the platform works well however our IT Security folk are raising concerns with this technology as a result of the split tunneling. Having the ability to turn off the split tunneling seems to be a non-negotiable for IT Security. This would be a real road-blocker for a full switch to Azure Virtual WAN's P2S VPN.
I would imagine that other organizations are also facing similar challenges with the "no choice on split tunneling" through the P2S VPN.
I see that in 2016 this was considered as part of the "long term" roadmap. It's almost 4 years later, any idea when this type of capability would be implemented?