Microsoft Entra ID Protection
Conditional Access

Risk-based access policies

In brief

The documentation now describes the Require Identity Verification control (preview) for Conditional Access policies using User risk or Sign-in risk conditions. It explains the required identity verification profile, supported credentials, and risk remediation outcomes.

What Entra admins need to know

Administrators adopting this control need an eligible identity verification profile and supported credential type. Successful verification remediates the applicable risk; failed verification does not.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Risk-based access policies

Risk-based access control policies can be applied to protect organizations when a sign-in or user is detected to be at risk.

Diagram of user, location, device, application, and risk signals informing Conditional Access decisions, including requiring identity verification.

Microsoft Entra Conditional Access offers two user-specific risk conditions powered by Microsoft Entra ID Protection signals: Sign-in risk and User risk. Organizations can create risk-based Conditional Access policies by configuring these two risk conditions and choosing an access control method. During each sign-in, ID Protection sends the detected risk levels to Conditional Access, and the risk-based policies apply if the policy conditions are satisfied.

  1. Require risk remediation: ID Protection manages the appropriate remediation flow for all authentication methods.
  2. Require password change: ID Protection blocks access until user completes a secure password change.
  3. Block access: ID Protection blocks the user until risk is addressed.
  4. Require Identity Verification (preview): Users complete identity verification to remediate risk in supported scenarios.

Policies requiring either #1 or #2 forces end users to remediate their user risk and unblock themselves.

  • AppId: Public cloud = 93625bc8-bfe2-437a-97e0-3d0060024faa, Azure for US Government = 00001111-aaaa-2222-bbbb-3333cccc4444
  • ResourceId: 00000003-0000-0000-c000-000000000000

Identity verification for risk

The Require Identity Verification (preview) grant control lets users remediate risk by verifying their identity in supported scenarios. Use this control in a Conditional Access policy with a User risk or Sign-in risk condition to require identity verification when the detected risk matches the policy. Create separate policies for the two risk conditions.

An eligible identity verification profile is a prerequisite for a policy that uses this grant control to work. Before configuring the policy, create and configure an identity verification profile with Profile purpose set to All or Verification and a provider and credential type that support your risk scenario. For tenant-issued credentials, select Verification. Don't use an Onboarding- or Recovery-purpose profile for the risk-based resource-access policy.

  • Policy configuration: Select an identity verification profile and credential type that support the risk scenario, and apply the identity verification grant control to your risk-based policy.
  • User experience: When the policy applies, the user completes the required identity verification challenge. Microsoft Entra ID Protection can use the successful verification result to remediate the applicable risk.
  • Remediation outcome: Review the verification result, access decision, and relevant risk record separately to confirm the outcome for the scenario.

Successful identity verification remediates user risk when the triggering policy uses a User risk condition, or sign-in risk when it uses a Sign-in risk condition. Failed verification doesn't remediate risk.

Follow the existing guidance to configure identity verification for risk, complete the verification journey, and validate the remediation outcome. Review the risk targeted by the triggering policy; don't infer that every risk was cleared.

For licensing specific to this integration, see identity verification licensing.

:::image type="content" source="../identity/conditional-access/media/policy-require-identity-verification/require-identity-verification-grant-control.png" alt-text="Screenshot of the Conditional Access Grant pane with Grant access selected and Require identity verification checked." lightbox="../identity/conditional-access/media/policy-require-identity-verification/require-identity-verification-grant-control.png":::

Sign-in risk-based Conditional Access policy

During each sign-in, ID Protection analyzes hundreds of signals in real-time and calculates a sign-in risk level that represents the probability that the given authentication request isn't authorized. This risk level then gets sent to Conditional Access, where the organization's configured policies are evaluated. Administrators can configure sign-in risk-based Conditional Access policies to enforce access controls based on sign-in risk, including requirements such as:

  • Allow access
  • Require multifactor authentication
  • Require reauthentication (Sign-in frequency)
  • Require Identity Verification (preview): Users complete identity verification to remediate risk in supported scenarios.

If risks are detected on a sign-in, users can perform the required access control such as multifactor authentication to self-remediate and close the risky sign-in event to prevent unnecessary noise for administrators.

Screenshot of a sign-in risk-based Conditional Access policy.

Migrate ID Protection risk policies to Conditional Access

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…