Pulse Secure Support helps you maintain your Secure Access deployment and provides rapid response for issue resolution. Our support centers are conveniently located in APAC, EMEA, and North America to provide local language support to customers and partners globally.
-->You can add and configure VPN connections for devices using Microsoft Intune. This article lists and describes commonly used settings and features when creating virtual private networks (VPNs). These VPN settings and features are used in device configuration profiles in Intune that are pushed or deployed to devices.
As part of your mobile device management (MDM) solution, use these settings to allow or disable features, including using a VPN vendor, enabling always on, using DNS, adding a proxy, and more.
These settings apply to devices running:
Depending on the settings you choose, not all values may be configurable.
Create a VPN device configuration profile.
Connection name: Enter a name for this connection. End users see this name when they browse their device for the list of available VPN connections.
Servers: Add one or more VPN servers that devices connect to. When you add a server, you enter the following information:
Register IP addresses with internal DNS: Select Enable to configure the Windows 10 VPN profile to dynamically register the IP addresses assigned to the VPN interface with the internal DNS. Select Disable to not dynamically register the IP addresses.
Connection type: Select the VPN connection type from the following list of vendors:
When you choose a VPN connection type, you may also be asked for the following settings:
Always On: Enable automatically connects to the VPN connection when the following events happen:
Authentication method: Select how you want users to authenticate to the VPN server. Using certificates provides enhanced features, such as zero-touch experience, on-demand VPN, and per-app VPN.
Remember credentials at each logon: Choose to cache the authentication credentials.
Custom XML: Enter any custom XML commands that configure the VPN connection.
EAP Xml: Enter any EAP XML commands that configure the VPN connection
Login group or domain: This property can't be set in the VPN profile. Instead, Mobile Connect parses this value when the user name and domain are entered in the username@domain
or DOMAINusername
formats.
Example:
For more information about writing custom XML commands, see each manufacturer's VPN documentation.
For more information about creating custom EAP XML, see EAP configuration.
Associate WIP or apps with this VPN: Enable this setting if you only want some apps to use the VPN connection. Your options:
Important
We recommend that you secure all app lists created for per-app VPNs. If an unauthorized user changes this list, and you import it into the per-app VPN app list, then you potentially authorize VPN access to apps that shouldn't have access. One way you can secure app lists is using an access control list (ACL).
Network traffic rules for this VPN connection: Select the protocols, and the local & remote port and address ranges, are enabled for the VPN connection. If you don't create a network traffic rule, then all protocols, ports, and address ranges are enabled. After you create a rule, the VPN connection uses only the protocols, ports, and address ranges that you enter in that rule.
Conditional Access for this VPN connection: Enables device compliance flow from the client. When enabled, the VPN client communicates with Azure Active Directory (AD) to get a certificate to use for authentication. The VPN should be set up to use certificate authentication, and the VPN server must trust the server returned by Azure AD.
Single sign-on (SSO) with alternate certificate: For device compliance, use a certificate different from the VPN authentication certificate for Kerberos authentication. Enter the certificate with the following settings:
DNS suffix search list: In DNS suffixes, enter a DNS suffix, and Add. You can add many suffixes.
When using DNS suffixes, you can search for a network resource using its short name, instead of the fully qualified domain name (FQDN). When searching using the short name, the suffix is automatically determined by the DNS server. For example, utah.contoso.com
is in the DNS suffix list. You ping DEV-comp
. In this scenario, it resolves to DEV-comp.utah.contoso.com
.
DNS suffixes are resolved in the order listed, and the order can be changed. For example, colorado.contoso.com
and utah.contoso.com
are in the DNS suffix list, and both have a resource called DEV-comp
. Since colorado.contoso.com
is first in the list, it resolves as DEV-comp.colorado.contoso.com
.
To change the order, click the dots to the left of the DNS suffix, and then drag the suffix to the top:
Kmplayer for mac os yosemite. Name Resolution Policy table (NRPT) rules: Name Resolution Policy table (NRPT) rules define how DNS resolves names when connected to the VPN. After the VPN connection is established, you choose which DNS servers the VPN connection uses.
You can add rules to the table that include the domain, DNS server, proxy, and other details to resolve the domain you enter. The VPN connection uses these rules when users connect to the domains you enter.
Select Add to add a new rule. For each server, enter:
contoso.com
or .allcontososubdomains.com
.10.0.0.3
or vpn.contoso.com
.http://proxy.com
.contoso.com
. When Not configured (default), the device doesn't automatically connect to the VPNhttp://proxy.contoso.com
, that includes the configuration file.vpn.contoso.com
Trusted network DNS suffixes: When users are already connected to a trusted network, you can prevent devices from automatically connecting to other VPN connections.
In DNS suffixes, enter a DNS suffix that you want to trust, such as contoso.com, and select Add. You can add as many suffixes as you want.
If a user is connected to a DNS suffix in the list, then the user won't automatically connect to another VPN connection. The user continues to use the trusted list of DNS suffixes you enter. The trusted network is still used, even if any autotriggers are set.
For example, if the user is already connected to a trusted DNS suffix, then the following autotriggers are ignored. Specifically, the DNS suffixes in the list cancel all other connection autotriggers, including:
The profile is created, but it's not doing anything yet. Next, assign the profile, and monitor its status.
Configure VPN settings on Android, iOS/iPadOS, and macOS devices.