---
title: Get started with Update Compliance (Windows 10)
description: Explains how to configure Update Compliance.
ms.prod: w10
ms.mktglfcycl: deploy
ms.sitesec: library
ms.pagetype: deploy
author: greg-lindsay
---

# Get started with Update Compliance

This topic explains the steps necessary to configure your environment for Windows Analytics: Update Compliance. 

Steps are provided in sections that follow the recommended setup process:
1.	Ensure that [prerequisites](#update-compliance-prerequisites) are met.
2.	[Add Update Compliance](#add-update-compliance-to-microsoft-operatiions-management-suite) to Microsoft Operations Management Suite
3.	[Deploy your Commercial ID](#deploy-your-commercial-id-to-your-windows-10-devices) to your organization’s devices

## Update Compliance Prerequisites

Update Compliance has the following requirements: 
1. Update Compliance is currently only compatible with Windows 10 devices. The solution is intended to be used with desktop devices (Windows 10 workstations and laptops). 
2. The solution requires that Windows 10 telemetry is enabled on all devices that are intended to be displayed in the solution. These devices must have at least the [basic level of telemetry](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization#basic-level) enabled. To learn more about Windows telemetry, see [Configure Windows telemetry in your organization](configure-windows-telemetry-in-your-organization.md). 
3. The telemetry of your organization’s Windows devices must be successfully transmitted to Microsoft. Microsoft has specified [endpoints for different aspects of telemetry](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization#endpoints), which must be whitelisted by your organization so the data can be transmitted. The following table is taken from the article on telemetry endpoints and summarizes the use of each endpoint:

    <TABLE BORDER=1>
    <TR><TD BGCOLOR="#cceeff">Service<TD BGCOLOR="#cceeff">Endpoint
    <TR><TD>Connected User Experience and Telemetry component<TD>v10.vortex-win.data.microsoft.com
    <BR>settings-win.data.microsoft.com
    <TR><TD>Windows Error Reporting	<TD>watson.telemetry.microsoft.com
    <TR><TD>Online Crash Analysis	<TD>oca.telemetry.microsoft.com
    </TABLE>

## Add Update Compliance to Microsoft Operations Management Suite

Update Compliance is offered as a solution in the Microsoft Operations Management Suite (OMS), a collection of cloud-based servicing for monitoring and automating your on-premises and cloud environments. For more information about OMS, see [Operations Management Suite overview](https://azure.microsoft.com/en-us/documentation/articles/operations-management-suite-overview/). 

If you are already using OMS, you’ll find Update Compliance in the Solutions Gallery. Select the **Update Compliance** tile in the gallery and then click **Add** on the solution's details page. Update Compliance is now visible in your workspace.

If you are not yet using OMS, use the following steps to subscribe to OMS Update Compliance:

1.	Go to [Operations Management Suite’s page](https://www.microsoft.com/en-us/cloud-platform/operations-management-suite) on Microsoft.com and click **Sign in**.

    <P><TABLE BORDER=1><TR><TD>
    <A HREF="images/uc-02.png"><img src="images/uc-02a.png"></A>
    <TABLE>

2.	Sign in to Operations Management Suite (OMS). You can use either a Microsoft Account or a Work or School account to create a workspace. If your company is already using Azure Active Directory (Azure AD), use a Work or School account when you sign in to OMS. Using a Work or School account allows you to use identities from your Azure AD to manage permissions in OMS.

    <P><TABLE BORDER=1><TR><TD>
    <A HREF="images/uc-03.png"><img src="images/uc-03a.png"></A>
    <TABLE>

3.	Create a new OMS workspace. 

    <P><TABLE BORDER=1><TR><TD>
    <A HREF="images/uc-04.png"><img src="images/uc-04a.png"></A>
    <TABLE>

4.	Enter a name for the workspace, select the workspace region, and provide the email address that you want associated with this workspace. Click **Create**.

    <P><TABLE BORDER=1><TR><TD>
    <A HREF="images/uc-05.png"><img src="images/uc-05a.png"></A>
    <TABLE>

5.	If your organization already has an Azure subscription, you can link it to your workspace. Note that you may need to request access from your organization’s Azure administrator. If your organization does not have an Azure subscription, create a new one or select the default OMS Azure subscription from the list. If you do not yet have an Azure subscription, follow [this guide](https://blogs.technet.microsoft.com/upgradeanalytics/2016/11/08/linking-operations-management-suite-workspaces-to-microsoft-azure/) to create and link an Azure subscription to an OMS workspace.

    <P><TABLE BORDER=1><TR><TD>
    <A HREF="images/uc-06.png"><img src="images/uc-06a.png"></A>
    <TABLE>

6.	To add the Update Compliance solution to your workspace, go to the Solutions Gallery.

    <P><TABLE BORDER=1><TR><TD>
    <A HREF="images/uc-07.png"><img src="images/uc-07a.png"></A>
    <TABLE>

7.	Select the **Update Compliance** tile in the gallery and then select **Add** on the solution’s details page. You might need to scroll to find **Update Compliance**. The solution is now visible on your workspace. 

    <P><TABLE BORDER=1><TR><TD>
    <A HREF="images/uc-08.png"><img src="images/uc-08a.png"></A>
    <TABLE>

8.	Click the **Update Compliance** tile to configure the solution. The **Settings Dashboard** opens.

    <P><TABLE BORDER=1><TR><TD>
    <A HREF="images/uc-09.png"><img src="images/uc-09a.png"></A>
    <TABLE>

9.	Click **Subscribe** to subscribe to OMS Update Compliance. You will then need to distribute your Commercial ID across all your organization’s devices. More information on the Commercial ID is provided below.

    <P><TABLE BORDER=1><TR><TD>
    <A HREF="images/uc-10.png"><img src="images/uc-10a.png"></A>
    <TABLE>

After you are subscribed to OMS Update Compliance and your devices have a Commercial ID, you will begin receiving data. It will typically take 24 hours for the first data to begin appearing. The following section explains how to deploy your Commercial ID to your Windows 10 devices.

>You can unsubscribe from the Update Compliance solution if you no longer want to monitor your organization’s devices. User device data will continue to be shared with Microsoft while the opt-in keys are set on user devices and the proxy allows traffic.

## Deploy your Commercial ID to your Windows 10 devices

In order for your devices to show up in Windows Analytics: Update Compliance, they must be configured with your organization’s Commercial ID. This is so that Microsoft knows that a given device is a member of your organization and to feed that device’s data back to you. There are two primary methods for widespread deployment of your Commercial ID: Group Policy and Mobile Device Management (MDM). 

- Using Group Policy<BR><BR>
    Deploying your Commercial ID using Group Policy can be accomplished by configuring domain Group Policy Objects with the Group Policy Management Editor, or by configuring local Group Policy using the Local Group Policy Editor.
    1. In the console tree, navigate to **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Data Collection and Preview Builds**
    2. Double-click **Configure the Commercial ID**
    3. In the **Options** box, under **Commercial Id**, type the Commercial ID GUID, and then click **OK**.<P>

- Using Microsoft Mobile Device Management (MDM)<BR><BR>
    Microsoft’s Mobile Device Management can be used to deploy your Commercial ID to your organization’s devices. The Commercial ID is listed under **Provider/ProviderID/CommercialID**. More information on deployment using MDM can be found [here](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/dmclient-csp). 
    
    For information on how to use MDM configuration CSPs, see [Introduction to configuration service providers (CSPs) for IT pros](https://technet.microsoft.com/en-us/itpro/windows/manage/how-it-pros-can-use-configuration-service-providers).

    When using the Intune console, you can use the OMA-URI settings of a [custom policy](https://go.microsoft.com/fwlink/p/?LinkID=616316) to configure the commercial ID. The OMA-URI (case sensitive) path for configuring the commerical ID is: <PRE>./Vendor/MSFT/DMClient/Provider/ProviderID/CommercialID</PRE>

    For example, you can use the following values in **Add or edit OMA-URI Setting**:
    
    **Setting Name**: Windows Analytics Commercial ID<BR>
    **Setting Description**: Configuring commercial id for Windows Analytics solutions<BR>
    **Data Type**: String<BR>
    **OMA-URI (case sensitive)**: ./Vendor/MSFT/DMClient/Provider/ProviderID/CommercialID<BR>
    **Value**: \<Use the GUID shown on the Windows Telemetry tab in your OMS workspace\><BR>



## Related topics

[Use Update Compliance to monitor Windows Updates](update-compliance-using.md)