How To: Require managed devices for cloud app access with Conditional Access
In a mobile-first, cloud-first world, Azure Active Directory (Azure AD) enables single sign-on to apps, and services from anywhere. Authorized users can access your cloud apps from a broad range of devices including mobile and also personal devices. However, many environments have at least a few apps that should only be accessed by devices that meet your standards for security and compliance. These devices are also known as managed devices.
This article explains how you can configure Conditional Access policies that require managed devices to access certain cloud apps in your environment.
Requiring managed devices for cloud app access ties Azure AD Conditional Access and Azure AD device management together. If you are not familiar with one of these areas yet, you should read the following topics, first:
- Conditional Access in Azure Active Directory - This article provides you with a conceptual overview of Conditional Access and the related terminology.
- Introduction to device management in Azure Active Directory - This article gives you an overview of the various options you have to get devices under organizational control.
- For Chrome support in Windows 10 Creators Update (version 1703) or later, install the Windows 10 Accounts extension. This extension is required when a Conditional Access policy requires device-specific details.
We recommend using Azure AD device based Conditional Access policy to get the best enforcement after initial device authentication. This includes closing sessions if the device falls out of compliance and device code flow.
Mastering the balance between security and productivity is a challenge. The proliferation of supported devices to access your cloud resources helps to improve the productivity of your users. On the flip side, you probably don't want certain resources in your environment to be accessed by devices with an unknown protection level. For the affected resources, you should require that users can only access them using a managed device.
With Azure AD Conditional Access, you can address this requirement with a single policy that grants access:
- To selected cloud apps
- For selected users and groups
- Requiring a managed device
In simple terms, managed devices are devices that are under some sort of organizational control. In Azure AD, the prerequisite for a managed device is that it has been registered with Azure AD. Registering a device creates an identity for the device in form of a device object. This object is used by Azure to track status information about a device. As an Azure AD administrator, you can already use this object to toggle (enable/disable) the state of a device.
To get a device registered with Azure AD, you have three options:
- Azure AD registered devices - to get a personal device registered with Azure AD
- Azure AD joined devices - to get an organizational Windows 10 device that is not joined to an on-premises AD registered with Azure AD.
- Hybrid Azure AD joined devices - to get a Windows 10 or supported down-level device that is joined to an on-premises AD registered with Azure AD.
These three options are discussed in the article What is a device identity?
To become a managed device, a registered device must be either a Hybrid Azure AD joined device or a device that has been marked as compliant.
Require Hybrid Azure AD joined devices
In your Conditional Access policy, you can select Require Hybrid Azure AD joined device to state that the selected cloud apps can only be accessed using a managed device.
This setting only applies to Windows 10 or down-level devices such as Windows 7 or Windows 8 that are joined to an on-premises AD. You can only register these devices with Azure AD using a Hybrid Azure AD join, which is an automated process to get a Windows 10 device registered.
What makes a Hybrid Azure AD joined device a managed device? For devices that are joined to an on-premises AD, it is assumed that the control over these devices is enforced using management solutions such as Configuration Manager or group policy (GP) to manage them. Because there is no method for Azure AD to determine whether any of these methods has been applied to a device, requiring a hybrid Azure AD joined device is a relatively weak mechanism to require a managed device. It is up to you as an administrator to judge whether the methods that are applied to your on-premises domain-joined devices are strong enough to constitute a managed device if such a device is also a Hybrid Azure AD joined device.
Require device to be marked as compliant
The option to require a device to be marked as compliant is the strongest form to request a managed device.
This option requires a device to be registered with Azure AD, and also to be marked as compliant by:
- A third-party mobile device management (MDM) system that manages Windows 10 devices via Azure AD integration. Third-party MDM systems for device OS types other than Windows 10 are not supported.
For a device that is marked as compliant, you can assume that:
- The mobile devices your workforce uses to access company data are managed
- Mobile apps your workforce uses are managed
- Your company information is protected by helping to control the way your workforce accesses and shares it
- The device and its apps are compliant with company security requirements
Scenario: Require device enrollment for iOS and Android devices
In this scenario, Contoso has decided that all mobile access to Microsoft 365 resources must use an enrolled device. All of their users already sign in with Azure AD credentials and have licenses assigned to them that include Azure AD Premium P1 or P2 and Microsoft Intune.
Organizations must complete the following steps in order to require the use of an enrolled mobile device.
- Sign in to the Azure portal as a global administrator, security administrator, or Conditional Access administrator.
- Browse to Azure Active Directory > Security > Conditional Access.
- Select New policy.
- Give your policy a name. We recommend that organizations create a meaningful standard for the names of their policies.
- Under Assignments, select Users and groups
- Under Include, select All users or the specific Users and groups you wish to apply this policy to.
- Select Done.
- Under Cloud apps or actions > Include, select Office 365.
- Under Conditions, select Device platforms.
- Set Configure to Yes.
- Include Android and iOS.
- Under Access controls > Grant, select the following options:
- Require device to be marked as compliant
- Confirm your settings and set Enable policy to On.
- Select Create to create and enable your policy.
When using the device-code OAuth flow, the require managed device grant control or a device state condition are not supported. This is because the device performing authentication cannot provide its device state to the device providing a code and the device state in the token is locked to the device performing authentication. Use the require multi-factor authentication grant control instead.
On Windows 7, iOS, Android, macOS, and some third-party web browsers Azure AD identifies the device using a client certificate that is provisioned when the device is registered with Azure AD. When a user first signs in through the browser the user is prompted to select the certificate. The end user must select this certificate before they can continue to use the browser.