deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-19 12:23:37 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

added enterprise

Browse Source
This commit is contained in:
Dani Halfin
2020-07-22 15:37:23 -07:00
parent a6a754853f
commit 1567c14ac7
2 changed files with 23 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
windows/privacy/data-processor-service-for-windows-public-preview-terms.md
View File

@ -1,5 +1,5 @@
---
title: Data processor service for Windows public preview terms
title: Data processor service for Windows Enterprise public preview terms
description: Use this article to understand Windows public preview terms of service.
keywords: privacy, GDPR
ms.localizationpriority: high
@ -17,7 +17,7 @@ ms.collection:
- M365-security-compliance
---
# Data processor service for Windows public preview terms
# Data processor service for Windows Enterprise public preview terms
**These terms (“Terms”) must be read and accepted by a tenant admin with appropriate access rights and authority. By participating in this public preview, you: (a) agree to the following Terms, and (b) represent and warrant that you have such rights and authority.**

42
windows/privacy/deploy-data-processor-service-windows.md
View File

@ -1,6 +1,6 @@
---
title: Technical Deployment of the data processor service for Windows
description: Use this article to understand how to deploy and manage the data processor service for Windows.
title: Technical Deployment of the data processor service for Windows Enterprise
description: Use this article to understand how to deploy and manage the data processor service for Windows Enterprise.
keywords: privacy, GDPR
ms.localizationpriority: high
ROBOTS: NOINDEX, NOFOLLOW
@ -17,35 +17,35 @@ ms.collection:
- M365-security-compliance
---
# Data processor service for Windows Overview
# Data processor service for Windows Enterprise Overview
>[!NOTE]
>This topic is intended for participants in the data processor service for Windows preview program and requires acceptance of specific terms of use. To learn
>This topic is intended for participants in the data processor service for Windows Enterprise preview program and requires acceptance of specific terms of use. To learn
more about the program and agree to the terms of use, see [https://aka.ms/dpswpublicpreview](https://aka.ms/dpswpublicpreview).
The privacy landscape keeps evolving, and with it, we make changes to our services to meet our customers’ needs.
The data processor service for Windows empowers you to be in control of diagnostic data from Windows devices, and act as data controllers for that data, under the definition of the European Union General Data Protection Regulation (GDPR).
The data processor service for Windows Enterprise empowers you to be in control of diagnostic data from Windows devices, and act as data controllers for that data, under the definition of the European Union General Data Protection Regulation (GDPR).
The data processor service for Windows will serve as a foundation for other Microsoft services that use Windows diagnostic data.
The data processor service for Windows Enterprise will serve as a foundation for other Microsoft services that use Windows diagnostic data.
The data processor service for Windows offering enables you to store and manage your Windows diagnostic data in the cloud, on top of an end-to-end data platform designed and built with compliance in mind, to help you meet your compliance obligations.
The data processor service for Windows Enterprise offering enables you to store and manage your Windows diagnostic data in the cloud, on top of an end-to-end data platform designed and built with compliance in mind, to help you meet your compliance obligations.
Your data is routed and stored inside an enterprise compliance boundary, operating under a prescriptive and focused set of compliance requirements, in accordance with industry standards.
The data processor service for Windows provides you with controls that help respond to delete data subject requests (DSRs) on diagnostic data, at user account closure, for a specific Azure AD User ID. Additionally, you’re able to execute an export DSR for a specific Azure AD User ID.
Should you desire so, Microsoft will accommodate a data processor service for Windows tenant account closure, either because you decide to close your Azure or Azure AD tenant account, or because you decide you no longer wish to be the data controller for diagnostic data, but still wish to remain an Azure customer.
The data processor service for Windows Enterprise provides you with controls that help respond to delete data subject requests (DSRs) on diagnostic data, at user account closure, for a specific Azure AD User ID. Additionally, you’re able to execute an export DSR for a specific Azure AD User ID.
Should you desire so, Microsoft will accommodate a data processor service for Windows Enterprise tenant account closure, either because you decide to close your Azure or Azure AD tenant account, or because you decide you no longer wish to be the data controller for diagnostic data, but still wish to remain an Azure customer.
>[!Note]
>Tenant account closure will lead to the deletion of all data associated with that tenant.
## Deployment of data processor service for Windows
Use the instructions below to easily manage the data processor service for Windows using a single setting, through Group Policy, or an MDM solution, in Windows 10, version 1809 or Windows Server 2019 and newer.
## Deployment of data processor service for Windows Enterprise
Use the instructions below to easily manage the data processor service for Windows Enterprise using a single setting, through Group Policy, or an MDM solution, in Windows 10, version 1809 or Windows Server 2019 and newer.
### Prerequisites
#### Versions supported
The data processor service for Windows is currently supported on Windows 10, version 1809, and newer versions.
The data processor service for Windows Enterprise is currently supported on Windows 10, version 1809, and newer versions.
#### Network requirements
The following endpoints need to be reachable from devices enrolled into the data processor service for Windows:
The following endpoints need to be reachable from devices enrolled into the data processor service for Windows Enterprise:
login.live.com
@ -61,14 +61,14 @@ For additional information, see the “device authentication” and “diagnosti
[Windows 10, version 1903 endpoints](https://docs.microsoft.com/Windows/privacy/manage-Windows-1903-endpoints)
### Deploying data processor service for Windows
You can use either Group Policy or an MDM solution to deploy the data processor service for Windows to your supported devices.
### Deploying data processor service for Windows Enterprise
You can use either Group Policy or an MDM solution to deploy the data processor service for Windows Enterprise to your supported devices.
In Group Policy, to enable data collection through the data processor service for Windows, go to **Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds** and switch the **Allow commercial data pipeline** setting to **enabled**.
In Group Policy, to enable data collection through the data processor service for Windows Enterprise, go to **Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds** and switch the **Allow commercial data pipeline** setting to **enabled**.
If you wish to disable, at any time, switch the same setting to **disabled**. The default state of the above setting is **disabled**.
To use an MDM solution, such as [Microsoft Intune](https://docs.microsoft.com/intune/custom-settings-Windows-10), to deploy the data processor service for Windows to your supported devices, use the following custom OMA-URI setting configuration:
To use an MDM solution, such as [Microsoft Intune](https://docs.microsoft.com/intune/custom-settings-Windows-10), to deploy the data processor service for Windows Enterprise to your supported devices, use the following custom OMA-URI setting configuration:
- **Name:** System/AllowCommercialDataPipeline
- **OMA-URI:** ./Vendor/MSFT/Policy/Config/System/AllowCommercialDataPipeline
@ -79,11 +79,11 @@ Under **Value**, use **1** to enable the service.
If you wish to disable, at any time, switch the same setting to **0** to disable. The default is **0**.
>[!Note]
>Data collected from a device, before it was enrolled into the data processor service for Windows, will not be moved into the enterprise compliance boundary.
>Data collected from a device, before it was enrolled into the data processor service for Windows Enterprise, will not be moved into the enterprise compliance boundary.
## Managing data processor service for Windows
## Managing data processor service for Windows Enterprise
### Executing user-based data subject requests (DSRs)
To perform user-based DSRs, the data processor service for Windows requires your organization to be reflected in Azure AD.
To perform user-based DSRs, the data processor service for Windows Enterprise requires your organization to be reflected in Azure AD.
If your environment is cloud-only and managed in Azure, or all your devices are Azure AD joined - you don’t need to take any further action.
@ -93,4 +93,4 @@ To learn more, visit [How To: Plan your hybrid Azure Active Directory join imple
Once you have Azure AD join or hybrid Azure AD join in place, you can learn more about executing user-based DSRs, by visiting this [page](https://review.docs.microsoft.com/microsoft-365/compliance/gdpr-dsr-windows?branch=siosulli-wps&view=o365-worldwide).
## Geo-location
Windows Diagnostic Data collected through the data processor service for Windows is hosted in our datacenter in the United States.
Windows Diagnostic Data collected through the data processor service for Windows Enterprise is hosted in our datacenter in the United States.