Create a Device Level Windows VPN Policy

You can configure a VPN profile policy for your Windows devices to securely and remotely access your organization’s network. The device must be enrolled in JumpCloud MDM. This policy works on devices running Windows 10/11.

Note:

This is a device level policy that applies system-wide to the device and all of its users. You can bind this policy to individual devices or device groups. For policies that apply to a specific user's profile across devices, see Get Started: Policies and Learn More section of this article.

Creating the Policy

To create a VPN policy for Windows devices, do the following:

Selecting the Policy Template

  1. Log in to the JumpCloud Admin portal.

Important:

If your data is stored outside of the US, check which login URL you should be using depending on your region. If your organization uses LDAP, RADIUS, or requires firewall allow list configuration, the Fully Qualified Domain Names (FQDNs) will also be region specific. See JumpCloud Data Centers for the URLs, FQDNs, and IP addresses.

  1. Go to Device Management > Policy Management. The Policy Management page is displayed.
  2. On the Policy Management page, click +Add New.
  3. Select Device Policy to assign the policy to devices and device groups. On the New Device Policy page:
    • Select the Windows tab.
    • Search and select the policy name and click Configure. The Details tab of the policy is displayed.
    • On the Details tab, configure the required policy configuration settings.
    • (Optional) In the Policy Name field, enter a new name for the policy or keep the default. Policy names must be unique.
    • (Optional) In the Policy Notes field, enter details such as creation date of the policy, and information on testing and deployment of the policy.

Configuring the Policy

  • In the Settings field, select the settings you want enabled for this policy.
    1. (Optional) Select the Always ON checkbox if you want to automatically connect to the VPN at sign-in. 
    2. (Optional) In the Profile Name field, enter a name for the VPN profile. 
    3. In the Profile Type field, select if the VPN profile is Native or a 3rd Party Plugin
      • For Native:
        1. In the Server name or address field, enter the VPN server details.
        2. Select the Connection Type
        3. In the Proxy field, define the proxy settings for the VPN profile.
      • For 3rd Party Plugin:
        1. Enter the Package Family Name.
        2. In the Server URL field, enter the server details.
        3. Enter Custom Configuration details.
        4. In the Proxy field, select the desired proxy option (None, Automatic, or Manual) to apply when the profile is active and connected.

Note:
  • For IKEV2 connection type, use the Install Certificate policy to ensure that the certificate is already available on the device.
  • For PPTP and L2TP connection types, the user will be prompted to enter a password.
  • For L2TP + Shared Key connection types, the admin must enter the password in the input field.

Applying the Policy

  • (Optional) Select the Policy Groups tab. Select one or more policy groups where you want to add this policy. 
  • Select the Device Groups tab. Select one or more device groups where you want to apply this policy to. For device groups with multiple OS member types, the policy only applies when a user logs into a supported Windows device that is enrolled in MDM.
  • Or, select the Devices tab. Select one or more devices where you want to apply this policy.
  • Click Create Policy. A success message is displayed indicating the completion of policy creation.

Note:

You must select either a device or device group to create and apply this policy.

Viewing Policy Status

  1. Select the Status tab.
  2. To see the last Result Log for a device where this policy is applied, click view.

Note:
  • If any errors occur, they're listed in Exit Status. If you have an Exit Status of 0, no errors occurred when applying or enforcing this policy.
Back to Top

Still Have Questions?

If you cannot find an answer to your question in our FAQ, you can always contact us.

Submit a Case