6.0 KiB
title, description, keywords, ms.localizationpriority, ROBOTS, ms.prod, ms.topic, f1.keywords, ms.author, author, manager, audience, ms.collection
| title | description | keywords | ms.localizationpriority | ROBOTS | ms.prod | ms.topic | f1.keywords | ms.author | author | manager | audience | ms.collection | |||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Technical Deployment of the data processor service for Windows | Use this article to understand how to deploy and manage the data processor service for Windows. | privacy, GDPR | high | NOINDEX, NOFOLLOW | w10 | article |
|
daniha | DaniHalfin | dansimp | itpro |
|
Data processor service for Windows 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 more about the program and agree to the terms of use, see 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 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. 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.
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.
Prerequisites
Versions supported
The data processor service for Windows 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:
login.live.com
cy2.vortex.data.microsoft.com.akadns.net
v10.events.data.microsoft.com
v10.vortex-win.data.microsoft.com/collect/v1
For additional information, see the “device authentication” and “diagnostic data” sections in the endpoint articles for each respective Windows version:
Windows 10, version 1809 endpoints
Windows 10, version 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.
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.
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, to deploy the data processor service for Windows to your supported devices, use the following custom OMA-URI setting configuration:
- Name: System/AllowCommercialDataPipeline
- OMA-URI: ./Vendor/MSFT/Policy/Config/System/AllowCommercialDataPipeline
- Data type: Integer
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.
Managing data processor service for Windows
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.
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.
If your environment uses on-premises Active Directory to manage identities - Azure AD Connect synchronization is required, and your environment needs to be configured for hybrid Azure AD join. To learn more, visit How To: Plan your hybrid Azure Active Directory join implementation and Azure AD Connect sync: Understand and customize synchronization.
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.
Geo-location
Windows Diagnostic Data collected through the data processor service for Windows is hosted in our datacenter in the United States.