Microsoft Defender for Identity
Identity protection

Multi-forest considerations - Microsoft Defender for Identity | Microsoft Learn

In brief

The page now describes monitoring, profiling, and forest mapping with Microsoft Defender rather than Defender for Identity. Its metadata was also updated.

What Defender admins need to know

Administrators should use the revised terminology when consulting the multi-forest deployment guidance. No action is stated as required.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Multi-forest considerations - Microsoft Defender for Identity | Microsoft Learn

For identity security, Microsoft Defender for Identity supports organizations with multiple Active Directory forests, givingso you the ability to easilycan monitor activity and profile users acrossin multiple forests.

Enterprise organizations typically have several Active Directory forests - often used for different purposes, including legacy infrastructure from corporate mergers and acquisitions, geographical distribution, and security boundaries (red forests).

Securing your multiple Active Directory forests with Microsoft Defender for Identity provides the following advantages:

  • View and investigate activities performed by users across multiple forests from a single location
  • Gain improved detection and reduce false positives with advanced Active Directory integration and account resolution

Network traffic impact for multi-forest support

WhenMicrosoft Defender for Identity maps your forests, it usesforests using the following process:

  1. After the Defender for Identity sensor starts running, the sensor queries the remote Active Directory forests and retrieves a list of users and machine data for profile creation.
  2. Every 5 minutes, each Defender for Identity sensor queries one domain controller from each domain, from each forest, to map all the forests in the network.