Intune Cisco Anyconnect

Posted on  by



  1. Announced by Brad Anderson today at Microsoft Ignite is new feature for Microsoft Intune which goes another step to both enhance and eliminate blockers towards using modern management with Microsoft Intune. Win32 Application Deployments The ability to “package” applications for deployment in Microsoft Intune is something that has been highly requested by many organisations making.
  2. Name your policies so you can easily identify them later. For example, a good policy name is App config policy: JSON Cisco AnyConnect VPN policy for Android Enterprise work profile devices in entire company. Description: Enter a description for the policy. This setting is optional, but recommended. Platform: Select Android Enterprise.
  3. AnyConnect Licenses enabled (APEX or VPN-Only). Components Used. The information in this document is based on these software and hardware versions: A Microsoft Azure AD subscription. Cisco ASA 9.7+ and Anyconnect 4.6+ Working AnyConnect VPN profile; The information in this document was created from the devices in a specific lab environment.
-->

Anybody have any luck pushing this through Intune? It gets stuck in the installing state and then eventually fails. This is currently the only.msi.

Intune integrates with network access control (NAC) partners to help organizations secure corporate data when devices try to access on-premises resources.

Important

NAC is not currently supported for Android Enterprise Fully Managed or Android Enterprise Dedicated devices.

Intune Cisco Anyconnect Vpn

How do Intune and NAC solutions help protect your organization resources?

NAC solutions check the device enrollment and compliance state with Intune to make access control decisions. If the device isn't enrolled, or is enrolled and not compliant with Intune device compliance policies, then the device should be redirected to Intune for enrollment, or for a device compliance check.

Example

If the device is enrolled and compliant with Intune, the NAC solution should allow the device access to corporate resources. For example, users can be allowed or denied access when trying to access corporate Wi-Fi or VPN resources.

Feature behaviors

Devices that are actively syncing to Intune can't move from Compliant / Noncompliant to Not Synched (or Unknown). The Unknown state is reserved for newly enrolled devices that haven't been evaluated for compliance yet.

For devices that are blocked from access to resources, the blocking service should redirect all users to the management portal to determine why the device is blocked. If the users visit this page, their devices are synchronously reevaluated for compliance.

Vpn

NAC and Conditional Access

NAC works with Conditional Access to provide access control decisions. For more information, see Common ways to use Conditional Access with Intune.

How the NAC integration works

Anyconnect

The following list is an overview on how NAC integration works when integrated with Intune. The first three steps, 1-3, explain the onboarding process. Once the NAC solution is integrated with Intune, steps 4-9 describe the ongoing operation.

  1. Register the NAC partner solution with Azure Active Directory (AAD), and grant delegated permissions to the Intune NAC API.
  2. Configure the NAC partner solution with the appropriate settings including the Intune discovery URL.
  3. Configure the NAC partner solution for certificate authentication.
  4. User connects to corporate Wi-Fi access point or makes a VPN connection request.
  5. NAC partner solution forwards the device information to Intune, and asks Intune about the device enrollment and compliance state.
  6. If the device isn't compliant or isn't enrolled, the NAC partner solution instructs the user to enroll or fix the device compliance.
  7. The device tries to reverify its compliance and enrollment state when applicable.
  8. Once the device is enrolled and compliant, NAC partner solution gets the state from Intune.
  9. Connection is successfully established which allows the device access to corporate resources.
Intune Cisco AnyconnectWith

Use NAC for VPN on your iOS/iPadOS devices

NAC is available on the following VPNs without enabling NAC in the VPN profile:

  • NAC for Cisco Legacy AnyConnect
  • F5 Access Legacy
  • Citrix VPN

NAC is also supported for Cisco AnyConnect, Citrix SSO, and F5 Access.

To enable NAC for Cisco AnyConnect for iOS

  • Integrate ISE with Intune for NAC as described in the link below.
  • Set the Enable Network Access Control (NAC) setting in the VPN profile to Yes.

To enable NAC for Citrix SSO

  • Use Citrix Gateway 12.0.59 or higher.
  • Users must have Citrix SSO 1.1.6 or later installed.
  • Integrate NetScaler with Intune for NAC as described in the Citrix product documentation.
  • In the VPN profile, select Base settings > Enable Network Access Control (NAC) > select I agree.

To enable NAC for F5 Access

  • Use F5 BIG-IP 13.1.1.5 or later.
  • Integrate BIG-IP with Intune for NAC. The Overview: Configuring APM for device posture checks with endpoint management systems F5 guide lists the steps.
  • In the VPN profile, select Base settings > Enable Network Access Control (NAC) > select I agree.

The VPN connection is disconnected every 24 hours for security reasons. The VPN can immediately be reconnected.

We're working with our partners to release a NAC solution for these newer clients. When solutions are ready, this article will be updated with additional information.

Intune Cisco Vpn

Next steps