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. 403 pages have an observed change; the newest was seen today.

Coverage and checks

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

Observed changes

RSS
‹ October 2017 ›
MonTueWedThuFriSatSun12345678910111213141516171819202122232425262728293031

October 2017 in brief

No change observed this month under these filters.

Week of 16 Nov 2026

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

    Changed article references · 1 added · 1 removed
    • Removed link: Microsoft Defender XDRhttps://security.microsoft.com
    • Added link: Microsoft Defender portalhttps://security.microsoft.com

    3 edited passages (17 words changed).

    Changed in: Post-installation steps (optional) · Validate successful deployment

    Changed wording view
    EditedPost-installation steps (optional)
    In [added: the] Microsoft Defender [removed: XDR,] [added: portal,] go to Settings > Identities > [removed: Sensors] [added: On-premises > Sensor Management] to view all of your Defender …
    Before: In Microsoft Defender XDR, go to Settings > Identities > Sensors to view all of your Defender …
    After: In the Microsoft Defender portal, go to Settings > Identities > On-premises > Sensor Management to view all of your Defender …
    EditedPost-installation steps (optional)
    Locate [removed: and select] the sensor that you installed on the [removed: server.] [added: server, open its row actions menu, and select Settings.]
    Before: Locate and select the sensor that you installed on the server.
    After: Locate the sensor that you installed on the server, open its row actions menu, and select Settings.

    1 more changed passage · see them all

    Observed today 03:28 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

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

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 18 Nov 22:28 UTC · 273 of 275 readable · 270 fully read · documentation 469/469 current