maciejrebisz.com

IT

How to get started with Conditional Access – block access based on user risk – Mobile-First Cloud-First

maximios August 14, 2022

I started this blog post series with “How to get started with Conditional Access” and will continue with some use cases. This use cases can be combined or be implemented stand alone – it all depends what you are your organisation want to accomplish.

In this use case we just add a extra layer of security on top of Azure Active Directory  – by setting up a couple of Conditional Access rules blocking or requires MFA based on the user risk. This is a recommendation I have when I do EMS projects at customers – and it is a easy way to stop the bad guys from accessing your corporate data.
This feature is from Azure AD Identity Protection – that are combined with Conditional Access.

The layout is to block a user in high risk when:

  • Accessing all services integrated with Azure AD
  • From Mobile apps and desktop clients
  • Inside or Outside of the corporate network
  • On any devices

The layout is to require MFA on a user in medium risk when:

  • Accessing all services integrated with Azure AD
  • From Mobile apps and desktop clients
  • Inside or Outside of the corporate network
  • On any devices

Note: User risk based conditional access requires AzureAD P2

Start the Azure Active Directory admin center

  1. Click Azure Active Directory
  2. Click Conditional Access

  1. Enter a name that makes sense to you : “CA – Block All High Risk Users”
  2. Select Assignments
  3. Select All users

It is recommended to check if you have users in high risk before enabling this conditional access rules otherwise the user will be blocked at next login

  1. Select Cloud apps
  2. Select Selected apps
  3. Select All cloud apps

Important : Don’t lock yourself out! Please read and understand what you are doing so you don’t lock you out of the Azure Management Portal

  1. Select Conditions
  2. Select Sign-in risk
  3. Click Configure – Yes
  4. Select high

Note: If you don’t see the section with Sign-in risk you don’t have AzureAD P2 features in your tenant

  1. Select Access controls
  2. Select “Block Access”

Now the Conditional Access rule are created and will first take effect when you sets the Enable policy to On

  1. Enter a name that makes sense to you : “CA – MFA All Medium Risk Users”
  2. Select Assignments
  3. Select All users

It is recommended to check if you have users in high risk before enabling this conditional access rules otherwise the user will be blocked at next login

  1. Select Cloud apps
  2. Select Selected apps
  3. Select All cloud apps

Important : Don’t lock yourself out! Please read and understand what you are doing so you don’t lock you out of the Azure Management Portal

  1. Select Conditions
  2. Select Sign-in risk
  3. Click Configure – Yes
  4. Select high

Note: If you don’t see the section with Sign-in risk you don’t have AzureAD P2 features in your tenant

Note: Normally I create a require MFA  when the end user is outside the internal network – but in this case if the end user is getting in risk they will be prompted for MFA both on the inside or outside of the network

  1. Select Access controls
  2. Select “Require multi-factor authentication”

Now the Conditional Access rule are created and will first take effect when you sets the Enable policy to On.

When we look at the sign in logs from Azure AD and see how many users that are in risk.

Start the Azure Active Directory admin center https://aad.portal.azure.com

Click on Azure AD Identity Protection

Then you will get access to the overview with a graph of users in risk in your tenant

Read more:

What is Azure Active Directory Identity Protection?

Related Posts

IT /

Intune – Windows device enrollment restrictions – Cloud First

IT /

How to add “hidden” Windows UWP to Windows Store for Business – Cloud First

IT /

Office 2016 Active Directory-Based activation – Cloud First

‹ How to deploy OneDrive Known Folder Move with Intune – Mobile-First Cloud-First › How to deploy OneDrive Known Folder Move with Intune – Mobile-First Cloud-First

Recent Posts

  • Intune – Windows device enrollment restrictions – Cloud First
  • How to add “hidden” Windows UWP to Windows Store for Business – Cloud First
  • Office 2016 Active Directory-Based activation – Cloud First
  • How to deploy Windows Local Experience Packs with Intune – Cloud First
  • Conditional Access for Outlook Web Access (OWA) – Cloud First

Recent Comments

No comments to show.

Archives

  • November 2025
  • October 2025
  • August 2025
  • July 2025
  • June 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • November 2024
  • September 2024
  • July 2024
  • June 2024
  • March 2024
  • December 2023
  • August 2023
  • June 2023
  • March 2023
  • February 2023
  • December 2022
  • September 2022
  • August 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • January 2022
  • December 2021
  • October 2021
  • September 2021
  • August 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • February 2020
  • January 2020
  • December 2019
  • October 2019
  • September 2019
  • June 2019
  • April 2019
  • March 2019
  • February 2019
  • March 2018
  • February 2018
  • December 2017
  • October 2017
  • August 2017

Categories

  • IT

Back to Top

© maciejrebisz.com 2026
Powered by WordPress • Themify WordPress Themes