[12.0 P1] Document passwordless account creation in the Blazor passkeys article

[aspnetcore-docs-bot]

Source: dotnet/aspnetcore#68648

Documentation confidence: 80

• Conceptual: required. The Blazor Web App template (12.0) adds a "Sign up with a passkey" option on the Register page and an anonymous /PasskeyRegistrationOptions endpoint.
• Migration: not required. Existing apps aren't affected; the article's existing-app steps now include the Register page update.
• Breaking change: not required. The change is additive.

Summary: Extended security/authentication/passkeys/blazor with 12.0-scoped sections for the registration endpoint, the Register page update, and creating an account with a passkey.

Modified files:

• aspnetcore/security/authentication/passkeys/blazor.md

Generated by PR Documentation Check · copilot · auto · 30.6 AIC · ⌖ 9.56 AIC · ⊞ 13.9K · ◷

---

Internal previews

File	Preview link
aspnetcore/security/authentication/passkeys/blazor.md	Learn preview

Build report

[aspnetcore-docs-bot]

@rolandVi, this draft documents your source change in dotnet/aspnetcore#68648.

Please review it for technical accuracy and confirm that the user impact and recommended guidance match the implementation.

[guardrex]

@BillWagner @gewarren ... We have no 12.0 moniker established for the repo yet. Do you want to add it now?

[DeagleGross]

@guardrex @tdykstra, this is a test PR from the aspnetcore workflow. The idea is to automatically process the merged PRs, and if AI thinks there is a good reason to document this (aka new feature, or new behavior, or breaking change etc), then it posts a PR here. Since this is a draft, you can ignore this. One PRs open, they are in ready-for-review state.

Does this process work for you? This will help us move faster with the docs and not forget to document anything. Let me know if you have propositions, or suggestions.

[guardrex]

All good, @DeagleGross, 👍 ... but note that Tom and Wade no longer work on this repo. I'm the only dedicated docs person left here, and it's unclear at this time if I'll still be around after December. If you need to interact with docs MS FTEs/managers about the repo, then @BillWagner and/or @gewarren are the contacts.

[DeagleGross]

Thanks Luke! btw aspnetcore onboarded to net12: dotnet/aspnetcore#69553, so i think 12.0 moniker should be prepared

[gewarren]

@BillWagner @gewarren ... We have no 12.0 moniker established for the repo yet. Do you want to add it now?

Done!

[guardrex]

Thanks, @gewarren.

@DeagleGross ... I changed the title to indicate 12.0 P1, which will probably be scheduled for February, 2027. I'll open-close this to see if the build error will clear now. UPDATE: All good! 🎉

PRs for the P1 release can accumulate here for the reference articles. It's still unknown if What's New content will move to Copilot generation. I think it would be a good idea to set that up. We doc authors are rapidly becoming real dinosaurs around here 🦖😄.

[guardrex]

@gewarren ... @aspnetcore-docs-bot[bot] triggered the CLA ☝️.