Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Guidance changes

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

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 ›
MonTueWedThuFriSatSun1234567891011121314151617181191202122232425262728293031

October 2026 in brief

2 changes to 2 pages

2 may need admin action

Windows Server 1 · Defender 1

Pick a day to list only its changes.

Week of 19 Oct 2026

  1. Windows Server AD FS DKM container hardening

    May need admin actionCheck whether new requirements apply to your setup; check whether a default changed for your tenant or devices; check the roles and permissions you grant.

    18 new passages (about 1020 words), 12 edited passages (179 words changed), 27 removed passages (about 610 words).

    New sections: In this article · Opting out of automatic remediation · Ownership failure event case (Event ID 1137) · Save the previous SDDL (Recommended) and 3 more

    Also changed: CVE-2026-56155: AD FS Distributed Key Manager container ACL hardening · Summary · Take action · Expected secure state changes and 1 more

    Changed wording view
    EditedCVE-2026-56155: AD FS Distributed Key Manager container ACL hardening
    [removed: Note] Original publish date: July 14, 2026 …
    Before: Note Original publish date: July 14, 2026 …
    After: Original publish date: July 14, 2026 …
    NewIn this article
    [added: Opting out of automatic remediation]
    Before: No saved wording on this side.
    After: Opting out of automatic remediation

    3 more changed passages · see them all

    Observed 19 Oct 00:53 UTC · current page

Week of 12 Oct 2026

  1. 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
    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

Quoted wording: © Microsoft Corporation · source and applicable license beside each change.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 06:51 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current