Enabling Reauthentication with MFA during Intune enrollment

-

The default configuration for user sign-in frequency in Azure Active Directory is a rolling window of 90 days. But there are scenarios where organizations may require a fresh authentication every time a user performs specific actions. Based on customer feedback, Microsoft have introduced Sign-in frequency option Every time in addition to existing periodic frequency of hours and days. With this new capability, organization can now re-verify identity, device, and any other Conditional Access conditions for high-risk scenarios like -
  • User risk 
  • Session risk 
  • Microsoft Intune device enrollment 
I wanted to test this new feature for Intune enrollment and shall be covering my experience in this blog. Let's get started.

2. Select Endpoint Security > Conditional Access > New Policy.
3. Provide a Name.
4. Under Users and groups, choose Specific users included and select the users or groups that you want to target.


5. Under Cloud apps, select the apps against which corporate data is to be protected. In this case, I am selecting Microsoft Intune Enrollment.


6. Under Grant, select Grant access as Require multifactor authentication.


7. Select Sign-in frequency as Every time.


8. Select Create to finish creating the policy. Note: It is recommended to test the policy in Report-only mode first before enabling it. 

End Result

The targeted user against the CA policy, will now be required to reauthenticate when enrolling their device into Microsoft Intune if they haven’t done so within the last five minutes. 


The sign-in can be verified in the Azure sign-in logs to check whether the correct CA policy has been enforced or not.




Conclusion

Previously sign-in frequency only applied to the first factor authentication on devices that were Azure AD joined, Hybrid Azure AD joined, and Azure AD registered. There was no easy way for organizations to re-enforce multifactor authentication (MFA) on those devices, until now. This new public preview capability not only allows organizations to improve their security posture for high-risk scenarios, but also the overall experience for password-less end-users.

At the time of writing this blog, the public preview supports the following scenarios:
  • Require user reauthentication during Intune device enrollment, regardless of their current MFA status.
  • Require user reauthentication for risky users with the require password change grant control.
  • Require user reauthentication for risky sign-ins with the require multifactor authentication grant control.
To know more about risky users and sign-ins, please refer to my earlier post on 'Using Conditional Access to enable Azure Active Directory Identity Protection risk polices'

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