Guidance changes

Observed changes to selected Microsoft guidance. Review in My radar · Timelines and exceptions

Summaries identify wording to review. “May need admin action” is reserved for dates, prerequisites, endpoints, permissions and defaults; a match does not confirm a policy change or availability in your environment.

How this works

Checks start a history on this installation. Observation time is not Microsoft's edit time, and edits made before collection or reverted between checks are unknown. History is limited to 20 source revisions per page.

Where a page's source is in a public Microsoft documentation repository on GitHub, its page also lists Microsoft's commits, and a change shows Microsoft's newest commit message between the two checks. That commit is the likeliest explanation, not a confirmed one: several commits can land between checks, shared include files change pages too, and commit dates are when the source changed, which can precede publication.

Changes sharing a sole source-commit candidate fold together. Other busy days fold by UTC observation date; they do not imply one upstream edit. Expand an entry to read every page. Article references show literal targets and labels, including relative addresses; image bytes are not captured or compared.

Where Microsoft publishes a page's source under an open license (CC BY 4.0, or MIT for Entra), a change shows the changed passages in Microsoft's wording, with removed and added words marked. Other pages show short quotes of the changed words only. Full document copies are not published here.

469 of 469 selected pages have a baseline. 401 pages have an observed change; the newest was seen today. 8 pages failed the last check.

Coverage and checks

469 of 469 selected pages have a baseline · 401 with observed changes · 461 current checks · 8 failed their last check

Observed changes

RSS

‹ October 2026 ›

MonTueWedThuFriSatSun1234567891011121131415161718192021222324252627282930131

Monday 12 October 2026 · day in brief

1 change to 1 page

1 may need admin action

Entra 1

30 Oct →All days

Week of 12 Oct 2026

Entra Authentication registration campaigns

May need admin actionCheck whether new requirements apply to your setup; check the roles and permissions you grant.

14 new passages (about 460 words), 4 edited passages (107 words changed), 7 removed passages (about 220 words).
New sections: How passkey registration nudges are evaluated · Step 1: Determine how the passkey profile affects the nudge · Step 2: Evaluate the platform, when required
Also changed: Examples · Can users be nudged within an SSO session? · Passkey nudge evaluation by platform · How the passkey profile affects the nudge evaluation
Changed wording view Inline diff Before After
NewHow passkey registration nudges are evaluated

[added: After a user meets the registration campaign’s eligibility requirements, their passkey profile determines whether existing registered passkeys suppress the nudge across all platforms or only for the current operating system and browser combination (platform). Start with the profile table. Use the platform table only when platform-specific evaluation applies.]

Before: No saved wording on this side.

After: After a user meets the registration campaign’s eligibility requirements, their passkey profile determines whether existing registered passkeys suppress the nudge across all platforms or only for the current operating system and browser combination (platform). Start with the profile table. Use the platform table only when platform-specific evaluation applies.
NewHow passkey registration nudges are evaluated

[added: These rules apply to passkey campaigns in both the Enabled and Microsoft managed states. They are separate from passkey profile eligibility for the Microsoft managed registration campaign. In the Microsoft managed state, only users assigned to at least one eligible passkey profile are nudged. In contrast, when the registration campaign is set to Enabled, any user who is enabled for passkeys can be nudged, regardless of their passkey profile.]

Before: No saved wording on this side.

After: These rules apply to passkey campaigns in both the Enabled and Microsoft managed states. They are separate from passkey profile eligibility for the Microsoft managed registration campaign. In the Microsoft managed state, only users assigned to at least one eligible passkey profile are nudged. In contrast, when the registration campaign is set to Enabled, any user who is enabled for passkeys can be nudged, regardless of their passkey profile.
18 more changed passages · see them all
Microsoft's commit: Merge pull request #14574 from JasSuri/docs/clarify-registration-campaign-sso-nudge
Observed 12 Oct 19:50 UTC · current page · MIT