Scope Defender for Identity action accounts to remediation needs

Frame this document as a source-led configuration and assurance check: Scope Defender for Identity action accounts to remediation needs. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Configure Microsoft Defender for Identity action accounts from Microsoft supports the following bounded statements:

• Defender for Identity needs the required permissions to perform remediation actions on compromised on-premises Active Directory accounts, separately from the account used to read directory data. The research record locates this support at Opening overview.
• The configurable action account applies to sensor v2.x on domain controllers; sensor v3.x uses the domain controller’s LocalSystem account for remediation. The research record locates this support at Version applicability paragraph.

These statements are the factual basis for this document. Do not extend them into a broader assurance. Review Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health only where the source and recorded environment align.

What the source does not establish

Grant only the documented remediation permissions and review the security effect of LocalSystem or dedicated gMSA use. No current deployment state or change approval follows from the source alone. Validate Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations, and treat examples or options as conditional inputs rather than defaults.

Applicability questions

• For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Version applicability paragraph, 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. Start with applicability, then compare the observed state with the cited source. 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.

An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations before and after the test, and store only sanitized operational evidence.

Verification and evidence

Keep the source locations Opening overview; Version applicability paragraph adjacent to the sanitized artifacts used for comparison. Prefer sensor inventory, service and action-account permissions, health alerts, connectivity tests, portal state, and controlled detection tests, with enough identity and timing data for an independent recheck.

Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.

Official references

• Configure Microsoft Defender for Identity action accounts — Microsoft