From 847ee5aa9ae747857a36fb1c0b13cf8c26b00f39 Mon Sep 17 00:00:00 2001 From: "Daniel H. Brown" <32883970+DHB-MSFT@users.noreply.github.com> Date: Thu, 29 May 2025 13:03:04 -0700 Subject: [PATCH] Freshness updates to "configure" article - URLs - PM feedback - Acrolinx --- ...ws-diagnostic-data-in-your-organization.md | 56 +++++++++---------- 1 file changed, 28 insertions(+), 28 deletions(-) diff --git a/windows/privacy/configure-windows-diagnostic-data-in-your-organization.md b/windows/privacy/configure-windows-diagnostic-data-in-your-organization.md index e367317ea5..88b38e45d8 100644 --- a/windows/privacy/configure-windows-diagnostic-data-in-your-organization.md +++ b/windows/privacy/configure-windows-diagnostic-data-in-your-organization.md @@ -7,7 +7,7 @@ ms.localizationpriority: high author: DHB-MSFT ms.author: danbrown manager: dansimp -ms.date: 03/11/2016 +ms.date: 05/29/2025 ms.topic: how-to ms.collection: - privacy-windows @@ -26,7 +26,7 @@ ms.collection: - Windows 10 Professional - Windows Server 2016 and later - Surface Hub -- Hololens +- HoloLens This article describes the types of Windows diagnostic data sent back to Microsoft and the ways you can manage it within your organization. Microsoft uses the data to quickly identify and address issues affecting its customers. @@ -34,7 +34,7 @@ This article describes the types of Windows diagnostic data sent back to Microso Microsoft collects Windows diagnostic data to solve problems and to keep Windows up to date, secure, and operating properly. It also helps us improve Windows and related Microsoft products and services and, for customers who have turned on the **Tailored experiences** setting, to provide more relevant tips and recommendations to enhance Microsoft and third-party products and services for each customer’s needs. -For more information about how Windows diagnostic data is used, see [Diagnostics, feedback, and privacy in Windows](https://support.microsoft.com/help/4468236/diagnostics-feedback-and-privacy-in-windows-10-microsoft-privacy). +For more information about how Windows diagnostic data is used, see [Diagnostics, feedback, and privacy in Windows](https://support.microsoft.com/windows/28808a2b-a31b-dd73-dcd3-4559a5199319). ### Diagnostic data gives users a voice @@ -48,13 +48,13 @@ For example, in an earlier version of Windows there was a version of a video dri ### _Improve end-user productivity_ -Windows diagnostic data also helps Microsoft better understand how customers use (or do not use) the operating system’s features and related services. The insights we gain from this data helps us prioritize our engineering effort to directly impact our customers’ experiences. These examples show how the use of diagnostic data enables Microsoft to build or enhance features which can help organizations increase employee productivity while lowering help desk calls. +Windows diagnostic data also helps Microsoft better understand how customers use (or don't use) the operating system’s features and related services. The insights we gain from this data helps us prioritize our engineering effort to directly impact our customers’ experiences. These examples show how the use of diagnostic data enables Microsoft to build or enhance features which can help organizations increase employee productivity while lowering help desk calls. - **Start menu.** How do people change the Start menu layout? Do they pin other apps to it? Are there any apps that they frequently unpin? We use this dataset to adjust the default Start menu layout to better reflect people’s expectations when they turn on their device for the first time. - **Cortana.** We use diagnostic data to monitor the scalability of our cloud service, improving search performance. -- **Application switching.** Research and observations from earlier Windows versions showed that people rarely used Alt+Tab to switch between apps. After discussing this with some users, we learned they loved the feature, saying that it would be highly productive, but they did not know about it previously. Based on this, we created the Task View button in Windows to make this feature more discoverable. Later diagnostic data showed significantly higher usage of this feature. +- **Application switching.** Research and observations from earlier Windows versions showed that people rarely used Alt+Tab to switch between apps. After discussing this with some users, we learned they loved the feature, saying that it would be highly productive, but they didn't know about it previously. Based on this, we created the Task View button in Windows to make this feature more discoverable. Later diagnostic data showed significantly higher usage of this feature. ## How Microsoft handles diagnostic data @@ -72,7 +72,7 @@ Depending on the diagnostic data settings on the device, diagnostic data can be Later in this document we provide further details about how to control what’s collected and what data can be included in these different types of diagnostic data. -As of March 6, 2024, Microsoft Edge diagnostic data is collected separately from Windows diagnostic data on Windows 10 (version 22H2 and newer) and Windows 11 (version 23H2 and newer) devices in the European Economic Area. The collection of Microsoft Edge diagnostic data is subject to its own settings. For more information related to this change, see [Microsoft Edge, browsing data, and privacy](https://support.microsoft.com/windows/bb8174ba-9d73-dcf2-9b4a-c582b4e640dd). +As of March 6, 2024, Microsoft Edge diagnostic data is collected separately from Windows diagnostic data on Windows 10 (version 22H2 and newer) and Windows 11 (version 23H2 and newer) devices in the European Economic Area. The collection of Microsoft Edge diagnostic data is subject to its own settings. For more information related to this change, see [Microsoft Edge, browsing data, and privacy](https://support.microsoft.com/microsoft-edge/bb8174ba-9d73-dcf2-9b4a-c582b4e640dd). ### Data transmission @@ -86,9 +86,9 @@ The following table lists the endpoints related to how you can manage the collec | - | - | |Connected User Experiences and Telemetry | v10.events.data.microsoft.com

v10c.events.data.microsoft.com

v10.vortex-win.data.microsoft.com | | [Windows Error Reporting](/windows/win32/wer/windows-error-reporting) | watson.telemetry.microsoft.com

umwatsonc.events.data.microsoft.com

*-umwatsonc.events.data.microsoft.com

ceuswatcab01.blob.core.windows.net

ceuswatcab02.blob.core.windows.net

eaus2watcab01.blob.core.windows.net

eaus2watcab02.blob.core.windows.net

weus2watcab01.blob.core.windows.net

weus2watcab02.blob.core.windows.net | -|Authentication | login.live.com



IMPORTANT: This endpoint is used for device authentication. We do not recommend disabling this endpoint.| +|Authentication | login.live.com



IMPORTANT: This endpoint is used for device authentication. We don't recommend disabling this endpoint.| | [Online Crash Analysis](/windows/win32/dxtecharts/crash-dump-analysis) | oca.telemetry.microsoft.com

oca.microsoft.com

kmwatsonc.events.data.microsoft.com

*-kmwatsonc.events.data.microsoft.com | -|Settings | settings-win.data.microsoft.com



IMPORTANT: This endpoint is required to remotely configure diagnostics-related settings and data collection. For example, we use the settings endpoint to remotely block an event from being sent back to Microsoft, or to enroll a device in the Windows diagnostic data processor configuration. Do not block access to this endpoint. This endpoint does not upload Windows diagnostic data. | +|Settings | settings-win.data.microsoft.com



IMPORTANT: This endpoint is required to remotely configure diagnostics-related settings and data collection. For example, we use the settings endpoint to remotely block an event from being sent back to Microsoft, or to enroll a device in the Windows diagnostic data processor configuration. Don't block access to this endpoint. This endpoint doesn't upload Windows diagnostic data. | ### Proxy server authentication @@ -109,7 +109,7 @@ Configure devices to use the signed-in user's context for proxy authentication. - Make sure that the users have proxy permission to reach the diagnostic data endpoints. This option requires that the devices have console users with proxy permissions, so you can't use this method with headless devices. > [!IMPORTANT] -> The user proxy authentication approach is incompatible with the use of Microsoft Defender for Endpoint. This behavior is because this authentication relies on the **DisableEnterpriseAuthProxy** registry key set to `0`, while Microsoft Defender for Endpoint requires it to be set to `1`. For more information, see [Configure machine proxy and internet connectivity settings in Microsoft Defender for Endpoint](/windows/security/threat-protection/windows-defender-atp/configure-proxy-internet-windows-defender-advanced-threat-protection). +> The user proxy authentication approach is incompatible with the use of Microsoft Defender for Endpoint. This behavior is because this authentication relies on the **DisableEnterpriseAuthProxy** registry key set to `0`, while Microsoft Defender for Endpoint requires it to be set to `1`. For more information, see [Configure your devices to connect to the Defender for Endpoint service using a proxy](/defender-endpoint/configure-proxy-internet). #### Device proxy authentication @@ -139,11 +139,11 @@ This approach is the most complex because it requires the following configuratio ### Data access -The principle of least privileged access guides access to Windows diagnostic data. Microsoft does not share personal data of our customers with third parties, except at the customer’s discretion or for the limited purposes described in the [Privacy Statement](https://www.microsoft.com/privacy/privacystatement). Microsoft may share business reports with hardware manufacturers and third-party partners that include aggregated and deidentified diagnostic data information. Data-sharing decisions are made by an internal team including privacy, legal, and data management. +The principle of least privileged access guides access to Windows diagnostic data. Microsoft doesn't share personal data of our customers with third parties, except at the customer’s discretion or for the limited purposes described in the [Microsoft Privacy Statement](https://www.microsoft.com/privacy/privacystatement). Microsoft may share business reports with hardware manufacturers and third-party partners that include aggregated and deidentified diagnostic data information. Data-sharing decisions are made by an internal team including privacy, legal, and data management. ### Retention -Microsoft believes in and practices data minimization. We strive to gather only the info we need and to store it only for as long as it’s needed to provide a service or for analysis. For more information on how long data is retained, see the section named **Our retention of personal data** in the [Microsoft Privacy Statement](https://www.microsoft.com/privacy/privacystatement). +Microsoft believes in and practices data minimization. We strive to gather only the info we need and to store it only for as long as it’s needed to provide a service or for analysis. For more information on how long data is retained, see the section named **Our retention of personal data** in the [Microsoft Privacy Statement](https://www.microsoft.com/privacy/privacystatement#mainOurretentionofpersonaldatamodule). ## Diagnostic data settings @@ -151,7 +151,7 @@ There are four diagnostic data collection settings. Each setting is described in - Diagnostic data off (Security) - Required diagnostic data (Basic) -- Enhanced (This setting is only available on devices running Windows 10, Windows Server 2016, and Windows Server 2019.) +- Enhanced (This setting is only available on devices running Windows 10 version 1809 and earlier, Windows Server 2016, and Windows Server 2019.) - Optional diagnostic data (Full) Here’s a summary of the types of data that is included with each setting: @@ -172,13 +172,13 @@ This setting was previously labeled as **Security**. When you configure this set This was the default setting for Windows Server 2022 Datacenter: Azure Edition prior to December 13, 2022. >[!NOTE] -> If your organization relies on Windows Update, the minimum recommended setting is **Required diagnostic data**. Because no Windows Update information is collected when diagnostic data is off, important information about update failures is not sent. Microsoft uses this information to fix the causes of those failures and improve the quality of our updates. +> If your organization relies on Windows Update, the minimum recommended setting is **Required diagnostic data**. Because no Windows Update information is collected when diagnostic data is off, important information about update failures isn't sent. Microsoft uses this information to fix the causes of those failures and improve the quality of our updates. ### Required diagnostic data Required diagnostic data, previously labeled as **Basic**, gathers a limited set of data that’s critical for understanding the device and its configuration. This data helps to identify problems that can occur on a specific hardware or software configuration. For example, it can help determine if crashes are more frequent on devices with a specific amount of memory or that are running a specific driver version. -This is the default setting for current releases of Windows, Windows 10, version 1903. Beginning December 13, 2022, it is also the default setting for Windows Server 2022 Datacenter: Azure Edition. +This is the default setting for Windows 10, version 1903 and later. Beginning December 13, 2022, it's also the default setting for Windows Server 2022 Datacenter: Azure Edition. Required diagnostic data includes: @@ -208,10 +208,10 @@ Required diagnostic data includes: ### Enhanced diagnostic data -In Windows 10 and Windows Server 2019, enhanced diagnostic data includes data about the websites you browse, how Windows and apps are used and how they perform, and device activity. The additional data helps Microsoft to fix and improve products and services for all users. +In Windows 10 (version 1809 and earlier) and Windows Server 2019, enhanced diagnostic data includes data about the websites you browse, how Windows and apps are used and how they perform, and device activity. The additional data helps Microsoft to fix and improve products and services for all users. >[!Important] ->This diagnostic data setting is not available on Windows 11 and Windows Server 2022 and has been replaced with policies that can control the amount of optional diagnostic data that is sent. More information on these settings are available in the **Manage diagnostic data using Group Policy and MDM** section of this topic. +>This diagnostic data setting is not available on Windows 11 and Windows Server 2022 and has been replaced with policies that can control the amount of optional diagnostic data that is sent. More information on these settings are available in the [Manage diagnostic data using Group Policy and MDM](#manage-diagnostic-data-using-group-policy-and-mdm) section of this article. When you choose to send enhanced diagnostic data, required diagnostic data will always be included, and we collect the following additional information: @@ -245,7 +245,7 @@ Optional diagnostic data, previously labeled as **Full**, includes more detailed Use the steps in this section to configure the diagnostic data settings for Windows and Windows Server in your organization. >[!IMPORTANT] ->These diagnostic data settings only apply to components, features, and apps that are considered a part of the Windows operating system. Third-party apps and other Microsoft apps, such as Microsoft Office, that customers install may also collect and send diagnostic data using their own controls. You should work with your app vendors to understand their diagnostic data policy, and how you can opt in or opt out. For more information on how Microsoft Office uses diagnostic data, see [Overview of privacy controls for Microsoft 365 Apps for enterprise](/deployoffice/privacy/overview-privacy-controls). If you would like to control Windows data collection that is not Windows diagnostic data, see [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md). +>These diagnostic data settings only apply to components, features, and apps that are considered a part of the Windows operating system. Third-party apps and other Microsoft apps, such as Microsoft Office, that customers install may also collect and send diagnostic data using their own controls. You should work with your app vendors to understand their diagnostic data policy, and how you can opt in or opt out. For more information on how Microsoft Office uses diagnostic data, see [Overview of privacy controls for Microsoft 365 Apps for enterprise](/microsoft-365-apps/privacy/overview-privacy-controls). If you would like to control Windows data collection that isn't Windows diagnostic data, see [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md). You can configure your device's diagnostic data settings using the management tools you’re already using, such as Group Policy or MDM. @@ -267,12 +267,12 @@ You can use Group Policy to set your organization’s diagnostic data setting: 1. From the Group Policy Management Console, go to **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Data Collection and Preview Builds**. -2. Double-click **Allow Telemetry** (or **Allow diagnostic data** on Windows 11 and Windows Server 2022). +2. Double-click **Allow diagnostic data** (or **Allow telemetry** on Windows 10 version 1809 and earlier and on Windows Server 2019). > [!NOTE] > If devices in your organization are running Windows 10, 1803 and later, the user can still use Settings to set the diagnostic data setting to a more restrictive value, unless the **Configure diagnostic data opt-in settings user interface** policy is set. -3. In the **Options** box, choose the setting that you want to configure, and then click **OK**. +3. In the **Options** box, choose the setting that you want to configure, and then select **OK**. ### Use Group Policy to manage optional diagnostic data collection @@ -283,15 +283,15 @@ The following policy lets you limit the types of [crash dumps](/windows/win32/dx 2. Double-click **Limit dump collection**. -3. In the **Options** box, choose the setting that you want to configure, and then click **OK**. +3. In the **Options** box, choose the setting that you want to configure, and then select **OK**. -You can also limit the number of diagnostic logs that are sent back to Microsoft. If this policy is enabled, diagnostic logs are not sent back to Microsoft. +You can also limit the number of diagnostic logs that are sent back to Microsoft. If this policy is enabled, diagnostic logs aren't sent back to Microsoft. 1. From the Group Policy Management Console, go to **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Data Collection and Preview Builds**. 2. Double-click **Limit diagnostic log collection**. -3. In the **Options** box, choose the setting that you want to configure, and then click **OK**. +3. In the **Options** box, choose the setting that you want to configure, and then select **OK**. ### Use MDM to manage diagnostic data collection @@ -339,8 +339,8 @@ Tenants with billing addresses in countries or regions in the Middle East and Af > [!NOTE] > The information in this section applies to the following versions of Windows: -> - Windows 10, versions 20H2, 21H2, 22H2, and newer -> - Windows 11, versions 21H2, 22H2, 23H2, and newer +> - Windows 10, versions 20H2 and newer +> - Windows 11, versions 21H2 and newer Starting with the January 2023 preview cumulative update, how you enable the processor configuration option depends on the billing address of the Azure AD tenant to which your devices are joined. @@ -356,7 +356,7 @@ For Windows devices with diagnostic data turned on and that are joined to an [Az - [Windows Update for Business reports](/windows/deployment/update/wufb-reports-overview) - [Windows Autopatch](/windows/deployment/windows-autopatch/overview/windows-autopatch-overview) -- [Windows updates reports (in Microsoft Intune)](/mem/intune/protect/data-enable-windows-data#windows-data) +- [Windows updates reports (in Microsoft Intune)](/intune/intune-service/protect/data-enable-windows-data#windows-data) *(Additional licensing requirements may apply to use these services.)* @@ -367,15 +367,15 @@ If you don’t sign up for any of these enterprise services, Microsoft will act > [!NOTE] > The information in this section applies to the following versions of Windows: > - Windows 10, versions 1809, 1903, 1909, and 2004. -> - Newer versions of Windows 10 and Windows 11 that have not updated yet to at least the January 2023 preview cumulative update. +> - Newer versions of Windows 10 and Windows 11 that haven't updated yet to at least the January 2023 preview cumulative update. To enable Windows diagnostic data processor configuration, you can use Group Policy or a custom setting in an MDM solution, such as Microsoft Intune. -- For Group Policy, you can use the “Allow commercial data pipeline” policy, which is also available in the Intune [settings catalog](/mem/intune/configuration/settings-catalog). +- For Group Policy, you can use the "Allow commercial data pipeline" policy, which is also available in the Intune [settings catalog](/intune/intune-service/configuration/settings-catalog). - For an MDM solution, you can use the AllowCommercialDataPipeline setting in the System Policy configuration service provider (CSP). For more information about AllowCommercialDataPipeline and the “Allow commercial data pipeline” policy, [review this information](/windows/client-management/mdm/policy-csp-system#allowcommercialdatapipeline). ## Change privacy settings on a single server -You can also change the privacy settings on a server running either the Azure Stack HCI operating system or Windows Server. For more information, see [Change privacy settings on individual servers](/azure-stack/hci/manage/change-privacy-settings). +You can also change the privacy settings on a server running either the Azure Stack HCI operating system or Windows Server. For more information, see [Change privacy settings on individual servers](/azure/azure-local/manage/change-privacy-settings).