{"id":17391,"date":"2026-07-21T04:01:14","date_gmt":"2026-07-20T19:01:14","guid":{"rendered":"https:\/\/m365jp.net\/?p=17391"},"modified":"2026-07-21T04:06:05","modified_gmt":"2026-07-20T19:06:05","slug":"mc1221452-updatemicrosoft-entra-id-general-availability-of-passkey-profiles-and-migration-for-existing-passkeys-fido2-tenants-3","status":"publish","type":"post","link":"https:\/\/m365jp.net\/index.php\/2026-07-21-mc1221452-updatemicrosoft-entra-id-general-availability-of-passkey-profiles-and-migration-for-existing-passkeys-fido2-tenants-3","title":{"rendered":"MC1221452 | (Update)Microsoft Entra ID: General Availability of passkey profiles and migration for existing Passkeys (FIDO2) tenants"},"content":{"rendered":"
\n
\n
\n\n\n\n
MC1221452 | (Update)Microsoft Entra ID: General Availability of passkey profiles and migration for existing Passkeys (FIDO2) tenants<\/th>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n\n\n\n\n\n\n\n
Classification<\/th>\nplanForChange<\/td>\n<\/tr>\n
Last Updated<\/th>\n07\/20\/2026 18:35:44<\/td>\n<\/tr>\n
Start Time<\/th>\n01\/23\/2026 00:54:46<\/td>\n<\/tr>\n
End Time<\/th>\n11\/30\/2026 07:00:00<\/td>\n<\/tr>\n
Message Content<\/th>\n\n

Updated July 20, 2026: We have updated the content. Thank you for your patience.<\/p>\n

[Introduction]<\/strong><\/p>\n

Starting in March 2026<\/strong>, Microsoft Entra ID will introduce passkey profiles <\/strong>and synced passkeys<\/strong> to General Availability (GA). This update allows administrators to opt in to a new passkey profiles experience that supports group-based passkey configurations and introduces a new passkeyType<\/strong> property.<\/p>\n

Important:<\/strong> Only tenants that already have Passkeys (FIDO2) enabled<\/strong> are affected by this update. <\/p>\n

<\/p>\n

<\/p>\n

The passkeyType<\/strong> property enables admins to configure:<\/p>\n

    \n
  1. <\/span>Device-bound passkeys<\/li>\n
  2. <\/span>Synced passkeys<\/li>\n
  3. <\/span>Both<\/li>\n<\/ol>\n

    If your tenant already has Passkeys (FIDO2) enabled and you do not opt in to passkey profiles during the initial rollout window, your tenant will be automatically migrated to the passkey profiles schema at the date range specified below. When this occurs: <\/p>\n

      \n
    1. <\/span>Existing Passkey (FIDO2) authentication method configurations will be moved into a Default passkey profile.<\/strong> <\/li>\n
    2. <\/span>The passkeyType<\/strong> value will be set based on the tenant\u2019s current attestation settings. Synced passkeys will be enabled for tenants with attestation enforcement disabled. <\/li>\n
    3. <\/span>No new authentication methods are enabled as part of this migration. <\/li>\n
    4. <\/span>This migration also impacts Authentication methods registration campaign set to \u201cMicrosoft managed\u201d state, which uses passkey configuration settings to determine which registration prompts are shown to users.<\/li>\n<\/ol>\n

      Authentication Methods Registration Campaign changes (Microsoft-Managed Only)<\/strong><\/p>\n

      Tenants are impacted when all the following conditions are met:<\/p>\n

        \n
      1. <\/span>The Passkeys (FIDO2) authentication method policy is Enabled<\/li>\n
      2. <\/span>Authentication methods registration campaign is set to \u201cMicrosoft managed\u201d state<\/li>\n
      3. <\/span>Allow self-service setup is Enabled<\/li>\n
      4. <\/span>Target specific AAGUIDs is not selected (no AAGUID restrictions configured)<\/li>\n
      5. <\/span>The Authentication Methods Registration Campaign state is set to Microsoft-managed<\/li>\n
      6. <\/span>The tenant has at least one user enabled for both<\/strong> synced passkeys and device\u2011bound passkeys<\/li>\n
      7. <\/span>Only users who are enabled for both synced passkeys and device\u2011bound passkeys, with no passkey profile restrictions configured (i.e. attestation enforcement, AAGUID restrictions), will receive a passkey registration nudge during sign\u2011in.<\/li>\n<\/ol>\n

        For these tenants, Microsoft-managed registration campaign settings will be updated after passkey profile automatic migration is complete. We will roll out changes incrementally to in-scope tenants according to the timeline outlined below. <\/p>\n

        [When this will happen]<\/strong><\/p>\n

        Passkey profile and Synced passkeys General Availability<\/strong><\/p>\n

          \n
        1. <\/span>Public cloud Worldwide, GCC:<\/strong> Rollout begins in early March 2026 and is expected to complete by late March 2026 <\/li>\n
        2. <\/span>GCC High, DoD clouds:<\/strong> Rollout begins in early May 2026 and is expected to complete by late May 2026 <\/li>\n
        3. <\/span>USNat, USSec:<\/strong> Rollout begins in early October 2026 (previously early July) and is expected to complete by late October 2026 (previously late July) <\/li>\n<\/ol>\n

          Automatic migration for existing passkeys (FIDO2) enabled tenants<\/strong><\/p>\n

            \n
          1. <\/span>Public cloud Worldwide, GCC: <\/strong>Rollout begins in early May 2026 and is expected to complete by late June 2026<\/li>\n
          2. <\/span>GCC High, DoD clouds: <\/strong>Rollout begins in early October 2026 (previously early August) and is expected to complete by late October 2026 (previously late August)<\/li>\n
          3. <\/span>USNat, USSec<\/strong>: Rollout begins in early October 2026 (previously early August) and is expected to complete by late October 2026 (previously late August)<\/li>\n<\/ol>\n

            Authentication Methods registration campaign changes in Microsoft-Managed state (for in-scope tenants):<\/strong><\/p>\n

              \n
            1. <\/span>Public cloud Worldwide, GCC: <\/strong>Rollout begins in early May 2026 and is expected to complete by late June 2026 <\/li>\n<\/ol>\n

              [How this affects your organization]<\/strong><\/p>\n

              Automatic migration for existing passkeys (FIDO2) enabled tenants <\/strong> <\/p>\n

              What will happen:<\/em><\/p>\n

              If you have not opted in to passkey profiles by your automatic enablement period, your tenant will be migrated to passkey profiles.<\/p>\n

                \n
              1. <\/span>Your existing Passkey (FIDO2) configurations will be migrated into a Default passkey profile<\/strong><\/li>\n
              2. <\/span>New passkeyType <\/strong>property will be auto-populated<\/li>\n
              3. <\/span>If enforce attestation <\/strong>is enabled<\/strong>, then device-bound allowed<\/li>\n
              4. <\/span>If enforce attestation <\/strong>is disabled<\/strong>, then device-bound and synced allowed<\/li>\n
              5. <\/span>Any existing key restrictions <\/strong>will remain intact<\/li>\n
              6. <\/span>Any existing user targets <\/strong>will be assigned to the Default passkey profile<\/strong><\/li>\n<\/ol>\n

                Authentication Methods registration campaign changes in Microsoft-Managed state (for in-scope tenants) <\/strong><\/p>\n

                What will happen:<\/em><\/p>\n

                Microsoft-managed registration campaign settings will be updated: <\/p>\n

                  \n
                1. <\/span>“Targeted authentication method\u201d will change from Microsoft Authenticator to \u201cpasskeys (FIDO2)\u201d. <\/li>\n
                2. <\/span>\u201cDays allowed to snooze\u201d setting will change from 3days to \u201c1 day\u201d. This setting will no longer be configurable. <\/li>\n
                3. <\/span>\u201cLimited number of snoozes\u201d setting will change from Enabled to “Disabled\u201d. This setting will no longer be configurable. <\/li>\n
                4. <\/span>The default user targeting will be updated from voice call or text message users to all multifactor authentication (MFA) capable users. <\/li>\n<\/ol>\n

                  What is the end user impact: <\/p>\n

                  Once the above changes have taken effect, users targeted in the registration campaign will begin to receive passkey registration nudges during sign-in flows after they have completed multifactor authentication. <\/p>\n

                    \n
                  1. <\/span> <\/li>\n<\/ol>\n

                    [What you can do to prepare]<\/strong><\/p>\n

                    If you want a configuration different from the migration defaults, review the timeline above and opt in to passkey profiles before your tenant\u2019s automatic enablement window begins<\/strong>. Then configure the Default passkey profile\u2019s passkeyType<\/strong> to your preferred values.<\/p>\n

                    We also recommend:<\/p>\n

                      \n
                    1. <\/span>Review your registration campaign <\/strong>configuration, especially if its set to Microsoft-managed<\/strong>. If you do not want registration campaign to target passkeys, you can: <\/li>\n
                    2. <\/span>Switch the registration campaign state to Enabled<\/em><\/strong> and continue targeting Microsoft Authenticator, or <\/li>\n
                    3. <\/span>Set the registration campaign state to Disabled<\/em><\/strong>.<\/li>\n
                    4. <\/span>Update runbooks and help content so your help desk and end users understand any changes in passkey availability or behavior. <\/li>\n<\/ol>\n

                      Learn more:<\/p>\n

                        \n
                      1. <\/span>Enable passkeys for your organization – Microsoft Entra ID | Microsoft Learn<\/a> <\/li>\n
                      2. <\/span>How to Enable Passkey (FIDO2) Profiles in Microsoft Entra ID (preview) – Microsoft Entra ID | Microsoft Learn<\/a><\/li>\n
                      3. <\/span>How to Enable Synced Passkeys (FIDO2) in Microsoft Entra ID (preview) – Microsoft Entra ID | Microsoft Learn<\/a><\/li>\n
                      4. <\/span>Synced passkeys FAQ – Microsoft Entra ID | Microsoft Learn<\/a><\/li>\n<\/ol>\n

                        [Compliance considerations]<\/strong><\/p>\n

                        No compliance considerations identified. Review as appropriate for your organization.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

                        MC1221452 | (Update)Microsoft Entra ID: General Availability of passkey profiles and migration for existing Pa […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-17391","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts\/17391","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/comments?post=17391"}],"version-history":[{"count":0,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts\/17391\/revisions"}],"wp:attachment":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/media?parent=17391"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/categories?post=17391"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/tags?post=17391"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}