Self-remediation experience with Microsoft Entra ID Protection and Conditional Access
In brief
The documentation now explains the Require Identity Verification challenge in risk-based Conditional Access, including testing steps and how successful or failed verification affects risk remediation.
What Entra admins need to know
Administrators can use the guidance to test the verification journey, distinguish it from adaptive risk remediation, and review risk results separately.
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.
Self-remediation experience with Microsoft Entra ID Protection and Conditional Access
When a user is required to remediate risk with this policy turned on, users must sign in immediately after their sessions are revoked. If the user just signed in but they're at risk, they'll be prompted to sign in again. The risk is remediated after the user successfully signed in the second time.
Identity verification for risk
When a risk-based Conditional Access policy uses Require Identity Verification (preview), users who meet the configured user-risk or sign-in-risk condition complete an identity verification challenge. An eligible identity verification profile, provider, and credential type are prerequisites. A recovery profile isn't automatically eligible for risk remediation.
The following illustrative example shows the Additional verification required interrupt. Use the credential type supported by your scenario's profile.
:::image type="content" source="media/concept-identity-protection-user-experience/conditional-access-identity-verification-prompt.png" alt-text="Illustrative identity verification interrupt for [email protected], prompting the user to continue in Microsoft Authenticator." lightbox="media/concept-identity-protection-user-experience/conditional-access-identity-verification-prompt.png":::
This journey is independent of the adaptive Require risk remediation flow. Don't assume that the verification challenge revokes sessions or requires the same reauthentication sequence as adaptive remediation.
To validate the journey with an approved test user:
- Confirm that the expected risk policy applies and presents the intended verification challenge.
- Complete the requested credential presentation and verification. If you need a credential, follow the supported issuance path for that credential type. Credential issuance alone isn't completion of verification.
- Return to, or restart, the original access attempt as directed by the journey. Test cancellation, verification failure, and missing or unavailable credentials separately.
- Check the access decision and verification result independently. If you can't complete verification, use your organization's support path.
Successful verification remediates user risk or sign-in risk, depending on the risk condition in the triggering policy. Failed verification doesn't remediate risk. Administrators check the targeted risk record separately; access or verification success doesn't establish that every risk was cleared.
Risky sign-in administrator unblock
Administrators might block users upon sign-in depending on their risk level. To get unblocked, users must contact their IT staff or try signing in from a familiar location or device. Self-remediation isn't an option in this case.
@@ -3,9 +3,12 @@ title: User self-remediation with Microsoft Entra ID Protection description: How can users self-remediate risk when administrators allow it? What is the experience when they don't? ms.service: entra-id-protection ms.topic: concept-article-ms.date: 10/30/2025+ms.date: 11/03/2026+author: tilarso+ms.author: tilarso+ai-usage: ai-assisted ms.reviewer: chuqiaoshi-ms.custom: sfi-image-nochange+ms.custom: sfi-image-nochange, msecd-doc-authoring-108 --- # Self-remediation experience with Microsoft Entra ID Protection and Conditional Access @@ -47,6 +50,27 @@ The adaptive risk remediation policy accommodates all authentication methods, in When a user is required to remediate risk with this policy turned on, users must sign in immediately after their sessions are revoked. If the user just signed in but they're at risk, they'll be prompted to sign in again. The risk is remediated after the user successfully signed in the second time. +### Identity verification for risk++When a risk-based Conditional Access policy uses **Require Identity Verification (preview)**, users who meet the configured user-risk or sign-in-risk condition complete an identity verification challenge. An eligible [identity verification profile](../identity/authentication/concept-authentication-verified-id.md#create-and-manage-identity-verification-profiles), provider, and credential type are prerequisites. A recovery profile isn't automatically eligible for risk remediation.++The following illustrative example shows the **Additional verification required** interrupt. Use the credential type supported by your scenario's profile.++:::image type="content" source="media/concept-identity-protection-user-experience/conditional-access-identity-verification-prompt.png" alt-text="Illustrative identity verification interrupt for [email protected], prompting the user to continue in Microsoft Authenticator." lightbox="media/concept-identity-protection-user-experience/conditional-access-identity-verification-prompt.png":::++This journey is independent of the adaptive **Require risk remediation** flow. Don't assume that the verification challenge revokes sessions or requires the same reauthentication sequence as adaptive remediation.++To validate the journey with an approved test user:++1. Confirm that the expected risk policy applies and presents the intended verification challenge.+1. Complete the requested credential presentation and verification. If you need a credential, follow the supported issuance path for that credential type. Credential issuance alone isn't completion of verification.+1. Return to, or restart, the original access attempt as directed by the journey. Test cancellation, verification failure, and missing or unavailable credentials separately.+1. Check the access decision and verification result independently. If you can't complete verification, use your organization's support path.++Successful verification remediates user risk or sign-in risk, depending on the risk condition in the triggering policy. Failed verification doesn't remediate risk. Administrators [check the targeted risk record separately](howto-identity-protection-remediate-unblock.md#validate-identity-verification-remediation); access or verification success doesn't establish that every risk was cleared.+++ ### Risky sign-in administrator unblock Administrators might block users upon sign-in depending on their risk level. To get unblocked, users must contact their IT staff or try signing in from a familiar location or device. Self-remediation isn't an option in this case. 