Maintaining governance over where company data is stored and how it is used, is a core priority for many IT professionals. In this mobile first world, with each user on average having 3+ devices and each with company data on them, ensuring that data is well protected can be a challenge. Giving users a choice of what device they want to use and how they want to use it to execute their job can be empowering – but we must protect the data that lives on those devices. This means ensuring that only compliant/approved devices, (and compliant/approved apps), can access that data. If that data were to be compromised (leaked, lost,stolen,etc) that could be devastating to an organization and place individual employees at risk.
A classic example is when an employee has a smartphone and would like to receive their company email on it. If they go to configure the built-in mail app with their email, how can you require the device to be enrolled into an MDM to be protected and require they use an approved email app? Well, Microsoft Intune and Azure Active Directory Conditional Access to the rescue! In this blog, you and I will take a journey on how to setup and configure this exact scenario and then test it to see what the end-user experience will look like.
I’m not going to cover Microsoft Intune or Azure AD Conditional Access in full technical detail. Please refer to the product documentation (links above) for more information.
Let’s start with understanding Conditional Access. At a high level, this allows me (IT) to provide you (the end user) with access to corporate resources based on a set of conditions and if you meet those conditions I’ll let you in. If you don’t meet those conditions, or perhaps meet only one or two, I will have additional steps for you to take before I unlock the front door and invite you in for dinner. You can best think of Conditional Access as an “If/Then” statement. For example, if you are coming from a device that is un-managed (and using an un-approved application), then allow access but require you to enroll the device in MDM (i.e. managed) and download the approved application for accessing email. Here’s a good graphical representation on how to think about this, at a high level (as you can see, this can be very powerful!):
Now that we have an understanding of Conditional Access, let’s configure it for this scenario. I’m going to create a new Conditional Access policy in Azure Active Directory from within the Azure portal:
Next I will scope it to all users:
Next, for Cloud Apps I will chose Office 365 Exchange Online:
Next, for Conditions I will choose device platforms and select all platforms:
For Grant I will choose grant access and check the box for require device to be marked as compliant and require approved client app. I’ll also check the radio button so that all controls are required. (For more information about what are approved client apps see this article).
Next I’ll enable the policy and click create:
I now need to configure the device compliance for Intune. I’m going to navigate to Device Compliance in the Intune blade:
I’m going to create a new policy that is targeted at just iOS:
IMPORTANT: If there’s other platforms you need to accommodate, you’ll need to create a new policy for each platform type (i.e. Windows, Mac, Android, etc).
For fun, block jail broken devices under device health:
And for more fun, require a passcode under system security:
Now the compliance policy has been created, I am going to assign it to all users:
Okay, let’s take a look at what the user experience is like for this scenario.
Let’s launch the native mail app on an iPad (iOS device):
Sign in with my corporate credentials:
Tap sign in:
When my company’s login page appears to finish the sign in process, enter my password:
What do we have here? …. Looks like Conditional Access kicked in! My device is not managed! But it does give me an option to Enroll!
IMPORTANT: To see the enrollment process, reference my other blog article Intune: MDM Enrollment Experience (complete device management)
Once the device is enrolled, with my policy it is also pulling down the Outlook app (well, the user is prompted to install it). When I launch the Outlook app….
Tap get started, and there’s my email profile!
NOTE: This does not require any configuration for the email profile to be automatically displayed.
And there’s my email!
Now what if I go back to the native mail app and try to use it? Well following the same process above where I type in my credentials and try to sign in again to the native mail app – Conditional Access will catch me red handed, and block me from using it:
Conclusion: As you can see, this is a very powerful feature and introduces automation into your device security strategy. Enjoy!