Page 141 of the DSE Cybersecurity knowledge center, with source-backed guidance and practical next steps.
Source-backed guidance for identity, vulnerability reduction, ransomware readiness, detection, response, and recovery.
Defender for Identity supports multiple Active Directory forests and can monitor activity and profile users across them. Each Defender for Identity sensor can report to only one Defender for Identity workspace.
Read the playbook
Each Defender for Identity sensor requires internet connectivity to the cloud service to report data and operate.
Read the briefing
The Defender for Identity sensor requires network connectivity to the Defender for Identity service. Microsoft recommends browser or PowerShell connectivity tests before deployment and again when a deployed sensor has connectivity problems.
Read the checklist
Microsoft moved classic Defender for Identity portal users to the unified Defender portal; the documentation says redirection is automatic and the legacy portal cannot be restored.
Read the explainer
Sensor settings must be configured correctly before Defender for Identity data becomes visible. Microsoft states that additional configuration and integration are needed to use the product’s full capabilities.
Read the guide
Devices enter Defender for Identity’s monitoring scope when they authenticate or request authorization from Active Directory; this includes mobile and non-Windows endpoints.
Read the playbook
A Directory Service Account reads Active Directory data by querying objects, tracking changes, and resolving entities, while the action account performs remediation. Directory Service Accounts apply only to sensor v2.x; sensor v3.x uses LocalSystem and does not use DSA or gMSA configuration.
Read the briefing
The documented gMSA is for sensor v2.x to read Active Directory data such as objects, changes, and entity information. Sensor v3.x uses LocalSystem for Active Directory interactions and does not require a gMSA or other Directory Service Account.
Read the checklist
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.
Read the explainer
The page defines prerequisite differences for a standalone sensor relative to the main deployment prerequisites. Standalone sensors do not collect ETW entries used by multiple detections, so Microsoft recommends the standard Defender for Identity sensor for full coverage.
Read the guide