Summary
- A new opt-in feature for automatic event-auditing configuration will be introduced for Defender for Identity unified sensors (v3.x).
- This feature reduces manual configuration steps by automatically applying necessary Windows event-auditing settings.
- Admins can enable this feature through the UI or Graph API, located under Defender for Identity Settings ? Advanced features.
- It applies to both new sensor activations and existing sensors if misconfigured, addressing specific auditing health issues.
- Admin action is required to enable this feature, which is not activated by default.
Primary Service: Defender XDR
Admin Impact: Medium
User Impact: Low
Release Start: 15 Jan 2026
Release End: 31 Jan 2026
Services: Defender XDR
Category: Stay informeed
Tags: Feature Update, Admin Action
History
12/9/2025 Item Added to Message Center
1/7/2026 The timeline for the rollout of the auditing opt-in feature has been updated. The availability is now starting mid-January 2026 (previously early January) and will complete by the end of January 2026 (previously mid-January).
Similarly, the rollout of related auditing health alerts will now also start mid-January 2026 (previously early January) and complete by the end of January 2026 (previously mid-January).
Microsoft Message
Updated January 6, 2026: We have updated the timeline. Thank you for your patience.
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 mid-January 2026 (previously early January), with rollout expected to complete by end of January 2026 (previously mid-January). Until then, it will remain disabled in the portal.
- Related auditing health alerts will also roll out gradually starting mid-January 2026 (previously early January), completing by end of January 2026 (previously mid-January).
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:
- 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
What you can do to prepare
No action is required unless you choose to enable the feature.
If you plan to opt in:
- 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:
- Auditing health alerts documentation
- Configure Windows event auditing
- Configure audit policies for Windows event logs
Compliance considerations
No compliance considerations identified, review as appropriate for your organization.