Automatic Windows event auditing configuration availability for unified sensors (V3.x)

Starting January 2026, Microsoft Defender for Identity unified sensors (v3.x) will offer an opt-in feature for automatic Windows event-auditing configuration, simplifying deployment by auto-applying required settings on new and misconfigured existing sensors. Admins must enable this feature via UI or Graph API.

Introduction

We’re introducing a new opt-in feature for automatic event-auditing configuration in Microsoft Defender for Identity unified sensors (v3.x). This enhancement simplifies deployment by automatically applying the required Windows event-auditing settings on sensors, reducing manual post-deployment steps and ensuring consistent policy enforcement across all onboarded sensors.

When this will happen:

  • General Availability (Worldwide, GCC, GCCH, and DoD): The auditing opt-in feature will be available starting early January 2026, with rollout expected to complete by mid-January 2026. Until then, it will remain disabled in the portal.
  • Related auditing health alerts will also roll out gradually starting early January 2026, completing by mid-January 2026.

How this affects your organization:

Who is affected: Admins managing Defender for Identity unified sensors (v3.x) in Microsoft 365 tenants.

What will happen:

  • A new opt-in setting will be available in both the UI and via Graph API.
  • In the UI, this option will appear under Defender for Identity Settings → Advanced features.
  • Once enabled, the automatic configuration feature will:
    • For new sensor activations: Automatically apply all required Windows event-auditing settings during activation.
    • For existing onboarded sensors: Automatically apply Windows event-auditing settings only if misconfigured and dismiss related health issues.
  • After enabling the toggle, the automatic configuration process may take up to 24 hours to apply across all applicable Identity Unified sensors (v3.x).
  • This feature is not enabled by default and requires admin action. No changes will occur unless admins choose to enable the feature.

Relevant auditing configurations health issues covered:

What you can do to prepare:

If you plan to opt in:

  • NTLM auditing is not enabled
  • Directory Services Advanced Auditing is not enabled as required
  • Directory Services Object Auditing is not enabled as required
  • Auditing on the Configuration container is not enabled as required
  • Auditing on the ADFS container is not enabled as required

No action is required unless you choose to enable the feature.

  • Review your unified sensor deployment strategy.
  • Enable the opt-in setting via the UI or Graph API.
  • Communicate the change to relevant IT and security teams.
  • Update internal documentation if you track auditing configurations.

Learn more:

Compliance considerations:

No compliance considerations identified, review as appropriate for your organization.

Message ID: MC1193410


Comments are closed.


I've been working with Microsoft Technologies over the last ten years, mainly focused on creating collaboration and productivity solutions that drive the adoption of Microsoft Modern Workplace.

%d bloggers like this: