Public mode

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

Some sources or documents need attention: 257/260 feeds/APIs · 416/439 docs · checked 21:54 UTC Customize Public modeDiscuss ChangeIntel on Discord

Defender for Identity deployment

Any two versions this installation kept of the page, compared the same way as each observed change. All guidance changes · Latest observation

Latest change
Defender · Official Microsoft guidance12 Oct 23:53 UTC → today 12:46 UTC

What changed across 2 changes

1 new passage (about 20 words), 5 edited passages (72 words changed), 1 removed passage (12 words). The changed wording mentions dates and deadlines, prerequisites, permissions, supported platforms, network endpoints. Review the source to confirm the effect.

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

Requirement wordingSupport wordingDate or deadline wordingEndpoint wording
EditedSelect your deployment method
… the following table to select the [removed: appropriate deployment for each] [added: recommended deployment. For supported v2.x platforms, see v2.x] server [removed: in your environment.] [added: requirements. Review the migration prerequisites separately before upgrading an existing v2.x sensor.]
EditedSelect your deployment method
[removed: For e][added: E]ligible domain [removed: controllers] [added: controllers, AD FS, AD CS, and Microsoft Entra Connect servers] running Windows Server 2019 or [removed: later,] [added: later support] sensor [removed: v3.x supports onboarding] [added: v3.x. You can onboard these servers] with or without Microsoft Defender for Endpoint deployment. [removed: Other eligible identity-role servers require Defender for Endpoint onboarding.]
EditedSelect your deployment method
… Server 2019 or later with the [removed: July] [added: September] 2026 or later cumulative update Defender … for Endpoint, activate sensor v3.x directly. [removed: For domain controllers that aren't onboarded to Defender for Endpoint,] [added: Otherwise,] use the sensor v3.x onboarding package. [removed: AD FS, AD CS, and Microsoft Entra Connect servers must be onboarded to Defender for Endpoint before activation.] Any supported server type Windows Server …
EditedSelect your deployment method
… onboarding through Defender for Endpoint. Eligible [removed: domain controllers] [added: servers] can instead use the sensor v3.x …
EditedChoose a deployment flow
If an eligible [removed: domain controller] [added: server] isn't onboarded to Defender for Endpoint, …

Short quotes of Microsoft's changed wording from Microsoft source, © Microsoft Corporation. Read the page for the full text.

Sections to inspect

Read the current Microsoft source

Compared across every change between the two versions, so an edit made and later undone does not show. Observation time is not publication time. Full source bodies are not published; as the page's license allows, only Microsoft's changed wording is shown.

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 20 Oct 21:54 UTC · 257 of 260 readable · 255 fully read · documentation 416/439 current