Model every Active Directory forest in one Defender for Identity monitoring plan

Keep this document to one review outcome: Model every Active Directory forest in one Defender for Identity monitoring plan. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Microsoft Defender for Identity multi-forest considerations from Microsoft supports the following bounded statements:

• Defender for Identity supports multiple Active Directory forests and can monitor activity and profile users across them. The research record locates this support at Opening overview.
• Each Defender for Identity sensor can report to only one Defender for Identity workspace. The research record locates this support at Multi-forest considerations.

The source support ends with the statements listed above. Use them to examine Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health in the applicable environment, not to imply a wider guarantee.

What the source does not establish

Multi-forest support does not establish trust, connectivity, sensor coverage, or data residency for a specific environment. 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 Multi-forest considerations, 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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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

Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Opening overview; Multi-forest considerations. Favor sensor inventory, service and action-account permissions, health alerts, connectivity tests, portal state, and controlled detection tests, linked to stable identifiers, time, and operator.

Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.

Official references

• Microsoft Defender for Identity multi-forest considerations — Microsoft