-
Notifications
You must be signed in to change notification settings - Fork 25k
Rename/reorder BWA+Entra pivots and samples #36505
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR renames and reorders the Blazor Web App with Entra pivots to better reflect the actual distinction between the two sample implementations. Previously named "BFF pattern" and "Non-BFF pattern," the pivots are now "With YARP and Aspire" and "Without YARP and Aspire," since both samples actually implement the BFF pattern. The YARP/Aspire version is now positioned first to align with Microsoft's focus on Aspire adoption.
Key changes:
- Pivot IDs renamed from
bff-pattern/non-bff-patterntowith-yarp-and-aspire/without-yarp-and-aspire - Sample folder references updated to
BlazorWebAppEntraBffYarpAspireandBlazorWebAppEntraBff - Article metadata date updated to 12/17/2025
- Cross-references updated across multiple documentation files
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| aspnetcore/zone-pivot-groups.yml | Renamed pivot IDs and titles from BFF/non-BFF to with-YARP-and-Aspire/without-YARP-and-Aspire, reordered to prioritize YARP/Aspire version |
| aspnetcore/security/authentication/configure-jwt-bearer-authentication.md | Updated cross-reference to use new pivot ID with-yarp-and-aspire |
| aspnetcore/blazor/security/blazor-web-app-with-entra.md | Major restructuring: swapped pivot content order, updated sample folder names, corrected typo, added/moved Prerequisites and Aspire sections, updated configuration examples |
| aspnetcore/blazor/security/additional-scenarios.md | Removed pivot parameter from cross-reference to allow readers to choose their own pivot |
| aspnetcore/blazor/call-web-api.md | Updated cross-references with new pivot IDs and clearer descriptions |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
wadepickett
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved. Looks great. Just a minor item suggested to verify if it has not been already.
Fixes #36427
cc: @halter73
Wade or Tom ... We're renaming our Blazor with Entra BFF and non-BFF samples and pivots. We used to have BFF and non-BFF samples, but I thought it would be a good idea to roll web API into the non-YARP/non-Aspire sample app for demo purposes. When I did that, I inadvertently ended up with misnamed samples and pivots. We now have both samples doing BFF ... one without YARP/Aspire and one with YARP/Aspire. That's how the renaming is to go now, so you'll see adjustments here to the pivot names and the sample apps that I'm making over on dotnet/blazor-samples#636. The samples PR will merge at the same time these changes go live.
This is only difficult to look at because I'm rotating two pivots at the top. This article will have a pivot for Without YARP/Aspire and With YARP/Aspire. Given MS's focus on Aspire adoption, I'm rotating the pivots so that the article loads with the YARP/Aspire pivot by default and in the first position in the pivot selector.
I'm updating the article date on this one because this is a set of major changes.
This whole process will be repeated for the BWA+OIDC samples and article on a separate pair of PRs that I'll put up tomorrow (Friday).
Internal previews