We’re introducing a significant change for enterprise Windows devices that have diagnostic data turned on. We will stop using policies to configure this option and introduce an organization-wide configuration based on Azure Active Directory (Azure AD) to determine Microsoft’s role in the data processing. This change will start with devices enrolled in the Dev Channel of the Windows Insider program no earlier than July 2022 and for supported versions of Windows 11 and Windows 10 no earlier than the last quarter of the calendar year 2022.
For details on these changes and how to enable the Windows diagnostic data processor configuration option, see Significant changes coming to the Windows diagnostic data processor configuration documentation topic.
Currently, to enroll devices in the Window diagnostic data processor configuration option, IT admins can use policies, such as the “Allow commercial data pipeline” policy at the individual device level. To enable efficiencies and help us implement our plan to store and process EU Data in the EU, we’ll stop using policies, such as the “Allow commercial data pipeline” policy, to configure the processor option. Instead, we’ll be introducing an organization-wide configuration based on Azure Active Directory (Azure AD) to determine Microsoft’s role in the data processing.
We’re making this change to help ensure the diagnostic data for all devices in an organization is processed in a consistent way, and in the same geographic region.
Involve Workload
- Azure Active Directory
- Microsoft Endpoint Manager
- Priva
- Windows
When will this happen
This change is releasing to Windows devices enrolled in the Dev Channel of the Windows Insider program the week of July 24, 2022. Any Windows build on or after 25169 will contain the changes. For other Windows devices (not in the Dev Channel), additional details on supported versions of Windows 11 and Windows 10 will be announced at a later date. These changes will roll out no earlier than the last quarter of the calendar year 2022.
What you need to do to prepare
Ensure that you meet the prerequisites for Windows diagnostic data processor configuration, join your devices to Azure AD, and keep your devices secure and up to date with quality updates. If you’re outside of the EU or EFTA, the organization must sign up for any of the following enterprise services:
- Update Compliance
- Windows Update for Business deployment service
- Microsoft Managed Desktop
- Endpoint analytics (in Microsoft Endpoint Manager)
- (Additional licensing requirements may apply to use these services.)
If you don’t sign up for any of these enterprise services, Microsoft will act as the controller for the diagnostic data.
Note: In all cases, enrollment in the Windows diagnostic data processor configuration requires a device to be joined to an Azure AD tenant. If a device is not properly enrolled, Microsoft will be the controller of diagnostic data processed in connection with Windows in accordance with the Microsoft Privacy Statement (aka.ms/privacy), and the Data Protection Addendum (aka.ms/DPA) terms will not apply.
Additional information
For details on these changes and how to enable the Windows diagnostic data processor configuration option, see Significant changes coming to the Windows diagnostic data processor configuration documentation topic.
- Answering Europe’s Call: Storing and Processing EU Data in the EU
- Significant changes coming to the Windows diagnostic data processor configuration
- Configure Windows diagnostic data in your organization
- Dev Channel
- Microsoft Products and Services Data Protection Addendum (DPA)
- Microsoft Privacy Statement
Message ID: MC391866
Published: 14 June 2022
Updated: 28 July 2022
Action required by: 01 July 2022
Platform: Windows Desktop, World tenant
