MC391866 – Reminder: Significant changes coming to the Windows Diagnostic data processor configuration

cloudscout.one Icon

*For this entry exists the more relevant or more recent entry MC406226

check before: 2022-07-01

Product:

Azure Active Directory, Microsoft Endpoint Manager, Priva, Windows

Platform:

Windows Desktop, World tenant

Status:

Change type:

Admin impact

Details:

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.

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.

Change Category:
XXXXXXX ...

Scope:
XXXXXXX ...

Release Phase:

Created:
2022-06-14

updated:
2022-08-27

the free basic plan is required to see all details. Sign up here


A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.


changes*

DatePropertyoldnew
2022-09-15MC prepareEnsure 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.
ps://blogs.microsoft.com/eupolicy/2021/05/06/eu-data-boundary/
ps://docs.microsoft.com/en-us/windows/privacy/changes-to-windows-diagnostic-data-collection#significant-changes-coming-to-the-windows-diagnostic-data-processor-confi
ps://docs.microsoft.com/en-us/windows/privacy/configure-windows-diagnostic-data-in-your-organiz
ps://docs.microsoft.com/en-us/windows-insider/flighting#dev-channel
ps://docs.microsoft.com/windows-insider/flighting#dev-channel
ps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FDPA&data=05%7C01%7CAlbert.Cabello%40microsoft.com%7C86bc5a1a771b4a74fc8508da4b0067e2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637904762393315046%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=viUXAaNDrNdTUmtzLYTPMwZdrohro%2BIkaDhRB31Yhlk%3D&reserved=0%22%20\t%20%22_blank
ps://privacy.microsoft.com/en-us/privacy
ps://privacy.microsoft.com/privacy
ps://review.docs.microsoft.com/en-us/managed-desktop/intro/
ps://review.docs.microsoft.com/en-us/mem/analytics/overvi
ps://review.docs.microsoft.com/en-us/windows/deployment/update/deployment-service-overvi
ps://review.docs.microsoft.com/en-us/windows/deployment/update/update-complianc
ps://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA
ps://www.microsoft.com/licensing/terms/product/Glossary/all
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.
https://blogs.microsoft.com/eupolicy/2021/05/06/eu-data-boundary/
https://docs.microsoft.com/en-us/windows/privacy/changes-to-windows-diagnostic-data-collection#significant-changes-coming-to-the-windows-diagnostic-data-processor-configuration
https://docs.microsoft.com/en-us/windows/privacy/configure-windows-diagnostic-data-in-your-organization
https://docs.microsoft.com/en-us/windows-insider/flighting#dev-channel
https://docs.microsoft.com/windows-insider/flighting#dev-channel
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FDPA&data=05%7C01%7CAlbert.Cabello%40microsoft.com%7C86bc5a1a771b4a74fc8508da4b0067e2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637904762393315046%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=viUXAaNDrNdTUmtzLYTPMwZdrohro%2BIkaDhRB31Yhlk%3D&reserved=0%22%20\t%20%22_blank
https://privacy.microsoft.com/en-US/privacystatement
https://privacy.microsoft.com/privacystatement
https://review.docs.microsoft.com/en-us/managed-desktop/intro/
https://review.docs.microsoft.com/en-us/mem/analytics/overview
https://review.docs.microsoft.com/en-us/windows/deployment/update/deployment-service-overview
https://review.docs.microsoft.com/en-us/windows/deployment/update/update-compliance-monitor
https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA
https://www.microsoft.com/licensing/terms/product/Glossary/all
2022-08-27MC prepareEnsure 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.
https://blogs.microsoft.com/eupolicy/2021/05/06/eu-data-boundary/
https://docs.microsoft.com/en-us/windows/privacy/changes-to-windows-diagnostic-data-collection#significant-changes-coming-to-the-windows-diagnostic-data-processor-configuration
https://docs.microsoft.com/en-us/windows/privacy/configure-windows-diagnostic-data-in-your-organization
https://docs.microsoft.com/en-us/windows-insider/flighting#dev-channel
https://docs.microsoft.com/windows-insider/flighting#dev-channel
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FDPA&data=05%7C01%7CAlbert.Cabello%40microsoft.com%7C86bc5a1a771b4a74fc8508da4b0067e2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637904762393315046%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=viUXAaNDrNdTUmtzLYTPMwZdrohro%2BIkaDhRB31Yhlk%3D&reserved=0%22%20\t%20%22_blank
https://privacy.microsoft.com/en-us/privacystatement
https://privacy.microsoft.com/privacystatement
https://review.docs.microsoft.com/en-us/managed-desktop/intro/
https://review.docs.microsoft.com/en-us/mem/analytics/overview
https://review.docs.microsoft.com/en-us/windows/deployment/update/deployment-service-overview
https://review.docs.microsoft.com/en-us/windows/deployment/update/update-compliance-monitor
https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA
https://www.microsoft.com/licensing/terms/product/Glossary/all
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.
ps://blogs.microsoft.com/eupolicy/2021/05/06/eu-data-boundary/
ps://docs.microsoft.com/en-us/windows/privacy/changes-to-windows-diagnostic-data-collection#significant-changes-coming-to-the-windows-diagnostic-data-processor-confi
ps://docs.microsoft.com/en-us/windows/privacy/configure-windows-diagnostic-data-in-your-organiz
ps://docs.microsoft.com/en-us/windows-insider/flighting#dev-channel
ps://docs.microsoft.com/windows-insider/flighting#dev-channel
ps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FDPA&data=05%7C01%7CAlbert.Cabello%40microsoft.com%7C86bc5a1a771b4a74fc8508da4b0067e2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637904762393315046%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=viUXAaNDrNdTUmtzLYTPMwZdrohro%2BIkaDhRB31Yhlk%3D&reserved=0%22%20\t%20%22_blank
ps://privacy.microsoft.com/en-us/privacy
ps://privacy.microsoft.com/privacy
ps://review.docs.microsoft.com/en-us/managed-desktop/intro/
ps://review.docs.microsoft.com/en-us/mem/analytics/overvi
ps://review.docs.microsoft.com/en-us/windows/deployment/update/deployment-service-overvi
ps://review.docs.microsoft.com/en-us/windows/deployment/update/update-complianc
ps://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA
ps://www.microsoft.com/licensing/terms/product/Glossary/all
2022-07-28MC prepareEnsure 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 Configure Windows diagnostic data in your organization documentation topic.
https://blogs.microsoft.com/eupolicy/2021/05/06/eu-data-boundary/
https://docs.microsoft.com/en-us/windows/privacy/configure-windows-diagnostic-data-in-your-organization
https://docs.microsoft.com/en-us/windows/privacy/configure-windows-diagnostic-data-in-your-organization?branch=dhb-privacy#significant-changes-coming-to-the-windows-diagnostic-data-processor-configuration
https://docs.microsoft.com/en-us/windows-insider/flighting#dev-channel
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FDPA&data=05%7C01%7CAlbert.Cabello%40microsoft.com%7C86bc5a1a771b4a74fc8508da4b0067e2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637904762393315046%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=viUXAaNDrNdTUmtzLYTPMwZdrohro%2BIkaDhRB31Yhlk%3D&reserved=0%22%20\t%20%22_blank
https://privacy.microsoft.com/en-us/privacystatement
https://privacy.microsoft.com/privacystatement
https://review.docs.microsoft.com/en-us/managed-desktop/intro/
https://review.docs.microsoft.com/en-us/mem/analytics/overview
https://review.docs.microsoft.com/en-us/windows/deployment/update/deployment-service-overview
https://review.docs.microsoft.com/en-us/windows/deployment/update/update-compliance-monitor
https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA
https://www.microsoft.com/licensing/terms/product/Glossary/all
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.
https://blogs.microsoft.com/eupolicy/2021/05/06/eu-data-boundary/
https://docs.microsoft.com/en-us/windows/privacy/changes-to-windows-diagnostic-data-collection#significant-changes-coming-to-the-windows-diagnostic-data-processor-configuration
https://docs.microsoft.com/en-us/windows/privacy/configure-windows-diagnostic-data-in-your-organization
https://docs.microsoft.com/en-us/windows-insider/flighting#dev-channel
https://docs.microsoft.com/windows-insider/flighting#dev-channel
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FDPA&data=05%7C01%7CAlbert.Cabello%40microsoft.com%7C86bc5a1a771b4a74fc8508da4b0067e2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637904762393315046%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=viUXAaNDrNdTUmtzLYTPMwZdrohro%2BIkaDhRB31Yhlk%3D&reserved=0%22%20\t%20%22_blank
https://privacy.microsoft.com/en-us/privacystatement
https://privacy.microsoft.com/privacystatement
https://review.docs.microsoft.com/en-us/managed-desktop/intro/
https://review.docs.microsoft.com/en-us/mem/analytics/overview
https://review.docs.microsoft.com/en-us/windows/deployment/update/deployment-service-overview
https://review.docs.microsoft.com/en-us/windows/deployment/update/update-compliance-monitor
https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA
https://www.microsoft.com/licensing/terms/product/Glossary/all
2022-07-28MC Last Updated06/13/2022 20:19:122022-07-27T23:13:14Z
2022-07-28MC MessagesWe’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 Configure Windows diagnostic data in your organization 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.

When will this happen:


This change will roll out initially to Windows devices enrolled in the Dev Channel of the Windows Insider program no earlier than July 2022. For other Windows devices (not in de Dev Channel), additional details on supported versions of Windows 11 and Windows 10 will be announced later. These changes will roll out no earlier than the last quarter of the calendar year 2022.
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.

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.
2022-07-28MC Action Required By07/01/2022 19:00:00
2022-07-28MC Start Time06/13/2022 20:19:112022-07-27T23:13:13Z
2022-07-28MC CategoryStay InformedPlan For Change
2022-07-28MC End Time07/01/2023 19:00:002023-07-27T23:13:13Z

*starting April 2022

Last updated 1 month ago

Login to your account

Welcome Back, We Missed You!