Account recovery overview in Microsoft Entra ID
In brief
The documentation now describes recovery as enabling registration of replacement authentication methods, rather than a complete authentication-method reset. It also updates group exclusion behavior, validation through directory claim mappings or extensions, and the default TAP flow, with a preview option for supported devices.
What Entra admins need to know
Administrators should review recovery profile scope, validation mappings, and TAP expectations when configuring or documenting account recovery.
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.
Account recovery overview in Microsoft Entra ID
Account recovery is a Microsoft Entra ID capability that enables users to regain access to their organizational accounts when they lose all registered authentication methods — such as when a primary device is lost, stolen, or compromised. Unlike self-service password reset (SSPR), which requires users to retain at least one authentication method, account recovery re-establishes trust in a user's identity through third-party identity verification before restoring access.
Account recovery replaces manual helpdesk-led recovery withuses automated identity proofing. Traditional helpdesk recovery is vulnerableproofing to socialreduce reliance on manual help desk verification. Social engineering attacks where bad actorscan manipulate support staff into illegitimately granting unauthorized access. Account recovery eliminates this attack vectorhelps reduce that risk by using government-issued identification and biometric verification through certified identity verification providers.
Account recovery fundamentals
| Primary use case | User forgot password but retains access to authentication methods | User lost access to all authentication methods |
| Authentication requirement | At least one registered method (policy can require up to two) | Identity verification through a certified provider |
| Trust assumption | User's identity is verified through existing methods | User's identity must be re-established |
| Recovery scope | Password only | CompleteAccess to register replacement authentication method resetmethods |
| Technology dependency | Existing MFAmultifactor authentication (MFA) methods | Identity verification services, Verified ID |
| Security level | Medium — relies on pre-registered methods | High — requires comprehensive identity proofing |
Business benefits
- Reduced
helpdeskhelp desk burden — Secure self-service recovery for total lockout scenarios reduces high-priority support tickets that require manual intervention. - Improved user experience — Users recover accounts independently without waiting for
helpdeskhelp desk availability, reducing downtime during critical situations. - Stronger security posture — Identity verification provides stronger assurance than traditional recovery methods that rely on social engineering-vulnerable information.
- Scalable for remote work — Organizations support distributed workforces without requiring physical presence or complex manual verification.
How account recovery works
Identity verification profiles — Configuration objects in the Microsoft Entra admin center that define how account recovery works for a specific group of users. Each profile specifies the recovery mode, target user groups, identity verification provider, and account validation rules. Organizations can create multiple profiles to support different user populations with different requirements.
Custom authentication extensions — Optional Azure Function, Logic App, or REST API endpoints that add organization-specific account validation logic during recovery. Verified claims from the identity verification provider are passed to the extension, which validates them against organizational data such as a human resources information system (HRIS) or an employee directory. Extensions should use managed identities or other secretless authentication for service-to-service communication. All data processed by the extension stays within the organization's trust boundary — no organizational data is shared with Microsoft.
Recovery flow
Credential validation
The user presents their newly acquired Verified ID to Microsoft Entra ID. The system validates the credential's authenticity. Account validation then uses the profile's configured directory claim mappings, a custom authentication extension, or both.
Access restoration
By default, the user receives a Temporary Access Pass (TAP) with limited validity and is guided through registering new authentication methods, such as passkeys. For the preview option to register without a TAP on supported devices, see Registration with or without a TAP.
Identity verification profiles
- Profile name and description — A friendly name to identify the profile's purpose.
- Recovery mode — Whether the profile operates in Evaluation mode (testing only — accounts are not recovered) or Production mode (full recovery enabled).
- User group scope — Included groups define the profile's scope. Excluded groups are excluded globally across all identity verification profiles.
- Identity verification provider — The third-party provider that performs identity proofing for users in this profile.
- Account validation rules — How identity claims are validated through configured directory mappings (Matches exactly or Contains for name matching), a custom authentication extension, or both.
Organizations create multiple profiles to address different requirements across their user populations. For example, a profile for corporate employees might use a different identity verification provider or stricter validation rules than a profile for frontline workers.
Each identity verification profile operates in one of two modes:
- Evaluation — Users can test the identity verification flow to confirm it works correctly. Accounts are not recovered in this mode. Use Evaluation mode to validate the experience with a small group before enabling full recovery.
- Production — Users who complete identity verification can fully recover their accounts, receive a Temporary Access Pass by default, and re-enroll authentication methods.
Start with Evaluation mode for new profiles to confirm the identity verification flow works for your users and policies before switching to Production.
Account validation and custom authentication extensions
For profiles that use first-name and last-name directory matching, identity claims are checked against the corresponding user properties in Microsoft Entra ID. The name-matching confidence levels described here are:
- Matches exactly — Claims must match exactly.
- Contains — Uses cross-field word matching to accommodate variations in names.
These options were previously named Exact and Relaxed, respectively. The labels changed, but the matching behavior is unchanged.
Custom authentication extensions can supplement directory matching or replace it entirely. During recovery, verified claims from the identity verification provider are passed to an organization-owned endpoint — an Azure Function, Logic App, or REST API — which validates them against authoritative data sources such as:
- HRIS systems (employee records)
- Employee directories
Understand shared profiles and registration options
Recovery requires identity verification. Configure the tenant's Account recovery policy, identity verification profiles, recovery settings, and Conditional Access scope.
Tenant-level recovery enablement
In the new Account recovery policy experience, the policy is disabled by default for both new and existing tenants. Enable the policy before users can recover their accounts. Tenants that used an earlier preview also need to enable the new policy to continue using recovery; existing profiles alone aren't sufficient.
Tenant-level enablement is separate from TAP issuance and stale-credential cleanup. See Enable the Account recovery policy.
Shared profiles and recovery settings
Manage shared profiles in Verified ID > ID verification profiles > Profiles. Tenant-level recovery enablement and actions after recovery are configured in the Account recovery settings blade.
Use Create an ID verification profile for shared profile setup and Configure recovery settings to choose a registration path.
Registration with or without a TAP (preview)
TAP issuance is on by default for new and existing tenants. This default controls the registration path when recovery is enabled; it doesn't enable the tenant's Account recovery policy. An explicit preview option lets you turn issuance off.
| Path after successful validation | Registration experience |
|---|---|
| TAP issuance on | Issue a TAP and use the established authentication method registration flow. |
| TAP issuance off | Continue to registration within the same recovery session without receiving a TAP on supported devices. When passkey attestation is required, this path is supported only on Android; iOS continues to receive a TAP. |
Stale-credential cleanup is off by default and requires explicit preview opt-in with TAP issuance off. Turning TAP issuance back on turns cleanup off before saving. When enabled, cleanup deletes all previously registered authentication methods after successful recovery and registration of the replacement passkey. It preserves the new passkey. If deletion fails, recovery remains successful.
Conditional Access and verification evidence
You can also apply Conditional Access to onboarding and recovery, adding an extra layer of security to the recovery flow. See Protect onboarding and recovery with Conditional Access for configuration guidance.
Identity verification status shows the user's current verification state, and verification history records the user's verification events. Successful recovery writes verification history to the user's account. When the user registers a passkey during recovery, credential provenance is recorded on that passkey to describe how it was established. For more information, see User verification status and history and Passkey credential provenance.
Next step
Account recovery takes about 5–10 minutes to set up. Start in Evaluation mode so you can validate the experience before enabling production recovery.
[!div class="nextstepaction"] Enable and configure account recovery in Microsoft Entra ID
Related content
@@ -4,18 +4,21 @@ description: Account recovery in Microsoft Entra ID enables users to regain acce ms.reviewer: tilarso ms.service: entra-id ms.topic: concept-article-ms.custom: msecd-doc-authoring-108, msecd-doc-authoring-1012-ms.date: 04/29/2026+ms.custom: sfi-ga-nochange, sfi-image-nochange, msecd-doc-authoring-1026+ms.date: 11/13/2026+author: rogulati+ms.author: rogulati+ai-usage: ai-assisted #customer intent: As an identity administrator, I want to understand how account recovery works in Microsoft Entra ID so that I can evaluate whether to deploy it for users who lose all their authentication methods. --- -# Account recovery overview+# Account recovery overview in Microsoft Entra ID Account recovery is a Microsoft Entra ID capability that enables users to regain access to their organizational accounts when they lose all registered authentication methods — such as when a primary device is lost, stolen, or compromised. Unlike self-service password reset (SSPR), which requires users to retain at least one authentication method, account recovery re-establishes trust in a user's identity through third-party identity verification before restoring access. -Account recovery replaces manual helpdesk-led recovery with automated identity proofing. Traditional helpdesk recovery is vulnerable to social engineering attacks where bad actors manipulate support staff into illegitimately granting access. Account recovery eliminates this attack vector by using government-issued identification and biometric verification through certified identity verification providers.+Account recovery uses automated identity proofing to reduce reliance on manual help desk verification. Social engineering attacks can manipulate support staff into granting unauthorized access. Account recovery helps reduce that risk by using government-issued identification and biometric verification through certified identity verification providers. ## Account recovery fundamentals @@ -43,19 +46,19 @@ Although account recovery and SSPR both restore user access, they address differ | **Primary use case** | User forgot password but retains access to authentication methods | User lost access to all authentication methods | | **Authentication requirement** | At least one registered method (policy can require up to two) | Identity verification through a certified provider | | **Trust assumption** | User's identity is verified through existing methods | User's identity must be re-established |-| **Recovery scope** | Password only | Complete authentication method reset |-| **Technology dependency** | Existing MFA methods | Identity verification services, Verified ID |+| **Recovery scope** | Password only | Access to register replacement authentication methods |+| **Technology dependency** | Existing multifactor authentication (MFA) methods | Identity verification services, Verified ID | | **Security level** | Medium — relies on pre-registered methods | High — requires comprehensive identity proofing | ### Business benefits -- **Reduced helpdesk burden** — Secure self-service recovery for total lockout scenarios reduces high-priority support tickets that require manual intervention.-- **Improved user experience** — Users recover accounts independently without waiting for helpdesk availability, reducing downtime during critical situations.+- **Reduced help desk burden** — Secure self-service recovery for total lockout scenarios reduces high-priority support tickets that require manual intervention.+- **Improved user experience** — Users recover accounts independently without waiting for help desk availability, reducing downtime during critical situations. - **Stronger security posture** — Identity verification provides stronger assurance than traditional recovery methods that rely on social engineering-vulnerable information. - **Scalable for remote work** — Organizations support distributed workforces without requiring physical presence or complex manual verification. > [!TIP]-> The Account Recovery overview page in the Microsoft Entra admin center includes a **cost savings estimator** that helps organizations project potential savings by comparing traditional helpdesk recovery costs against self-service account recovery.+> The Account Recovery overview page in the Microsoft Entra admin center includes a **cost savings estimator** that helps organizations project potential savings by comparing traditional help desk recovery costs against self-service account recovery. ## How account recovery works @@ -69,7 +72,7 @@ Account recovery operates through a structured identity verification and trust r - **Identity verification profiles** — Configuration objects in the Microsoft Entra admin center that define how account recovery works for a specific group of users. Each profile specifies the recovery mode, target user groups, identity verification provider, and account validation rules. Organizations can create multiple profiles to support different user populations with different requirements. -- **Custom authentication extensions** — Optional Azure Function, Logic App, or REST API endpoints that add organization-specific account validation logic during recovery. Verified claims from the identity verification provider are passed to the extension, which validates them against organizational data such as HRIS systems or employee directories. Extensions should use managed identities or other secretless authentication for service-to-service communication. All data processed by the extension stays within the organization's trust boundary — no organizational data is shared with Microsoft.+- **Custom authentication extensions** — Optional Azure Function, Logic App, or REST API endpoints that add organization-specific account validation logic during recovery. Verified claims from the identity verification provider are passed to the extension, which validates them against organizational data such as a human resources information system (HRIS) or an employee directory. Extensions should use managed identities or other secretless authentication for service-to-service communication. All data processed by the extension stays within the organization's trust boundary — no organizational data is shared with Microsoft. ### Recovery flow @@ -85,11 +88,11 @@ The user is redirected to the identity verification provider specified in their ### Credential validation -The user presents their newly acquired Verified ID to Microsoft Entra ID. The system validates the credential's authenticity and matches identity attributes from the credential against stored user profile information — first name and last name by default. If a custom authentication extension is configured in the profile, additional claim validation runs against organizational data.+The user presents their newly acquired Verified ID to Microsoft Entra ID. The system validates the credential's authenticity. Account validation then uses the profile's configured directory claim mappings, a custom authentication extension, or both. ### Access restoration -The user receives a Temporary Access Pass with limited validity and is guided through registering new authentication methods, such as passkeys.+By default, the user receives a Temporary Access Pass (TAP) with limited validity and is guided through registering new authentication methods, such as passkeys. For the preview option to register without a TAP on supported devices, see [Registration with or without a TAP](#registration-with-or-without-a-tap-preview). ## Identity verification profiles @@ -97,9 +100,9 @@ Identity verification profiles are the central configuration object for account - **Profile name and description** — A friendly name to identify the profile's purpose. - **Recovery mode** — Whether the profile operates in Evaluation mode (testing only — accounts are not recovered) or Production mode (full recovery enabled).-- **User group scope** — Which users the profile applies to, defined by included and excluded groups.+- **User group scope** — Included groups define the profile's scope. Excluded groups are excluded globally across all identity verification profiles. - **Identity verification provider** — The third-party provider that performs identity proofing for users in this profile.-- **Account validation rules** — How identity claims are matched against Entra user properties, including match confidence (exact or relaxed) and optional custom authentication extension validation.+- **Account validation rules** — How identity claims are validated through configured directory mappings (**Matches exactly** or **Contains** for name matching), a custom authentication extension, or both. Organizations create multiple profiles to address different requirements across their user populations. For example, a profile for corporate employees might use a different identity verification provider or stricter validation rules than a profile for frontline workers. @@ -108,7 +111,7 @@ Organizations create multiple profiles to address different requirements across Each identity verification profile operates in one of two modes: - **Evaluation** — Users can test the identity verification flow to confirm it works correctly. Accounts are **not** recovered in this mode. Use Evaluation mode to validate the experience with a small group before enabling full recovery.-- **Production** — Users who complete identity verification can fully recover their accounts, receive a Temporary Access Pass, and re-enroll authentication methods.+- **Production** — Users who complete identity verification can fully recover their accounts, receive a Temporary Access Pass by default, and re-enroll authentication methods. Start with Evaluation mode for new profiles to confirm the identity verification flow works for your users and policies before switching to Production. @@ -117,15 +120,17 @@ Start with Evaluation mode for new profiles to confirm the identity verification ### Account validation and custom authentication extensions -By default, account recovery matches identity claims from the verification provider against the user's **First name** and **Last name** properties in Microsoft Entra ID. Admins can configure the match confidence level:+For profiles that use first-name and last-name directory matching, identity claims are checked against the corresponding user properties in Microsoft Entra ID. The name-matching confidence levels described here are: -- **Exact** — Claims must match exactly.-- **Relaxed** — Allows minor variations in name matching.+- **Matches exactly** — Claims must match exactly.+- **Contains** — Uses cross-field word matching to accommodate variations in names.++These options were previously named **Exact** and **Relaxed**, respectively. The labels changed, but the matching behavior is unchanged. > [!TIP]-> For sensitive user populations, consider enabling a custom authentication extension to validate additional claims beyond first and last name. Default name-only matching may not provide sufficient assurance for high-risk accounts.+> For sensitive user populations, consider enabling a custom authentication extension to validate additional claims beyond first and last name. Name-only matching may not provide sufficient assurance for high-risk accounts. -For organizations that need stronger validation, custom authentication extensions add a second layer of account matching. During recovery, verified claims from the identity verification provider are passed to an organization-owned endpoint — an Azure Function, Logic App, or REST API — which validates them against authoritative data sources such as:+Custom authentication extensions can supplement directory matching or replace it entirely. During recovery, verified claims from the identity verification provider are passed to an organization-owned endpoint — an Azure Function, Logic App, or REST API — which validates them against authoritative data sources such as: - HRIS systems (employee records) - Employee directories@@ -135,9 +140,56 @@ For organizations that need stronger validation, custom authentication extension > [!IMPORTANT] > Data processed by the custom authentication extension stays within the organization's trust boundary. No organizational data is shared with Microsoft — only the match result is returned to the account recovery flow. -## Next steps+<a id="understand-the-proposed-recovery-experience"></a>++## Understand shared profiles and registration options++Recovery requires identity verification. Configure the tenant's Account recovery policy, identity verification profiles, recovery settings, and Conditional Access scope.++### Tenant-level recovery enablement++In the new Account recovery policy experience, the policy is disabled by default for both new and existing tenants. Enable the policy before users can recover their accounts. Tenants that used an earlier preview also need to enable the new policy to continue using recovery; existing profiles alone aren't sufficient.++Tenant-level enablement is separate from TAP issuance and stale-credential cleanup. See [Enable the Account recovery policy](how-to-account-recovery-enable.md#enable-the-account-recovery-policy).++### Shared profiles and recovery settings++Manage shared profiles in **Verified ID** > **ID verification profiles** > **Profiles**. Tenant-level recovery enablement and actions after recovery are configured in the Account recovery settings blade.++Use [Create an ID verification profile](../../verified-id/how-to-create-id-verification-profile.md) for shared profile setup and [Configure recovery settings](how-to-account-recovery-enable.md#configure-recovery-settings) to choose a registration path.++### Registration with or without a TAP (preview)++TAP issuance is on by default for new and existing tenants. This default controls the registration path when recovery is enabled; it doesn't enable the tenant's Account recovery policy. An explicit preview option lets you turn issuance off.++| Path after successful validation | Registration experience |+| --- | --- |+| TAP issuance on | Issue a TAP and use the established authentication method registration flow. |+| TAP issuance off | Continue to registration within the same recovery session without receiving a TAP on supported devices. When passkey attestation is required, this path is supported only on Android; iOS continues to receive a TAP. |++Stale-credential cleanup is off by default and requires explicit preview opt-in with TAP issuance off. Turning TAP issuance back on turns cleanup off before saving. When enabled, cleanup deletes all previously registered authentication methods after successful recovery and registration of the replacement passkey. It preserves the new passkey. If deletion fails, recovery remains successful.++> [!NOTE]+> When passkey attestation is required, turning off TAP issuance is supported only on Android. iOS continues to receive a TAP, even when TAP issuance is turned off, because the TAP-free registration path doesn't support attestation on iOS.++### Conditional Access and verification evidence++You can also apply Conditional Access to onboarding and recovery, adding an extra layer of security to the recovery flow. See [Protect onboarding and recovery with Conditional Access](../conditional-access/policy-require-identity-verification.md#configure-an-onboarding-and-recovery-policy) for configuration guidance.++> [!NOTE]+> **Terms of use**, **Require authentication strength**, and most other Microsoft Entra-specific controls aren't supported for the onboarding and recovery user action. Review the [control limitations](../conditional-access/policy-require-identity-verification.md#review-control-limitations) and test policy enforcement before rollout.++Identity verification status shows the user's current verification state, and verification history records the user's verification events. Successful recovery writes verification history to the user's account. When the user registers a passkey during recovery, credential provenance is recorded on that passkey to describe how it was established. For more information, see [User verification status and history](concept-authentication-methods-manage.md#identity-verification-status-and-history) and [Passkey credential provenance](concept-authentication-passkeys-fido2.md#credential-provenance).++> [!NOTE]+> During preview, credential provenance is recorded only for passkey credentials.++## Next step++Account recovery takes about 5–10 minutes to set up. Start in Evaluation mode so you can validate the experience before enabling production recovery. -Account recovery takes about 5–10 minutes to set up. Start in Evaluation mode so you can validate the experience before enabling production recovery. To get started, see [Enable and configure account recovery in Microsoft Entra ID](how-to-account-recovery-enable.md).+> [!div class="nextstepaction"]+> [Enable and configure account recovery in Microsoft Entra ID](how-to-account-recovery-enable.md) ## Related content 