![]() ![]() ![]() ![]() The only problem? There is no way to force the “connect automatically” setting in the native VPN client, thus the client’s major requirement was not met. This VPN client is designed to compliment the native VPN client and adds support for MFA as well as allowing connections from the native VPN interface. The next suggestion was to leverage the Azure VPN Client from the Microsoft store. The problem, as it turned out is the native VPN client has a limit of 25 route rules per connection - something that *shouldn’t* normally be a problem, but was insurmountable in this scenario. If we use this, we can utilize the native VPN policies within Intune which let us define everything we need - including setting the connection to automatically connect. My first suggestion was to simply use the built-in VPN client that comes with Windows 10. The requirements were quite simple - They were building out an Azure Point-To-Site VPN solution and needed me to come up with a way to deliver the connection to the end user devices. One of my clients recently came to me asking for assistance to set up a new VPN solution. Published: File under: Azure, Intune, PowerShell ![]()
0 Comments
Leave a Reply. |