Include non-domain and non-Windows devices in Defender for Identity monitoring scope

Keep this document to one review outcome: Include non-domain and non-Windows devices in Defender for Identity monitoring scope. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Microsoft Defender for Identity frequently asked questions from Microsoft supports the following bounded statements:

• Devices enter Defender for Identity’s monitoring scope when they authenticate or request authorization from Active Directory; this includes mobile and non-Windows endpoints. The research record locates this support at What is Defender for Identity? > Does Defender for Identity monitor only domain-joined devices?.
• Defender for Identity monitors the behavior of all computer accounts and other entities because those entities can be used for malicious activity. The research record locates this support at What is Defender for Identity? > Does Defender for Identity monitor computer accounts and user accounts?.

Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving identity alerts, investigations, remediation roles, evidence retention, escalation, exclusions, and incident workflows and the conditions the source actually describes.

What the source does not establish

The documented scope is authentication and authorization activity against Active Directory; it does not imply endpoint telemetry, complete network visibility, or detection of every malicious action. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that Active Directory, Windows DNS, time, cloud portals, endpoint data, network telemetry, privileged access, and response staffing are healthy. Documented options are review inputs, not universal mandates.

Applicability questions

• For source statement 1 at What is Defender for Identity? > Does Defender for Identity monitor only domain-joined devices?, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at What is Defender for Identity? > Does Defender for Identity monitor computer accounts and user accounts?, which observable configuration, record, or test can confirm applicability here?
• Which deployed instance of identity alerts, investigations, remediation roles, evidence retention, escalation, exclusions, and incident workflows 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, cloud portals, endpoint data, network telemetry, privileged access, and response staffing?
• 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. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of identity alerts, investigations, remediation roles, evidence retention, escalation, exclusions, and incident workflows, 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, cloud portals, endpoint data, network telemetry, privileged access, and response staffing. Handle credentials, keys, recovery data, and personal information through approved secure channels.

Verification and evidence

Build a reproducible chain from What is Defender for Identity? > Does Defender for Identity monitor only domain-joined devices?; What is Defender for Identity? > Does Defender for Identity monitor computer accounts and user accounts? to the observed environment. Useful domain evidence includes alert records, investigation timelines, analyst actions, tuning or exclusion approvals, remediation results, and case closure; label every item with scope, timestamp, collector, and stable identifier.

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

• Microsoft Defender for Identity frequently asked questions — Microsoft