Skip to content

Ulysses Neves

Microsoft Entra ID, authentication, and hybrid identity troubleshooting.

Menu
  • Home
  • Microsoft Azure
  • Microsoft AD FS
  • Microsoft 365
  • Contact
  • Troubleshooting Index
Menu

Enhancing Azure role activation security with FIDO2/Passkeys

Posted on September 23, 2024

Configuring Entra Privileged Identity Management (PIM) with Conditional Access authentication context and Conditional Access authentication strength can significantly enhance your organization’s security posture. By requiring users to meet specific authentication requirements when activating roles in PIM, you can ensure that sensitive roles are only accessed under the most secure conditions.

Conditional Access authentication strength is a feature that allows you to define and enforce specific authentication methods, such as multifactor authentication (MFA) or passwordless authentication, based on the sensitivity of the roles being accessed. This ensures that only users who meet the highest security standards can activate privileged roles.

Benefits of integrating Conditional Access authentication strength with Entra PIM and Conditional Access authentication context include:

Enhanced Security: By requiring stronger authentication methods, such as phishing-resistant MFA or passwordless authentication, you reduce the risk of unauthorized access to sensitive roles.
Compliance: Enforcing specific authentication strengths helps meet regulatory and compliance requirements by ensuring that only authenticated and authorized users can access critical resources.
Improved User Experience: Users can benefit from a seamless and secure authentication process, reducing the need for frequent password changes and minimizing the risk of password-related security issues.
Granular Control: Administrators can create custom authentication strength policies tailored to the organization’s security needs, providing flexibility and control over access management.

This guide will walk you through the process of configuring Entra PIM activation using Conditional Access authentication context. We will cover each step in detail and indicate where you should place screenshots to aid in understanding.

Note: In this article, Passkeys will be used as the authentication strength method. If you want to use it, make sure you have enabled it in your tenant following this official Microsoft guide: Enable passkeys for your organization (preview) – Microsoft Entra ID | Microsoft Learn


Step 1: Set Up Authentication strength

  1. Access the Azure Portal
    Log into the Azure Portal with your administrative credentials.
  2. Navigate to Authentication strength
    Select Microsoft Entra ID, and then select Security. Expand Protect and select Conditional Access. In the Manage section, click on Authentication strengths.
  3. Click on New authentication strength.
  4. Enter a name and description for your authentication strength setting.
    • Select Passkeys (FIDO2).


  5. Click on Advanced options.
  6. Select Microsoft Authenticator (Preview)


  7. Click Save.
  8. Click Next and Update.

Step 2: Set Up Authentication Context

  1. Access the Azure Portal
    Log into the Azure Portal with your administrative credentials.
  2. Navigate to Authentication contexts
    Select Microsoft Entra ID, and then select Security. Expand Protect and select Conditional Access. In the Manage section, click on Authentication contexts.
  3. Click on New authentication context.
  4. Enter a name and description for your authentication context.
  5. Check the Publish to apps checkbox.
  6. Click Save.

Step 3: Set Up Conditional Access Policy for Authentication Context

  1. Access the Azure Portal
    Log into the Azure Portal with your administrative credentials.
  2. Navigate to Conditional Access
    Select Microsoft Entra ID, and then select Security. Expand Protect and select Conditional Access.
  3. Create a New Conditional Access Policy
    Select Create new policy at the top of the Conditional Access pane. Name your policy appropriately, e.g., “PIM Role Activation Context”.


  4. Assign Users and Groups
    In the Assignments section, choose Users and groups and specify the users or groups that the policy will apply to. This will generally be the users who will activate PIM roles. In my case, I’m setting this to All users. Please make sure you add at least one account in the exclusion list.


  5. Select Target resources
    In the Target resources section, choose Authentication Context, and add select the authentication context configuration created on step 1.

  6. Configure Conditions (Optional)
    You may configure additional conditions such as device compliance, location, etc., depending on your organization’s security requirements.


  7. Configure Access Controls
    Under Grant, choose Require authentication strength and select the authentication context you created in step 2. In my case, I’ve configured Phishing-resistant MFA methods.

    Note: Mandating strong authentication for PIM group membership allows the use of advanced methods like phishing-resistant MFA and Passwordless MFA, providing enhanced security compared to basic MFA methods like SMS.


  8. Enable the Policy
    Toggle Enable policy to On, then click Create to save the policy.

Step 4: Configure PIM to Use Conditional Access Authentication Context

  1. Navigate to Privileged Identity Management (PIM)
    From the Azure Portal, go to Microsoft Entra ID > Identity Governance > Privileged Identity Management.
  2. Select the Role to Configure
    Under Manage, select Microsoft Entra roles (or Azure resources if you’re configuring PIM for Azure resources). Then, select Roles to view all available roles.


  3. Choose a Role
    Click on the role you want to configure with the Conditional Access authentication context. I’m using Application Administrator, but you can choose any available role.



  4. Modify Role Settings
    In the role’s settings pane, click Edit. Select Microsoft Entra Conditional Access authentication context option and select the Authentication Context configured on step 2.

  5. Save the Changes
    Click Update to apply the changes to the role.

    Make sure you have users eligible to PIM role assigment. If you don’t, you can configure selecting Add Assignments below:


Step 3: Verify the Configuration

  1. Test Role Activation
    Sign in as a user who is eligible for the role. Try to activate the role to ensure that the Conditional Access authentication context is enforced. The user should be prompted to satisfy the authentication context (e.g., MFA) before the role is activated. During our test, we see conditional access policy requires additional verification because our test user didn’t sign in using passkeys:



    The user is prompted to authenticate using either a FIDO2 key or a Passkey:



    After completing the authentication using the passkey, the authentication is successful and the user is now able to activate the role using PIM:


  2. Monitor Logs and Alerts
    After testing, review the Microsoft Entra sign-in logs and Conditional Access insights to confirm that the policy was applied as expected. This step is crucial for validating that your security configurations are working correctly.

    With the sign in activities below, we confirm the policy PIM Role Activation Context has applied and the user has authenticated using a passkey:






Conclusion

Configuring Microsoft Entra PIM with Conditional Access authentication context and Conditional Access authentication strength features adds an extra layer of security to the role activation process, ensuring that sensitive actions are protected by rigorous authentication requirements. By following the steps outlined in this guide, you can effectively integrate these powerful security features into your organization’s identity management strategy.

Regularly review and update your Conditional Access policies and PIM settings to adapt to evolving security needs and ensure that your configurations remain aligned with best practices.

Did you find this article helpful? Consider showing your appreciation by liking and sharing it. 🙂

Disclaimer:  The views expressed in this post are personal and do not represent the opinions of my organization. The provided solution is offered “AS IS” without warranties or guarantees and should be validated in a test environment before deployment in production.

Your suggestions and feedback are invaluable; feel free to leave a comment.

[ ]’s Ulysses Neves

Related guides: Browse the Microsoft Identity Troubleshooting Index or the Microsoft Entra Conditional Access topic archive.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Microsoft Defender for Identity domain investigation: six questions to ask first September 10, 2026
  • Microsoft Entra Kerberos key rotation: what changes—and what administrators should check September 6, 2026
  • Microsoft Authenticator Will Block Jailbroken Devices in 2026 — What You Need to Know March 17, 2026
  • Enhancing Azure role activation security with FIDO2/Passkeys September 23, 2024
  • Microsoft Entra ID CAP | Enforcing WHfB using Authentication Strength April 21, 2024

Archives

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

Tags

#aaddownleveldevice #adfs #adfscertificate #adfscertificates #adfsmfaadapter #azureauth #azureCA #azuredevice #capolicy #cloudsummit2021 #conditionalaccess #conditionalaccesspolicy #deviceregistration #farmbehavior #gopasswordless #mfaserver #msidentity #namedlocation #securingazure #securingazuread #sslprivatekey #troubleshootingadfs #troubleshootingwaptrust #tshootadfs #waptrust #webapplicationproxy #WHFBcerttrust #whfbdeployment #WHfBhybridsetup #WHfBprovisioning #widdatabase adconnect AD FS authenticationstrength az500 azurepim Azure security cloudsecurity microsoft365 Microsoft Azure Microsoft Entra hybrid join Microsoft Entra ID Microsoft Entra MFA PowerShell WHfB
©2026 Ulysses Neves | Design: Newspaperly WordPress Theme
Ulysses Neves
Gerenciar Consentimento de Cookies
Para fornecer as melhores experiências, usamos tecnologias como cookies para armazenar e/ou acessar informações do dispositivo. O consentimento para essas tecnologias nos permitirá processar dados como comportamento de navegação ou IDs exclusivos neste site. Não consentir ou retirar o consentimento pode afetar negativamente certos recursos e funções.
Funcional Always active
O armazenamento ou acesso técnico é estritamente necessário para a finalidade legítima de permitir a utilização de um serviço específico explicitamente solicitado pelo assinante ou utilizador, ou com a finalidade exclusiva de efetuar a transmissão de uma comunicação através de uma rede de comunicações eletrónicas.
Preferências
O armazenamento ou acesso técnico é necessário para o propósito legítimo de armazenar preferências que não são solicitadas pelo assinante ou usuário.
Estatísticas
O armazenamento ou acesso técnico que é usado exclusivamente para fins estatísticos. O armazenamento técnico ou acesso que é usado exclusivamente para fins estatísticos anônimos. Sem uma intimação, conformidade voluntária por parte de seu provedor de serviços de Internet ou registros adicionais de terceiros, as informações armazenadas ou recuperadas apenas para esse fim geralmente não podem ser usadas para identificá-lo.
Marketing
O armazenamento ou acesso técnico é necessário para criar perfis de usuário para enviar publicidade ou para rastrear o usuário em um site ou em vários sites para fins de marketing semelhantes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
Ver preferências
  • {title}
  • {title}
  • {title}