Microsoft Defender for Identity
Identity protection

Whats New

In brief

Eligible new Defender for Endpoint customers may receive automatic Defender for Identity sensor v3.x activation and Windows auditing. Existing Defender for Identity customers will see a portal notice before these settings are enabled; eligible non-domain-controller AD FS, AD CS, and Microsoft Entra Connect servers are now covered. A sensor update with security improvements is also listed.

What Defender admins need to know

Review the notice on the Sensor management page and select Opt out if automatic enablement is not desired. No mandatory action is stated.

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.

September 2026

Automatic sensor v3.x activation and Windows auditing by default

The rollout differs for new Microsoft Defender for Endpoint customers and existing Defender for Identity customers:

New Microsoft Defender for Endpoint customers: If your organization is licensed for Defender for Identity, its first device was onboarded to Defender for Endpoint on or after September 13, 2026, and it doesn't already have a Defender for Identity workspace, Defender for Identity automatically creates a workspace when it identifies an eligible identity-role server. It also enables automatic sensor v3.x activation and Windows auditing by default.

This flow activates the Defender for Identity sensor capability on eligible servers that are already onboarded to Defender for Endpoint. It doesn't add a separate Defender for Identity installation, activate the sensor on other Defender for Endpoint servers, or affect servers that already have a Defender for Identity sensor.

Existing Defender for Identity customers: The change becomes available gradually. The Defender portal displays a notice before it enables the settings automatically. After the notice period ends, the portal enables the settings.

While the notice appears, select Go to Advanced features to enable the settings or Opt out to prevent automatic enablement.

The notice appears on the Sensor management tab of the On-premises settings page.

For more information, see Activate the Defender for Identity sensor v3.x and Configure Windows event auditing.

Identity Security dashboard and Coverage & Maturity

The Identity Security dashboard provides a centralized view of identity-related security risks and posture across your organization. Coverage & Maturity helps security teams understand identity protection across on-premises, cloud, SaaS, identity providers, and partner technologies, identify coverage and deployment gaps, and prioritize actions to improve identity security posture. For more information, see Coverage & Maturity.

Sensor v3.x support for additional identity server roles: AD CS, AD FS, and Entra Connect (Preview)

Defender for Identity sensor v3.x now supports eligible AD FS, AD CS, and Microsoft Entra Connect servers that aren't domain controllers. Manual activationcontrollers and automatic Windows event auditing are supported. Automatic activation and migration arendon't currently supported.have an existing Defender for Identity sensor. For more information, see Defender for Identity sensor v3.x prerequisites.

Combined Sensor management tab on the On-premises settings page

August 2026

Defender for Identity sensor updates

Version numberUpdates
2.255.19347.63719This sensor update includes security improvements.

Expanded automatic auditing support for AD CS, AD FS, and Entra Connect servers

Automatic Windows event auditing now configures auditing for AD FS, AD CS, and Microsoft Entra Connect. Auditing is configured automatically on any eligible server that runs Defender for Identity sensor v3.x, including servers that aren't domain controllers. For more information, see Configure Defender for Identity to collect Windows events automatically.