Entra Content Refactor: Refresh stale Azure AD branding and legacy links to Entra targets (branding batch)

[wadepickett]

Contributes to epic #36277

Summary

Several ASP.NET Core articles link to legacy /azure/active-directory/develop/… paths and use stale "Azure AD" branding. Refresh to current Microsoft Entra branding and link targets. These are homogeneous, low-risk link/text swaps.

Important

Scope is narrow. Only two kinds of change are in scope: (1) retarget /azure/active-directory/develop/quickstart-v2-aspnet-core-webapp and /azure/active-directory/develop/v2-oauth2-on-behalf-of-flow links, and (2) change the literal link text "Azure AD" → "Microsoft Entra ID" where noted. Do NOT touch any Azure AD B2C links, B2C link text, or the B2C EOL include blocks — B2C is out of scope for this batch.

Verified link mapping

Both targets verified to resolve on Microsoft Learn. Re-verify before committing; if a target 404s, do not guess — flag it in the PR.

Legacy target	New target
/azure/active-directory/develop/quickstart-v2-aspnet-core-webapp	/entra/identity-platform/quickstart-web-app-sign-in
/azure/active-directory/develop/v2-oauth2-on-behalf-of-flow	/entra/identity-platform/v2-oauth2-on-behalf-of-flow

Files and changes

individual.md

• aspnetcore/security/authentication/individual.md

• ⚠️ The two tables are NOT identical — the branding differs. Make exactly these edits:

• First table — "dotnet new webapp" (L62–64):

  • L62 IndividualB2C: no change (B2C link — out of scope).
  • L63 SingleOrg: link text is already Entra ID (leave text); retarget URL /azure/active-directory/develop/quickstart-v2-aspnet-core-webapp → /entra/identity-platform/quickstart-web-app-sign-in.
  • L64 MultiOrg: link text is already Entra ID (leave text); retarget the same URL.

• Second table — "Visual Studio" (L77–79):

  • L77 (Individual / existing user store): no change (B2C link — out of scope).
  • L78 Single Org: change link text Azure AD → Microsoft Entra ID and retarget the URL.
  • L79 Multiple Org: change link text Azure AD → Microsoft Entra ID and retarget the URL.

• Do not modify: L62, L77 (B2C links/text), the [!INCLUDE] B2C EOL lines at L67 and L82, or any other row.

• After edits, exactly four URL retargets and two text swaps ("Azure AD"→"Microsoft Entra ID") should exist in this file.

configure-jwt-bearer-authentication.md

• aspnetcore/security/authentication/configure-jwt-bearer-authentication.md
• Existing /entra/msal/… link (L248) — leave as-is.
• Retarget the two /azure/active-directory/develop/v2-oauth2-on-behalf-of-flow links:
  • L250 (body, "Use Microsoft Identity Web on behalf of flow" section)
  • L334 (Standards list)
• No text/branding change needed here (link text is "Microsoft identity platform and OAuth 2.0 On-Behalf-Of flow" — already correct).

Optional low-priority touch-ups (approximate line numbers; locate by surrounding text, not by line)

• configure-oidc-web-authentication.md — tidy the "Entra or Azure portal" phrasing.
• key-vault-configuration.md — optionally crosslink the Entra app-registration/cert-upload sub-steps; keep the Azure Key Vault access-policy steps.
• grpc/authn-and-authz.md — optionally make the lone "Microsoft Entra ID" bullet a crosslink.
• key-storage-providers.md — optional wording tweak to the "Entra or Azure portal" pointer.

Note

These optional files were not re-verified. Skip any that don't cleanly match; they must not block the PR.

Definition of done

• All four /azure/active-directory/develop/quickstart-v2-aspnet-core-webapp links in individual.md (L63, L64, L78, L79) now point to /entra/identity-platform/quickstart-web-app-sign-in.
• "Azure AD" link text at L78 and L79 is now "Microsoft Entra ID". (L63/L64 text stays "Entra ID".)
• Both /azure/active-directory/develop/v2-oauth2-on-behalf-of-flow links in the JWT article (L250, L334) point to /entra/identity-platform/v2-oauth2-on-behalf-of-flow.
• No B2C link, B2C link text, or B2C EOL include was changed.
• Every retargeted /entra/… link resolves on Microsoft Learn (no 404s).
• ms.date updated in each edited file.
• No code samples, framework-integration context, or Azure Key Vault / Azure RBAC steps changed.
• PR opened against main, linking this issue.

Guardrail

Refresh the two named legacy links and the "Azure AD" text only. Do not touch Azure AD B2C content (links, text, or EOL includes), framework-integration context, code samples, or Azure Key Vault / Azure RBAC steps.