Update to Windows Autopatch diagnostic data collection levels and removal of Windows Autopatch data collection policy

Windows Diagnostics data settings must be configured for Windows Autopatch reports to accurately include devices and update status. The necessary Windows diagnostic data collection level to be configured on devices registered to Autopatch with the following diagnostic data settings: Windows 10 and Windows 11 – Required Windows 10, 1809 only – Basic With this change: Windows Autopatch will cease to deploy and configure the Windows Data Diagnostics policy. Previously, as part of the Autopatch feature activation process, Windows Autopatch deployed a policy named Windows Autopatch – Data collection which set the Windows diagnostics data collection level to Optional for managed devices. You will be able to configure and maintain the Windows Diagnostics Data level policy in your environment.  As part of the ongoing service maintenance Windows Autopatch will remove the Windows Autopatch Data collection policy from tenants starting March 03, 2025, Pacific Standard Time. This change will be completed in 2 weeks.  Action required: Create and deploy a Windows Diagnostic data collection policy with at least the recommended minimum setting to all Autopatch devices prior to this change. You may see missing Client State and Client Substate values if your devices are not configured with the recommended Windows Diagnostics settings and level. Alternatively, you may already be covered with existing data collection policies in your environment. TIP: You may want to consider using the Windows Autopatch Devices – All group which contains all of the active, registered devices presently in your Autopatch implementation across any and all Autopatch Groups. This is a service-managed group (subject to changes at any time). Not Registered devices will not appear in this Entra group.   Message ID: MC996580

The post Update to Windows Autopatch diagnostic data collection levels and removal of Windows Autopatch data collection policy appeared first on M365 Admin.