Plan Defender for Identity sensor coverage by server role

Keep this document to one review outcome: Plan Defender for Identity sensor coverage by server role. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Microsoft Defender for Identity deployment overview from Microsoft supports the following bounded statements:

• Defender for Identity sensors collect signals from on-premises identity infrastructure for threat detection. The research record locates this support at Opening overview.
• The service detects activity such as privilege escalation and high-risk lateral movement and reports exploitable identity issues such as unconstrained Kerberos delegation. The research record locates this support at Opening overview.

Keep the evidence boundary at these traced claims. They support a review of Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health; they do not support conclusions outside the source’s stated conditions.

What the source does not establish

Use the server-role matrix and prerequisites for implementation; the overview does not prove that every eligible server is onboarded or healthy. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations are healthy. Documented options are review inputs, not universal mandates.

Applicability questions

• For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Opening overview, which observable configuration, record, or test can confirm applicability here?
• Which deployed instance of Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health will be compared with the source, and why that instance?
• How will the review distinguish a source mismatch from a failure in Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations?
• Who approves the conclusion, exception, test window, and rollback threshold?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health, observed and expected states, owner, and reason for deviation.

Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations. Handle credentials, keys, recovery data, and personal information through approved secure channels.

Verification and evidence

Tie each conclusion back to Opening overview; Opening overview and to observable material such as sensor inventory, service and action-account permissions, health alerts, connectivity tests, portal state, and controlled detection tests. Preserve provenance and stable identifiers without copying secrets into the evidence set.

Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.

Official references

• Microsoft Defender for Identity deployment overview — Microsoft