What are common ways to use Conditional Access with Intune?
There are two types of conditional access with Intune: device-based conditional access and app-based conditional access. You need to configure the related compliance policies to drive conditional access compliance at your organization. Conditional access is commonly used to do things like allow or block access to Exchange, control access to the network, or integrate with a Mobile Threat Defense solution.
The information in this article can help you understand how to use the Intune mobile device compliance capabilities and the Intune mobile application management (MAM) capabilities.
Conditional Access is an Azure Active Directory capability that is included with an Azure Active Directory Premium license. Intune enhances this capability by adding mobile device compliance and mobile app management to the solution. The Conditional Access node accessed from Intune is the same node as accessed from Azure AD.
Device-based Conditional Access
Intune and Azure Active Directory work together to make sure only managed and compliant devices can access email, Microsoft 365 services, Software as a service (SaaS) apps, and on-premises apps. Additionally, you can set a policy in Azure Active Directory to only enable domain-joined computers or mobile devices that are enrolled in Intune to access Microsoft 365 services.
Intune provides device compliance policy capabilities that evaluate the compliance status of the devices. The compliance status is reported to Azure Active Directory that uses it to enforce the Conditional Access policy created in Azure Active Directory when the user tries to access company resources.
Device-based Conditional Access policies for Exchange online and other Microsoft 365 products are configured through the Microsoft Endpoint Manager admin center.
Learn more about Intune device compliance.
Learn more about Supported browsers with Conditional Access in Azure Active Directory.
When you enable Device Based Access for content that users access from browser apps on their Android personally-owned work profile devices, users that enrolled before January 2021 must enable browser access as follows:
- Launch the Company Portal app.
- Go to the Settings page from the menu.
- In the Enable Browser Access section, tap the ENABLE button.
- Close and then restart the browser app.
This enables access in browser apps, but not to browser WebViews that open within apps.
Applications available in Conditional Access for controlling Microsoft Intune
When you are configuring conditional access in the Azure Active Directory portal, you have two applications available:
- Microsoft Intune - This application controls access to the Microsoft Endpoint Manager console and data sources. Configure grants/controls on this application when you want to target the Microsoft Endpoint Manager console and data sources.
- Microsoft Intune Enrollment - This application controls the enrollment workflow. Configure grants/controls on this application when you want to target the enrollment process. For more information see Require multi-factor authentication for Intune device enrollments.
Conditional access based on network access control
Intune integrates with partners like Cisco ISE, Aruba Clear Pass, and Citrix NetScaler to provide access controls based on the Intune enrollment and the device compliance state.
Users can be allowed or denied access to corporate Wi-Fi or VPN resources based on whether the device they're using is managed and compliant with Intune device compliance policies.
- Learn more about the NAC integration with Intune.
Conditional access based on device risk
Intune partners with Mobile Threat Defense vendors that provide a security solution to detect malware, Trojans, and other threats on mobile devices.
How the Intune and Mobile Threat Defense integration works
When mobile devices have the Mobile Threat Defense agent installed, the agent sends compliance state messages back to Intune reporting when a threat is found on the mobile device itself.
The Intune and mobile threat defense integration plays a factor in the conditional access decisions based on device risk.
- Learn more about Intune mobile threat defense.
Conditional access for Windows PCs
Conditional access for PCs provides capabilities similar to those available for mobile devices. Let's talk about the ways you can use conditional access when managing PCs with Intune.
Hybrid Azure AD joined: This option is commonly used by organizations that are reasonably comfortable with how they're already managing their PCs through AD group policies or Configuration Manager.
Azure AD domain joined and Intune management: This scenario is for organizations that want to be cloud-first (that is, primarily use cloud services, with a goal to reduce use of an on-premises infrastructure) or cloud-only (no on-premises infrastructure). Azure AD Join works well in a hybrid environment, enabling access to both cloud and on-premises apps and resources. The device joins to the Azure AD and gets enrolled to Intune, which can be used as a conditional access criteria when accessing corporate resources.
Bring your own device (BYOD)
- Workplace join and Intune management: Here the user can join their personal devices to access corporate resources and services. You can use Workplace join and enroll devices into Intune MDM to receive device-level policies, which are another option to evaluate conditional access criteria.
Learn more about Device Management in Azure Active Directory.
App-based conditional access
Intune and Azure Active Directory work together to make sure only managed apps can access corporate e-mail or other Microsoft 365 services.
- Learn more about app-based conditional access with Intune.
Intune Conditional access for Exchange on-premises
Conditional access can be used to allow or block access to Exchange on-premises based on the device compliance policies and enrollment state. When conditional access is used in combination with a device compliance policy, only compliant devices are allowed access to Exchange on-premises.
You can configure advanced settings in conditional access for more granular control such as:
Allow or block certain platforms.
Immediately block devices that aren't managed by Intune.
Any device used to access Exchange on-premises is checked for compliance when device compliance and conditional access policies are applied.
When devices don't meet the conditions set, the end user is guided through the process of enrolling the device to fix the issue that is making the device noncompliant.
Beginning in July of 2020, support for the Exchange connector is deprecated, and replaced by Exchange hybrid modern authentication (HMA). Use of HMA does not require Intune to setup and use the Exchange Connector. With this change, the UI to configure and manage the Exchange Connector for Intune has been removed from the Microsoft Endpoint Manager admin center, unless you already use an Exchange connector with your subscription.
If you have an Exchange Connector set up in your environment, your Intune tenant remains supported for its use, and you’ll continue to have access to UI that supports its configuration. See Install Exchange on-premises connector for more information. You can continue to use the connector or configure HMA and then uninstall your connector.
Hybrid Modern Authentication provides functionality that was previously provided by the Exchange Connector for Intune: Mapping of a device identity to its Exchange record. This mapping now happens outside of a configuration you make in Intune or the requirement of the Intune connector to bridge Intune and Exchange. With HMA, the requirement to use the ‘Intune' specific configuration (the connector) has been removed.
What's the Intune role?
Intune evaluates and manages the device state.
What's the Exchange server role?
Exchange server provides API and infrastructure to move devices to quarantine.
Keep in mind that the user who's using the device must have a compliance profile and Intune license assigned to them so the device can be evaluated for compliance. If no compliance policy is deployed to the user, the device is treated as compliant and no access restrictions are applied.