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
What changed
4 edited passages (51 words changed). 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.
[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.]
… 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 …
… onboarding through Defender for Endpoint. Eligible[removed: domain controllers][added: servers] can instead use the sensor v3.x …
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.