Conditional Access: Restricting Office 365 access to Managed Devices only

-

A lot has been said about enforcing CA for Exchange Online and there are several scenarios that can play out. One such scenario is restricting access of not just Exchange Online, but the complete Office 365 to managed devices only. In this blog, I am going to cover my experience of creating the CA policy.

Configuration

The policy requirements that I have taken into consideration are –

  1. Office 365
  2. Device Platform (iOS & Android)
  3. Enforced across Browser & Mobile apps
  4. Require MFA
  5. Require Devices to be marked as compliant
  6. Require approved client app

Let’s begin.

1. Open the endpoint.microsoft.com and navigate to Devices-> Conditional Access | Policies->New policy.

2. Give a name and select the Users & groups. (Since the policy will result in restrictive experience by limiting the access to corporate data, it is advisable to test it against a selected group of users. For testing, I have just added myself, but it is recommended to use a test account instead.)

3. In the section Cloud apps or actions, when you add Office 365 Exchange Online, you will see a message stating that Exchange Online is part of Office 365 and you should select Office 365 app instead. This is because Office 365 includes Exchange Online as a child app among many others which is why it is advisable to add Office 365 instead of Exchange Online separately.

According to Microsoft

"The Office 365 app makes it possible to target these services all at once. We recommend using the new Office 365 app, instead of targeting individual cloud apps to avoid issues with service dependencies. Targeting this group of applications helps to avoid issues that may arise due to inconsistent policies and dependencies.

Administrators can choose to exclude specific apps from policy if they wish by including the Office 365 app and excluding the specific apps of their choice in policy."


4.      In the Conditions section, under Device platforms, I selected Android & iOS keeping in line with the requirements.

 


5.  In the Conditions section, under Client apps, I selected all the options. This is because I want to restrict access to corporate resources over a browser in case a user tries to access Office.com and the web apps within it. Also, I want to restrict access against mobile office apps (especially Outlook) and third-party email apps.




6.  Moving on to Access Controls, under Grant, I selected the following.

 


 

This will ensure that access to the Office 365 cloud apps will only be granted when a user has successfully completed MFA challenge, has a device enrolled and compliant and is using an approved app. 

In case you want to refer to the list of approved apps, then you can check the link here.

7. Last but not the least, you get the option to Enable Policy where I chose to switch it On. You can also only select Report-only incase you are in process of testing and validation. The action will get logged in sign-in data. More on that later..



End User Experience

When a user tries to access Outlook from an unmanaged device using a browser, the action will be blocked and the user will be presented with the following screen and the option to enroll their device.

When a user tries to access Outlook from an unmanaged device using a Outlook app, the action will be blocked and the user will be presented with the following screen and the option to enroll the device.

Admin experience

As an administrator, one can monitor the application of the CA policies through Sign-in data in Azure AD.

Here are some snippets.

When the user tries to access corporate resources from an un-managed device, you should see this reflecting in the sign-in data.

 

Under Conditional Access, you will be able to see which all CA policies got applied.

                                        

 You can click on Show details against the CA policy to get more details.






Similarly, you should see the sign-in data when a user accesses the corporate resource from a managed device.




Conclusion

CA is a great way of enforcing access restrictions against corporate resources. There are some caveats that one needs to be mindful of when implementing policies for Exchange online, especially when a device needs to be managed and compliant. Please note that if a device is not compliant, the CA policy will not grant control and access will be blocked to the cloud apps added in the policy (Office 365 in this case as covered in this blog).

I hope the process defined in this blog will help the reader to understand and implement the various aspects of the CA policies involving Exchange online against managed device. Happy securing!

Comments

Post a Comment

Popular posts from this blog

How to force escrowing of BitLocker recovery keys using Intune

-
Image
Every now and then it so happens that BitLocker recovery keys do not escrow in AAD. The usual culprits are incorrect BitLocker policies and\or the device hardware configuration failing to meet the minimum requirements. The other scenario and something I recently experienced is when everything is setup right and still the recovery key doesn’t escrow in AAD. As I understand, this can happen if the escrow process got interrupted the first time due to network or local devices related issues and the process could not resume. To circumvent this issue, one can simply push a PowerShell script to the devices to force the escrow of the recovery keys to AAD. Here is a script to do so. try{ $BitlockerVol = Get-BitLockerVolume -MountPoint $env:SystemDrive         $KPID=""         foreach($KP in $BitlockerVol.KeyProtector){             if($KP.KeyProtectorType -eq "RecoveryPassword"){              ...
Read more

Prevent users from running certain programs or applications on Windows endpoints using Intune

-
Image
  When it comes to blocking or preventing users from running an application on Windows devices, one normally uses App locker policy, Windows Defender Application Control and not so new but pretty useful method called Defender Vulnerability management within Microsoft 365 Defender Portal. A recent question on the Tech Community Microsoft forum prompted me to look for all possible alternatives. I started reminiscing over the legacy GPO policies and that is when I stumbled upon the policy  Don’t run specified Windows applications  located under User Administrative Templates - The policy setting does come with its own caveat - " This policy setting only prevents users from running programs that are started by the File Explorer process. It does not prevent users from running programs, such as Task Manager, which are started by the system process or by other processes. Also, if users have access to the command prompt (Cmd.exe), this policy setting does not prevent them from st...
Read more

Intune: Configure Printers for Non-Administrative Users

-
Image
Configuring printers for end users or giving them the ability to do it themselves is a normal requirement for organizations. Now if your users are Administrators, then the configuration can be straight forward, but in case of Non-Administrators there are additional steps required as Non-Administrators will not be able to add a driver in the driver store despite being able to install a printer. In this blog, I will cover the steps that I took to address this requirement using Intune. The setup involves 2 steps -  1. Setup registries. 2. Install the driver and configure the printer Setting up registries – The registries that need to be configured are actually part of a GPO setting – Allow non-administrators to install drivers for these device setup classes It can be found under: Computer Configuration -> Policies -> Administrative Templates -> System -> Driver Installation I used a Powershell script to set the values and wrapped it in a Win32 application. $P...
Read more