Entra Content Refactor: Trim duplicated secret-setup steps in microsoft-logins.md

[wadepickett]

Description

Contributes to epic #36277

Summary

The microsoft-logins.md article already links to the authoritative Entra docs for app registration and credential creation, but the "Next steps" section restates Entra admin-center secret steps that the Entra docs own. Per the epic goal, trim the duplication and point to Entra instead.

File

• aspnetcore/security/authentication/social/microsoft-logins.md

Current state

• Already links to Entra for app registration (L21/88) and credentials (L25/92) — these are correct and should stay.
• The "Next steps" bullets restate Entra admin-center secret creation/configuration (L76–77 and L139–140).

Requested changes

1. Trim the "Next steps" secret-step restatements (L76–77, L139–140) to a concise crosslink to the authoritative Entra guidance already referenced earlier in the article.
2. Leave the ASP.NET Core–specific content (Secret Manager usage, Program.cs/Startup configuration, sign-in flow) intact.

Guardrail

This is a light content trim, not a rewrite. Remove only the duplicated Entra secret-setup restatements; keep all ASP.NET Core framework content and the existing correct Entra crosslinks.

Note

The previously associated PR #36508 fixed an unrelated bug (#36497) and does not address this refactor; a fresh change is needed.

Page URL

https://learn.microsoft.com/en-us/aspnet/core/security/authentication/social/microsoft-logins?view=aspnetcore-10.0

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/security/authentication/social/microsoft-logins.md

Document ID

ce69b990-0b4c-abda-cd2d-68f85cd8031e

Platform Id

c1bb804d-a454-af4f-b074-976f71ffb606

Article author

@tdykstra

Metadata

• ID: a4c264c0-0c5c-298e-bb45-9b4891c8d162
• PlatformId: c1bb804d-a454-af4f-b074-976f71ffb606
• Service: aspnet-core
• Sub-service: security

Related Issues

[wadepickett]

After talking a closer look at the next step link, I decided they are fine as is. Closing. It was a mistake to create this issue in the first place.