Size Defender for Identity sensor v2 separately from sensor v3

Use this document to connect an official requirement or behavior to observable evidence: Size Defender for Identity sensor v2 separately from sensor v3. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Plan capacity for Microsoft Defender for Identity deployment from Microsoft supports the following bounded statements:

• The capacity planning tool was designed for the resource-intensive network processes of sensor v2.x. The research record locates this support at Opening overview.
• Microsoft says sensor v3.x does not require the sizing tool because it relies mainly on Windows events and event tracing and has lower resource requirements. The research record locates this support at Opening overview.

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

The tool estimates sensor capacity; it is not a substitute for production performance monitoring or application-owner approval. 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 Opening overview, 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.

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

Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Opening overview; Opening overview. 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.

Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.

Official references

• Plan capacity for Microsoft Defender for Identity deployment — Microsoft