Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Guidance changes

Observed changes to selected Microsoft guidance. Review in My radar · Timelines and exceptions

469 of 469 selected pages have a baseline. 403 pages have an observed change; the newest was seen today.

Coverage and checks

469 of 469 selected pages have a baseline · 403 with observed changes · 469 current checks

Observed changes

RSS
‹ March 2015 ›
MonTueWedThuFriSatSun12345678910111213141516171819202122232425262728293031

March 2015 in brief

No change observed this month under these filters.

Week of 16 Nov 2026

  1. 2 pages · shared source commit 17 Nov 2026 – 18 Nov 2026 · 2 changes 1 may need admin action · 1 read to decide · 0 no action expected

    microsoftdocs/entra-docs · commit d55e8547df234acc92ef02b03f863c8c04b47ddf

    1. Read to decideNew content in “Credential provenance (preview)” and 2 more; read it to see whether it concerns you.

      Changed article references · 7 added · 0 removed
      • Added image: Illustrative screenshot of John Doe's passkey details showing High assurance, Employee ID under Verified with, and Temporary Access Pass under Derived from.media/concept-authentication-passkeys-fido2/passkey-credential-provenance.png
      • Added link: Identity verification licensing../../fundamentals/licensing#identity-verification
      • Added link: Identity verification status and historyconcept-authentication-methods-manage#identity-verification-status-and-history
      • Added link: identity verification status and historyconcept-authentication-methods-manage#identity-verification-status-and-history
      • Added link: Manage identity verification for a userconcept-authentication-methods-manage#manage-identity-verification-for-a-user
      • Added link: Identity verification reportinghowto-authentication-methods-activity#identity-verification-reporting
      • Added link: media/concept-authentication-passkeys-fido2/passkey-credential-provenance.png#lightbox

      22 new passages (about 800 words).

      New sections: Credential provenance (preview) · Credential assurance classification (preview) · Credential assurance lifecycle

      Changed wording view
      NewCredential provenance (preview)
      [added: Credential provenance records how a passkey was established, including its relationship to identity verification at registration. It's separate from the user's current account verification status and from passkey device or provider attestation.]
      Before: No saved wording on this side.
      After: Credential provenance records how a passkey was established, including its relationship to identity verification at registration. It's separate from the user's current account verification status and from passkey device or provider attestation.
      NewCredential provenance (preview)
      [added: Note During preview, credential provenance and credential assurance classification are available only for passkeys. Status and provenance reporting don't provide credential-provenance policy enforcement.]
      Before: No saved wording on this side.
      After: Note During preview, credential provenance and credential assurance classification are available only for passkeys. Status and provenance reporting don't provide credential-provenance policy enforcement.

      17 more changed passages · see them all

      Microsoft's commit: Publish Ignite 2026 High Assurance documentation release (#15002)

      Observed today 03:28 UTC · current page · MIT

    2. May need admin actionCheck whether new requirements apply to your setup.

      Changed article references · 5 added · 0 removed
      • Added link: Passkey registration during Identity-verified onboarding and recovery (preview)#identity-verified-onboarding-and-recovery-during-preview
      • Added link: enrollment-method and app-deployment requirements../conditional-access/policy-require-identity-verification#android-work-profile-compatibility-during-preview
      • Added link: work-profile compatibility and deployment prerequisites../conditional-access/policy-require-identity-verification#android-work-profile-compatibility-during-preview
      • Added link: Link to Windows compatibility../conditional-access/policy-require-identity-verification#link-to-windows-compatibility
      • Added link: Register passkeys in Authenticatorhow-to-register-passkey-authenticator

      8 new passages (about 320 words).

      New section: Passkey registration during Identity-verified onboarding and recovery (preview)

      Also changed: Store passkeys in Android profiles

      Changed wording view
      NewStore passkeys in Android profiles
      [added: For identity-verified onboarding and recovery during preview, users enrolled through Android Management API (AM API) should complete the journey with TAP issuance instead of being required to set up a passkey. See Passkey registration during Identity-verified onboarding and recovery (preview).]
      Before: No saved wording on this side.
      After: For identity-verified onboarding and recovery during preview, users enrolled through Android Management API (AM API) should complete the journey with TAP issuance instead of being required to set up a passkey. See Passkey registration during Identity-verified onboarding and recovery (preview).
      NewPasskey registration during Identity-verified onboarding and recovery (preview)
      [added: The minimum Authenticator app versions listed below apply to identity verification step-up, onboarding, and recovery.]
      Before: No saved wording on this side.
      After: The minimum Authenticator app versions listed below apply to identity verification step-up, onboarding, and recovery.

      5 more changed passages · see them all

      Microsoft's commit: Publish Ignite 2026 High Assurance documentation release (#15002)

      Observed 17 Nov 08:42 UTC · current page · MIT

  2. May need admin actionCheck whether new requirements apply to your setup; check the roles and permissions you grant; check the dates against your plans.

    Changed article references · 1 added · 0 removed
    • Added link: supported methods for creating an enterprise application from a multitenant app../enterprise-apps/create-service-principal-cross-tenant?pivots=ms-graph

    1 edited passage (113 words changed).

    Changed wording view
    EditedWorkarounds for an authentication strength Conditional Access policy loop
    You can exclude the Microsoft Authenticator Credential Registration resource from the Conditional Access policy. [added: 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 [removed: in] [added: 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. As a Cloud Application Administrator or Application Administrator[removed: : M][added: , m]anually 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 For example, use Microsoft Graph Explorer to make a POST request to https://graph.microsoft.com/v1.0/servicePrincipals with the following body: { "appId": "6aa00308-ea33-4caa-90d6-ae905d8cb51b" } [removed: After you provision] [added: As a Conditional Access Administrator, opt in users to] the [removed: app,] [added: dedicated registration resource. In] Microsoft [removed: Authenticator Credential Registration appears as] [added: Graph Explorer, use the Policy.ReadWrite.ConditionalAccess permission to make] a [removed: resource] [added: PATCH request to https://graph.microsoft.com/beta/identity/conditionalAccess/settings with the following body: { "authenticatorPasskeyRegistrationResourceMapping": { "isEnabled": true, "includeUsers": ["All"] } } To opt] in [added: selected users instead, replace "All" with their tenant user object IDs. Updating includeUsers replaces the existing list. This workaround requires Microsoft Authenticator version 6.2607.4697 or later for Android and version 6.8.56 or later for iOS. As a] Conditional [removed: Access. Exclude it] [added: Access Administrator, exclude Microsoft Authenticator Credential Registration] from [removed: any] [added: the] Conditional Access policies scoped to All resources t[removed: o un][added: hat ]block passkey [removed: registration in Microsoft Authenticator.] [added: registration.]
    Before: You can exclude the Microsoft Authenticator Credential Registration resource from the Conditional Access policy. 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. 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 For example, use Microsoft Graph Explorer to make a POST request to https://graph.microsoft.com/v1.0/servicePrincipals with the following body: { "appId": "6aa00308-ea33-4caa-90d6-ae905d8cb51b" } 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.
    After: 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 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. 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 For example, use Microsoft Graph Explorer to make a POST request to https://graph.microsoft.com/v1.0/servicePrincipals with the following body: { "appId": "6aa00308-ea33-4caa-90d6-ae905d8cb51b" } 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: { "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. This workaround requires Microsoft Authenticator version 6.2607.4697 or later for Android and version 6.8.56 or later for iOS. As a Conditional Access Administrator, exclude Microsoft Authenticator Credential Registration from the Conditional Access policies scoped to All resources that block passkey registration.

    Microsoft's commit: Clarify Authenticator minimum versions for passkey registration workaround

    Observed 17 Nov 21:02 UTC · current page · MIT

Week of 26 Oct 2026

  1. May need admin actionCheck whether new requirements apply to your setup; check the roles and permissions you grant; check the dates against your plans.

    Changed article references · 1 added · 0 removed
    • Added link: exclude the Microsoft Authenticator Credential Registration resource#workarounds-for-an-authentication-strength-conditional-access-policy-loop

    2 new passages (about 170 words), 1 edited passage (1 word changed), 1 removed passage (about 80 words).

    Changed in: Workarounds for an authentication strength Conditional Access policy loop · Users who can't register passkeys because of Require approved client app or Require app protection policy Conditional Access grant controls

    Changed wording view
    NewWorkarounds for an authentication strength Conditional Access policy loop
    [added: You can exclude the Microsoft Authenticator Credential Registration resource from the Conditional Access policy. 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. 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 For example, use Microsoft Graph Explorer to make a POST request to https://graph.microsoft.com/v1.0/servicePrincipals with the following body: { "appId": "6aa00308-ea33-4caa-90d6-ae905d8cb51b" } 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.]
    Before: No saved wording on this side.
    After: You can exclude the Microsoft Authenticator Credential Registration resource from the Conditional Access policy. 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. 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 For example, use Microsoft Graph Explorer to make a POST request to https://graph.microsoft.com/v1.0/servicePrincipals with the following body: { "appId": "6aa00308-ea33-4caa-90d6-ae905d8cb51b" } 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.
    EditedWorkarounds for an authentication strength Conditional Access policy loop
    Note With [removed: either] [added: 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 …
    Before: Note With either 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 …
    After: 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 …

    2 more changed passages · see them all

    Microsoft's commit: Merge pull request #14558 from tilarso/docs/migrate-passkey-pr-2124

    Observed 28 Oct 23:20 UTC · current page · MIT

Week of 12 Oct 2026

  1. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    The page title or its body outside the tracked passages changed. Review the source for its effect.

    Observed 12 Oct 23:53 UTC · current page

  2. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    The page title or its body outside the tracked passages changed. Review the source for its effect.

    Observed 12 Oct 19:50 UTC · current page

  3. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    The page title or its body outside the tracked passages changed. Review the source for its effect.

    Observed 12 Oct 19:50 UTC · current page

  4. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    The page title or its body outside the tracked passages changed. Review the source for its effect.

    Observed 12 Oct 19:35 UTC · current page

  5. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    2 edited passages (51 words changed).

    Changed wording view
    EditedPrerequisites for passkeys in Authenticator
    … in the following table to enable cross-device registration and authentication. Devices must be allowed to reach these URLs. For more information about requirements for Apple devices, see Use Apple products on enterprise networks. Platform URL Android cable.ua5v.com iOS cable.auth.comapp-site-association.cdn-apple.comapp-site-association.networking.apple Note [removed: Users can't use] [added: On iOS, users can only register attested passkeys directly in the Authenticator app. On Android, users can register attested passkeys directly in the Authenticator app and by using a] cross-device registration [removed: if you enable attestation.] [added: flow.]
    Before: … in the following table to enable cross-device registration and authentication. Devices must be allowed to reach these URLs. For more information about requirements for Apple devices, see Use Apple products on enterprise networks. Platform URL Android cable.ua5v.com iOS cable.auth.comapp-site-association.cdn-apple.comapp-site-association.networking.apple Note Users can't use cross-device registration if you enable attestation.
    After: … in the following table to enable cross-device registration and authentication. Devices must be allowed to reach these URLs. For more information about requirements for Apple devices, see Use Apple products on enterprise networks. Platform URL Android cable.ua5v.com iOS cable.auth.comapp-site-association.cdn-apple.comapp-site-association.networking.apple Note On iOS, users can only register attested passkeys directly in the Authenticator app. On Android, users can register attested passkeys directly in the Authenticator app and by using a cross-device registration flow.
    EditedAuthenticator attestation
    [removed: Users] [added: On iOS, users] can only register attested passkeys directly in the Authenticator app. [removed: Cross-device registration flows don't support registration of] [added: On Android, users can register] attested [removed: passkeys.] [added: passkeys directly in the Authenticator app and by using a cross-device registration flow.]
    Before: Users can only register attested passkeys directly in the Authenticator app. Cross-device registration flows don't support registration of attested passkeys.
    After: On iOS, users can only register attested passkeys directly in the Authenticator app. On Android, users can register attested passkeys directly in the Authenticator app and by using a cross-device registration flow.

    Microsoft's commit: Align attestation registration guidance

    Observed 12 Oct 19:35 UTC · current page · MIT

  6. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    The page title or its body outside the tracked passages changed. Review the source for its effect.

    Observed 12 Oct 19:35 UTC · current page

  7. Entra Passkeys and FIDO2

    Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    The page title or its body outside the tracked passages changed. Review the source for its effect.

    Observed 12 Oct 19:19 UTC · current page

Quoted wording: © Microsoft Corporation · source and applicable license beside each change.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 18 Nov 18:55 UTC · 272 of 275 readable · 270 fully read · documentation 469/469 current