Enable and support passkeys in Authenticator for Microsoft Entra ID
In brief
The documentation now requires administrators to opt users into the dedicated registration resource through Microsoft Graph, then exclude it from applicable Conditional Access policies. Android users also need Microsoft Authenticator 6.2607.4697 or later.
What Entra admins need to know
Provision the enterprise application, configure the opt-in as a Conditional Access Administrator, and update applicable policies before passkey registration becomes available at the end of November 2026.
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.
1For users to register new sign-in methods, your grant control for the mobile policy needs to match your Conditional Access policy to register Security info.
- You can exclude the Microsoft Authenticator Credential Registration resource from the Conditional Access policy. To use this resource for passkey registration, you must also opt in users by using the Microsoft Graph API.
As a Cloud Application Administrator or Application Administrator, manually provision the Microsoft Authenticator Credential Registration app by using one of the supported methods for creating an enterprise application from a multitenant app. Use the following details:
- App ID:
6aa00308-ea33-4caa-90d6-ae905d8cb51b - Required role: Cloud Application Administrator or Application Administrator }
- App ID:
After you provisionAs a Conditional Access Administrator, opt in users to theapp,dedicated registration resource. In Microsoft Graph Explorer, use thePolicy.ReadWrite.ConditionalAccesspermission to make aPATCHrequest tohttps://graph.microsoft.com/beta/identity/conditionalAccess/settingswith the following body:{ "authenticatorPasskeyRegistrationResourceMapping": { "isEnabled": true, "includeUsers": ["All"] } }To opt in selected users instead, replace
"All"with their tenant user object IDs. UpdatingincludeUsersreplaces the existing list.As a Conditional Access Administrator, exclude Microsoft Authenticator Credential Registration
appears as a resource in Conditional Access. Exclude itfromanythe Conditional Access policies scoped to All resourcesto unblockthat block passkeyregistration in Microsoft Authenticator.registration.
@@ -2,7 +2,7 @@ title: Enable and support passkeys in Authenticator for Microsoft Entra ID description: Learn about Authenticator-specific requirements, configuration, and troubleshooting for passkeys in Microsoft Authenticator for Microsoft Entra ID. ms.topic: how-to-ms.date: 10/02/2026+ms.date: 11/04/2026 ms.reviewer: mjsantani, guptashi, tilarso ms.collection: M365-identity-device-management ms.custom: sfi-ga-nochange, sfi-image-nochange, msecd-doc-authoring-108@@ -196,14 +196,14 @@ Here are some workarounds: <sup>1</sup>For users to register new sign-in methods, your grant control for the mobile policy needs to match your Conditional Access policy to register [Security info](https://mysignins.microsoft.com/security-info). -- You can exclude the **Microsoft Authenticator Credential Registration** resource from the Conditional Access policy.+- You can exclude the **Microsoft Authenticator Credential Registration** resource from the Conditional Access policy. To use this resource for passkey registration, you must also opt in users by using the Microsoft Graph API. > [!NOTE]- > The Microsoft Authenticator Credential Registration resource will be available in November 2026. Before you can exclude the resource from a Conditional Access policy, you must provision the Microsoft Authenticator Credential Registration enterprise application in your tenant.+ > The Microsoft Authenticator Credential Registration resource will be available at the end of November 2026. Before you can exclude the resource from a Conditional Access policy, you must provision the Microsoft Authenticator Credential Registration enterprise application in your tenant.+ >+ > This workaround requires Microsoft Authenticator version **6.2607.4697 or later** for Android. - As a Cloud Application Administrator or Application Administrator:-- 1. Manually provision the **Microsoft Authenticator Credential Registration** app by using one of the [supported methods for creating an enterprise application from a multitenant app](/entra/identity/enterprise-apps/create-service-principal-cross-tenant?pivots=ms-graph). Use the following details:+ 1. As a **Cloud Application Administrator** or **Application Administrator**, manually provision the **Microsoft Authenticator Credential Registration** app by using one of the [supported methods for creating an enterprise application from a multitenant app](~/identity/enterprise-apps/create-service-principal-cross-tenant.md?pivots=ms-graph). Use the following details: - **App ID**: `6aa00308-ea33-4caa-90d6-ae905d8cb51b` - **Required role**: Cloud Application Administrator or Application Administrator@@ -216,7 +216,20 @@ Here are some workarounds: } ``` - 1. After you provision the app, **Microsoft Authenticator Credential Registration** appears as a resource in Conditional Access. Exclude it from any Conditional Access policies scoped to **All resources** to unblock passkey registration in Microsoft Authenticator.+ 1. As a **Conditional Access Administrator**, opt in users to the dedicated registration resource. In Microsoft Graph Explorer, use the `Policy.ReadWrite.ConditionalAccess` permission to make a `PATCH` request to `https://graph.microsoft.com/beta/identity/conditionalAccess/settings` with the following body:++ ```json+ {+ "authenticatorPasskeyRegistrationResourceMapping": {+ "isEnabled": true,+ "includeUsers": ["All"]+ }+ }+ ```++ To opt in selected users instead, replace `"All"` with their tenant user object IDs. Updating `includeUsers` replaces the existing list.++ 1. As a **Conditional Access Administrator**, exclude **Microsoft Authenticator Credential Registration** from the Conditional Access policies scoped to **All resources** that block passkey registration. > [!NOTE] > With any workaround, users must also satisfy any Conditional Access policy that targets **Register security info** or they can't register the passkey. If you have other conditions set up with the **All resources** policies, those conditions must be met when the passkey is registered. 