Android Enterprise device settings to configure VPN in Intune

This article describes the different VPN connection settings you can control on Android Enterprise devices. As part of your mobile device management (MDM) solution, use these settings to create a VPN connection, choose how the VPN authenticates, select a VPN server type, and more.

This feature applies to:

  • Android Enterprise personally owned devices with a work profile (BYOD)
  • Android Enterprise corporate-owned work profile (COPE)
  • Android Enterprise corporate owned fully managed (COBO)
  • Android Enterprise corporate owned dedicated devices (COSU)

As an Intune administrator, you can create and assign VPN settings to Android Enterprise devices. To learn more about VPN profiles in Intune, see VPN profiles.

Note

To configure always-on VPN, you need to create a VPN profile, and also create a device restrictions profile with the Always-on VPN setting configured.

Before you begin

Fully Managed, Dedicated, and Corporate-Owned Work Profile

  • Connection type: Select the VPN connection type. Your options:

    • Cisco AnyConnect
    • SonicWall Mobile Connect
    • F5 Access
    • Pulse Secure
    • Microsoft Tunnel (Not supported on Android Enterprise dedicated devices.)

The available settings depend on the VPN client you choose. Some settings are only available for specific VPN clients.

Base VPN (fully managed, dedicated, and corporate-owned work profile)

  • Connection name: Enter a name for this connection. End users see this name when they browse their device for the available VPN connections. For example, enter Contoso VPN.

  • VPN server address or FQDN: Enter the IP address or fully qualified domain name (FQDN) of the VPN server that devices connect. For example, enter 192.168.1.1 or vpn.contoso.com.

  • Authentication method: Choose how devices authenticate to the VPN server. Your options:

    • Certificates: Select an existing SCEP or PKCS certificate profile to authenticate the connection. Configure certificates lists the steps to create a certificate profile.

    • Username and password: When end users sign into the VPN server, they're prompted to enter their user name and password.

    • Derived credential: Use a certificate that's derived from a user's smart card. If no derived credential issuer is configured, Intune prompts you to add one.

      For more information, see Use derived credentials in Intune.

  • Enter key and value pairs for the NetMotion Mobility VPN attributes: Add or import Keys and Values that customize your VPN connection. These values are typically supplied by your VPN provider.

  • Microsoft Tunnel site (Microsoft Tunnel only): Select an existing site. The VPN client connects to the public IP address or FQDN of this site.

    For more information, see Microsoft Tunnel for Intune.

Per-app VPN (fully managed, dedicated, and corporate-owned work profile)

  • Add: Select managed apps from the list. When users start the apps you add, traffic automatically routes through the VPN connection.

For more information, see Use a VPN and per-app VPN policy on Android Enterprise devices.

Always-on VPN (fully managed, dedicated, and corporate-owned work profile)

  • Always-on VPN: Enable turns on always-on VPN so VPN clients automatically connect and reconnect to the VPN when possible. When set to Not configured, Intune doesn't change or update this setting. By default, always-on VPN might be disabled for all VPN clients.

    Only one VPN client can be configured for always-on VPN on a device. Be sure to have no more than one always-on VPN policy deployed to a single device.

Proxy (fully managed, dedicated, and corporate-owned work profile)

  • Automatic configuration script: Use a file to configure the proxy server. Enter the proxy server URL that includes the configuration file. For example, enter http://proxy.contoso.com/pac.
  • Address: Enter the IP address or fully qualified host name of the proxy server. For example, enter 10.0.0.3 or vpn.contoso.com.
  • Port number: Enter the port number associated with the proxy server. For example, enter 8080.

Personally owned work profile

  • Connection type: Select the VPN connection type. Your options:

    • Check Point Capsule VPN

    • Cisco AnyConnect

      Note

      With Cisco AnyConnect in the personally owned work profile, there may be some extra steps for end users to complete the VPN connection. For more information, go to VPN profiles - What successful VPN profiles look like.

    • SonicWall Mobile Connect

    • F5 Access

    • Pulse Secure

    • NetMotion Mobility

    • Microsoft Tunnel

The available settings depend on the VPN client you choose. Some settings are only available for specific VPN clients.

Base VPN (personally owned work profile)

  • Connection name: Enter a name for this connection. End users see this name when they browse their device for the available VPN connections. For example, enter Contoso VPN.

  • VPN server address: Enter the IP address or fully qualified domain name (FQDN) of the VPN server that devices connect. For example, enter 192.168.1.1 or vpn.contoso.com.

  • Authentication method: Choose how devices authenticate to the VPN server. Your options:

    • Certificates: Select an existing SCEP or PKCS certificate profile to authenticate the connection. Configure certificates lists the steps to create a certificate profile.

    • Username and password: When end users sign into the VPN server, they're prompted to enter their user name and password.

    • Derived credential: Use a certificate that's derived from a user's smart card. If no derived credential issuer is configured, Intune prompts you to add one.

      For more information, see Use derived credentials in Intune.

  • Fingerprint (Check Point Capsule VPN only): Enter the fingerprint string given to you by the VPN vendor, such as Contoso Fingerprint Code. This fingerprint verifies that the VPN server can be trusted.

    When authenticating, a fingerprint is sent to the client so the client knows to trust any server that has the same fingerprint. If the device doesn't have the fingerprint, it prompts the user to trust the VPN server while showing the fingerprint. The user manually verifies the fingerprint, and chooses to trust to connect.

  • Enter key and value pairs for the NetMotion Mobility VPN attributes: Add or import Keys and Values that customize your VPN connection. These values are typically supplied by your VPN provider.

  • Microsoft Tunnel site (Microsoft Tunnel only): Select an existing site. The VPN client connects to the public IP address or FQDN of this site.

    For more information, see Microsoft Tunnel for Intune.

Per-app VPN (personally owned work profile)

  • Add: Select managed apps from the list. When users start the apps you add, traffic automatically routes through the VPN connection.

For more information, see Use a VPN and per-app VPN policy on Android Enterprise devices.

Always-on VPN (personally owned work profile)

  • Always-on VPN: Enable turns on always-on VPN so VPN clients automatically connect and reconnect to the VPN when possible. When set to Not configured, Intune doesn't change or update this setting. By default, always-on VPN might be disabled for all VPN clients.

    Only one VPN client can be configured for always-on VPN on a device. Be sure to have no more than one always-on VPN policy deployed to a single device.

Proxy (personally owned work profile)

  • Automatic configuration script: Use a file to configure the proxy server. Enter the proxy server URL that includes the configuration file. For example, enter http://proxy.contoso.com/pac.
  • Address: Enter the IP address or fully qualified host name of the proxy server. For example, enter 10.0.0.3 or vpn.contoso.com.
  • Port number: Enter the port number associated with the proxy server. For example, enter 8080.

Next steps

Assign the profile and monitor its status.

You can also create VPN profiles for Android device administrator, iOS/iPadOS, macOS, and Windows 10 and later.

Troubleshooting VPN profile issues in Microsoft Intune