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.

Coverage and checks

469 of 469 selected pages have a baseline · 401 with observed changes · 469 current checks

Observed changes

RSS

‹ October 2026 ›

MonTueWedThuFriSatSun1234567891011121131415161718119202122232425262728293031

October 2026 in brief

2 changes to 1 page

1 may need admin action1 read to decide

Defender 2

Pick a day to list only its changes.

Week of 12 Oct 2026

Defender Defender for Identity on AD FS, AD CS and Entra Connect servers

May need admin actionCheck whether new requirements apply to your setup.

1 new passage (17 words), 2 edited passages (4 words changed).
New section: Configure sensors for AD FS, AD CS, and Microsoft Entra Connect
Also changed: Prerequisites
Changed wording view Inline diff Before After
NewConfigure sensors for AD FS, AD CS, and Microsoft Entra Connect

[added: Use these procedures for Defender for Identity v2.x sensors. For v3.x sensors, follow v3.x deployment and configuration.]

Before: No saved wording on this side.

After: Use these procedures for Defender for Identity v2.x sensors. For v3.x sensors, follow v3.x deployment and configuration.
EditedPrerequisites

… The following additional requirements apply to [added: v2.x sensors on] AD FS, AD CS, and Microsoft …

Before: … The following additional requirements apply to AD FS, AD CS, and Microsoft …

After: … The following additional requirements apply to v2.x sensors on AD FS, AD CS, and Microsoft …
1 more changed passage · see them all
Observed 18 Oct 23:50 UTC · current page
Defender Defender for Identity on AD FS, AD CS and Entra Connect servers

Read to decideThe wording changed without matching a rule; read the changed passages to decide.

The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 12 Oct 23:53 UTC · current page