Automatic Windows event auditing configuration availability for unified sensors (V3.x)
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Rollout
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
Schedule dates changed in the text
Date phrases in schedule sentences differ between the versions this installation saw- Seen 6 Jan 2026
early January 2026→ end of January 2026
Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.
What the notice says
Microsoft’s text, safely structuredUpdated January 6, 2026: We have updated the timeline. Thank you for your patience.
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 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:
Compliance considerations
No compliance considerations identified, review as appropriate for your organization.
What changed
Between archive captures, newest first- Tags
Feature update, Admin impact→ Updated message, Feature update, Admin impact
Updated January 6, 2026: We have updated the timeline. Thank you for your patience. Introduction We’re introducing a new opt-in feature for automatic event-auditing configuration in … GCC, GCCH, and DoD): The auditing opt-in feature will be available starting mid-January 2026 (previously early
January 2026,January), with rollout expected to complete bymid-January 2026.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 earlyJanuary 2026,January), completing bymid-January 2026.end of January 2026 (previously mid-January). How this affects your organization: Who is affected: Admins managing Defender for …- Tags
- · first version seen
Learn more
Links from the notice and their documentation checks- Auditing health alerts documentationNot read yet
- Configure Windows event auditingNot read yet
- Configure audit policies for Windows event logsNot read yet
Related public evidence
No related evidence found in this installation's recent collection. This does not establish that no announcement exists.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- 3 linked pages have not been read yet.