+ 
+
+
+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.
+
+
+ 
+
+
+3. Create a new OMS workspace.
+
+
+ 
+
+
+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**.
+
+
+ 
+
+
+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.
+
+
+ 
+
+
+6. To add the Update Compliance solution to your workspace, go to the Solutions Gallery.
+
+
+ 
+
+
+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.
+
+
+ 
+
+
+8. Click the **Update Compliance** tile to configure the solution. The **Settings Dashboard** opens.
+
+
+ 
+
+
+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.
+
+
+ 
+
+
+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
+ 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**.
+
+- Using Microsoft Mobile Device Management (MDM)
+ 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).
+
+
diff --git a/windows/manage/update-compliance-monitor.md b/windows/manage/update-compliance-monitor.md
new file mode 100644
index 0000000000..cea946a497
--- /dev/null
+++ b/windows/manage/update-compliance-monitor.md
@@ -0,0 +1,53 @@
+---
+title: Monitor Windows Updates with Update Compliance (Windows 10)
+description: Introduction to Update Compliance.
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.pagetype: deploy
+author: greg-lindsay
+---
+
+# Monitor Windows Updates with Update Compliance
+
+## Introduction
+
+With Windows 10, organizations need to change the way they approach monitoring and deploying updates. Update Compliance is a powerful set of tools that enable organizations to monitor and track all important aspects of Microsoft’s new servicing strategy: [Windows as a Service](waas-overview.md).
+
+Update Compliance is a solution built within Operations Management Suite (OMS), a cloud-based monitoring and automation service which has a flexible servicing subscription based off data usage/retention. For more information about OMS, see [Operations Management Suite overview](http://azure.microsoft.com/en-us/documentation/articles/operations-management-suite-overview/).
+
+Update Compliance uses the Windows telemetry that is part of all Windows 10 devices. It collects system data including update installation progress, Windows Update for Business (WUfB) configuration data, and other update-specific information, and then sends this data privately to a secure cloud to be stored for analysis and usage within the solution.
+
+Update Compliance provides the following:
+
+- An overview of your organization’s devices that just works.
+- Dedicated drill-downs for devices that might need attention.
+- An inventory of devices, including the version of Windows they are running and their update status.
+- An overview of WUfB deferral configurations (Windows 10 Anniversary Update [1607] and later).
+- Powerful built-in [log analytics](https://www.microsoft.com/en-us/cloud-platform/insight-and-analytics?WT.srch=1&WT.mc_id=AID529558_SEM_%5B_uniqid%5D&utm_source=Bing&utm_medium=CPC&utm_term=log%20analytics&utm_campaign=Hybrid_Cloud_Management) to create useful custom queries.
+- Cloud-connected access utilizing Windows 10 telemetry means no need for new complex, customized infrastructure.
+
+See the following topics in this guide for detailed information about configuring and use the Update Compliance solution:
+
+- [Get started with Update Compliance](update-compliance-get-started.md): How to add Update Compliance to your environment.
+- [Using Update Compliance](update-compliance-using.md): How to begin using Update Compliance.
+
+An overview of the processes used by the Update Compliance solution is provided below.
+
+## Update Compliance architecture
+
+The Update Compliance architecture and data flow is summarized by the following five step process:
+
+**(1)** User computers send telemetry data to a secure Microsoft data center using the Microsoft Data Management Service.
+**(2)** Telemetry data is analyzed by the Update Compliance Data Service.
+**(3)** Telemetry data is pushed from the Update Compliance Data Service to your OMS workspace.
+**(4)** Telemetry data is available in the Update Compliance solution.
+**(5)** You are able to monitor and troubleshoot Windows updates on your network.
+
+These steps are illustrated in following diagram:
+
+
+
+>This process assumes that Windows telemetry is enabled and devices are assigned your Commercial ID.
+
+
diff --git a/windows/manage/update-compliance-using.md b/windows/manage/update-compliance-using.md
new file mode 100644
index 0000000000..90c8c40942
--- /dev/null
+++ b/windows/manage/update-compliance-using.md
@@ -0,0 +1,350 @@
+---
+title: Using Update Compliance (Windows 10)
+description: Explains how to begin usihg Update Compliance.
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.pagetype: deploy
+author: greg-lindsay
+---
+
+# Use Update Compliance to monitor Windows Updates
+
+This section describes how to use Update Compliance to monitor Windows Updates and troubleshoot update failures on your network.
+
+
+Update Compliance:
+- Uses telemetry gathered from user devices to form an all-up view of Windows 10 devices in your organization.
+- Enables you to maintain a high-level perspective on the progress and status of updates across all devices.
+- Provides a workflow that can be used to quickly identify which devices require attention.
+- Enables you to track deployment compliance targets for updates.
+
+>Information is refreshed daily so that update progress can be monitored. Changes will be displayed about 24 hours after their occurrence, so you always have a recent snapshot of your devices.
+
+In OMS, the aspects of a solution's dashboard are usually divided into blades. Blades are a slice of information, typically with a summarization tile and an enumeration of the items that makes up that data. All data is presented through queries. Perspectives are also possible, wherein a given query has a unique view designed to display custom data. The terminology of blades, tiles, and perspectives will be used in the sections that follow.
+
+Update Compliance has the following primary blades:
+
+
+1. [OS Update Overview](#os-update-overview)
+2. [Overall Quality Update Status](#overall-quality-update-status)
+3. [Latest and Previous Security Update Status](#latest-and-previous-security-update-status)
+4. [Overall Feature Update Status](#overall-feature-update-status)
+5. [CB, CBB, LTSB Deployment Status](#cb-cbb-ltsb-deployment-status)
+6. [List of Queries](#list-of-queries)
+
+
+## OS Update Overview
+
+The first blade of OMS Update Compliance is the General **OS Update Overview** blade:
+
+
+
+
+This blade is divided into three sections:
+- Device Summary:
+- Needs Attention Summary
+- Update Status Summary
+
+The **Device Summary** displays the total number of devices in your organization. These devices have the commercial ID configured, telemetry enabled, and have sent telemetry to Microsoft within the last 28 days. The tile also shows the devices that Need Attention.
+
+
+The **Needs Attention Summary** summarizes devices that require action on your part. There are multiple reasons why a device might need attention, and these reasons are categorized and summarized in the tile. You can view details about devices that are categorized as Needs Attention using a table view. The following **Needs Attention** states are defined:
+
+
+
+| Needs Attention | Definition
+ | | Out of Support | Total number of devices that are no longer receiving servicing updates
+ | | Update failed | When a device has reported a failure at some stage in its update deployment process, it will report that the Update Failed. You can click on this to see the full set of devices with more details about the stage at which a failure was reported, when the device reported a failure, and other data.
+ | | Missing 2+ Security Updates | Total number of devices that are missing two or more security updates
+ | | Update Progress Stalled | Total number of devices where an update installation has been “in progress” for more than 7 days
+ |
+
+
+The **Update Status Summary** summarizes your organization's devices per the Windows 10 "Windows as a Service" (WaaS) model. For more information about WaaS, see [Overview of Windows as a service](waas-overview.md). Devices are categorized as: **Current**, **Up-to-date**, and **Not up-to-date**. See the following graphical representation of this model:
+
+
+
+
+
+Update Status Summary definitions:
+
+
+
+| Update Status | Definition
+ | | Current and Up-to-date | A device that is current is on the latest and greatest Microsoft offers. It is on the very newest feature update (ex. The Windows Anniversary Update, RS1), on the very latest quality update for its servicing branch.
+ | | Up-to-date | A device that is up-to-date is on the latest quality update for its servicing option (CB, CBB, LTSB), and the device is running an OS that is supported by Microsoft.
+ | | Not up-to-date | A device does not have the latest quality update for its servicing option.
+ |
+
+
+## Overall Quality Update Status
+
+**Overall Quality Update Status** is the second blade in Update Compliance. It has a donut data tile and lists the breakdown of the Up-to-date status of devices pivoted on OS version. See the following example:
+
+
+
+
+
+The donut tile offers a summary of all devices in your organization, divided into **Up-to-date** and **Not up-to-date**. Recall that devices that are current are also up-to-date.
+
+
+The list view contains the breakdown of Up-to-date, Not up-to-date, and Update failed, all pivoted on OS version (e.g., 1507, 1511, 1607). Clicking on any of the rows of this list view will display the **OS Quality Update Summary Perspective** for that OS version.
+
+
+## Latest and Previous Security Update Status
+
+Security updates are extremely important to your organization, so in addition to an overall view of Quality Updates, the deployment status for the latest two security updates are displayed for each supported OS build offered by Microsoft.
+
+
+
+
+
+For the latest security update, a doughnut chart is displayed across all OS builds with a count of installed, in progress/deferred, update failed, and unknown status relative to that update. Two table views are provided below the doughnut displaying the same breakdown for each OS build supported by Microsoft.
+
+See the following definitions:
+
+
+
+| Term | Definition
+ | | OS Build | The OS build + Revision for the OS Version. The build + revision is a one-to-one mapping of the given security update in this context.
+ | | Version | The OS Version corresponding to the OS build.
+ | | Installed | The count of devices that have the given security update installed. In the case that the latest security update is not latest quality update (that is, an update has since been released but it did not contain any security fixes), then devices that are on a newer update will also be counted.
+
For the previous security update, a device will display as **Installed** until it has at least installed the latest security update.
+ | | In Progress or Deferred | The count of devices that are either currently in the process of installing the given security update, or are deferring the install as per their WUFB policy.
+
All devices in this category for Previous Security Update Status are missing 2 or more security updates, and therefore qualify as needing attention.
+ | | Update Failed | The count of devices that were **In Progress** for the given security update, but failed at some point in the process. They will no longer be shown as **In Progress or deferred** in this case, and only be counted as **Update failed**.
+ | | Status Unknown | If a device should be, in some way, progressing toward this security update, but it’s status cannot be inferred, it will count as **Status Unknown**. Devices that are not using Windows Update are the most likely devices to fall into this category.
+ |
+
+
+## Overall Feature Update Status
+
+Windows 10 has two main update types: Quality and Feature updates. The third blade in Update Compliance provides the most essential data about your organization’s devices for feature updates.
+
+Microsoft has developed terms to help specify the state of a given device for how it fits into the Windows as a Service (WaaS) model. There are three update states for a device:
+- Current
+- Up-to-date
+- Not up-to-date
+
+
+See the **Update Status Summary** description under [OS Update Overview](#os-update-overview) in this guide for definitions of these terms.
+
+
+The Overall Feature Update Status blade focuses around whether or not your devices are considered Current. See the following example:
+
+
+
+
+
+Devices are evaluated by OS Version (e.g., 1607) and the count of how many are Current, Not Current, and have Update Failures is displayed. Clicking on any of these counts will allow you to view all those devices, as well as select the **Update Deployment Status** perspective, described below.
+
+
+## CB, CBB, LTSB Deployment Status
+
+Following the overview with respect to how current your organization’s devices are, there are three tables that show feature update deployment for all devices. The devices are split up by which branch they are on, as this directly impacts whether they are supported (for example, 1607 may be supported under CBB, but not under CB). This allows you a quick glance at how deployment is progressing across your organization with respect to feature updates.
+
+See the following example:
+
+
+
+
+
+The three tables break down devices by feature update. For each OS version, the following columns provide counts of the possible device states:
+
+
+
+| Deployment Status | Description
+ | | Feature Update | A concatenation of servicing branch (CB, CBB, LTSB) and OS Version (e.g., 1607)
+ | | Installed | The number of devices that have reported to be on the given servicing train and feature update.
+ | | In progress | The number of devices that have reported to be at some stage in the installation process for the given feature update.
+
Example: Device X running CB 1507 could be installing CB 1607. In this example, X would count as both **Installed** for **CB 1507** and **In Progress** for **CB 1607**.
+ | | Scheduled next 7 days | The total number of devices that are set to have a deferral period expire within 7 days, and after that deferral period expires are targeted to install the given update.
+
Example: Device Y running CB 1507 could be scheduled to install CB 1607 in 5 days. In this example, X would count as both **Installed** for **CB 1507** and **Scheduled next 7 days** for **CB 1607**
+ | | Update Failed | The total number of devices that were **In progress** with the installation for the given feature update, but encountered a failure.
+
Example: Device X running CB 1507 could be installing CB 1607. X then encounters an error during installation. In this example, X would count as both **Installed** for **CB 1507** and **Update failed** for **CB 1607**, but not as **In progress** for **CB 1607**.
+ | | Status Unknown | For devices not using Windows Update to get updates, some information on deployment progress cannot be known. It is possible to know the current installed Feature Update for a device, but not which devices are **In Progress**, **Scheduled next 7 days**, or devices with **Update Failed**.
+
Devices that Update Compliance knows belongs to your organization, but it does not know update failures or installation progress, will be counted here.
+ |
+
+
+## Quality Update Perspective
+
+The Quality Update Deployment Status perspective is a breakdown of the most essential data the user should know about the status of their devices with respect to being Up-to-date. The perspective shows a summary of the organization’s devices for one specific OS version, or build.
+
+### Quality Update Build Summary
+
+The build summary blade attempts to summarize the most important data points to the user for the given build. It is divided into two sections. The first section is a summary of devices for that build – the total number of devices, and the amount that need attention. Each row within the table below is a breakdown of why each device requires attention. The rows can be interacted with to be taken to a larger table view that shows detailed information about all the devices that meet the given criteria. See the following example:
+
+
+
+
+
+### Quality Update Deferral Configurations
+
+The next blade is the Deferral configuration blade, which shows the WUFB Deferral configurations for all devices that are using WUFB and are reporting to Update Compliance. If no information can be gathered from a device or it is not configured to use WUFB, it will show up as **Not configured (-1)**. See the following example:
+
+
+
+
+
+### Quality Update Deployment Status
+
+Under the three top-level blades is the deployment status for the newest quality update for the given build. It provides information on the revision number as well as how many days it has been since that revision has been released. See the following example:
+
+
+
+
+
+See the following table for a description of last reported states for devices deploying that quality update.
+
+
+
+| Deployment State | Description
+ | | Update Completed | When a device has finished the update process and is on the given update, it will display here as **Update completed**.
+ | | In Progress | Devices that are “in progress” installing an update will fall within this category. This category is detailed in the following blade: **Detailed Deployment Status**.
+ | | Deferred | If a device’s WUfB deferral policy dictates that it is not set to receive this update, the device will show as Update deferred.
+ | | Cancelled | A device will report that the update has been cancelled if the user, at some point, cancelled the update on the device.
+ | | Blocked | Devices that are blocked are prevented from proceeding further with the given update. This could be because another update is paused, or some other task on the device must be performed before the update process can proceed.
+ |
+
+
+
+
+### Quality Update Detailed Deployment Status
+
+This blade provides more detail on the deployment process for the update in the Deployment Status blade. This blade is more of a deployment funnel for devices, enabling you to see at a more granular level how devices are progressing along in their deployment. See the following example:
+
+
+
+
+
+>Devices that are not managed using Windows Update (Windows Update for Business or otherwise) will not have detailed deployment information.
+
+
+The following table provides a list of the detailed deployment states a device can report:
+
+
+
+| Detailed Deployment State | Description
+ | | Update deferred | The WUfB policy of the device dictates the update is deferred.
+ | | Pre-Download Tasks Passed | The device has finished all tasks necessary prior to downloading the update.
+ | | Download Started | The update has begun downloading on the device.
+ | | Download Succeeded | The device has successfully downloaded the update.
+ | | Pre-Install Tasks Passed | The device has downloaded the update successfully, and successfully passed all checks prior to beginning installation of the update.
+ | | Install Started | The device has begun installing the update.
+ | | Reboot Required | The device has finished installing the update, and a reboot is required before the update can be completed.
+ | | Reboot Pending | The device is pending a scheduled reboot before the update can be completed.
+ | | Reboot Initiated | The device has reported to have initiated the reboot process for completing the update.
+ | | Update completed | The device has completed installing, rebooting, and applying the update.
+ |
+
+
+## Feature Update Perspective
+
+
+Like Quality Updates, the Feature Update Deployment Status perspective is a breakdown of information most essential to an administrator. This information is viewed by clicking on a given build on the Feature Update Status blade and then navigating to the **Update Deployment Status** pane as displayed previously. In Update Compliance, a perspective is assigned to a query; the query used to generate the perspective can be altered to show other information, if desired.
+
+Every piece of data shown in this view can be clicked; when clicked, it will alter the query to focus only on the data you need. If the perspective is not meaningful after the query is altered, you can use the other data views like the List and Table.
+
+>After clicking on an OS version from the Feature Update Status blade, the query must fully load the results before you can select the Update Deployment Status perspective.
+
+### Feature Update Build Summary
+
+
+The Build Summary blade provides a summary for all devices on the given build. It gives a count of all devices, as well as a count of all devices that need attention. Below the counts, you can see why the devices need attention, with a count of devices that fall into each category. See the following example:
+
+
+
+### Feature Update Deferral Configuration
+
+
+This blade shows all deferral configurations for the devices on the given build. See the following example:
+
+
+
+
+
+Deferral configurations are WUfB-specific, and are shown as days. Some useful information regarding how deferral configurations are shown:
+- The devices are grouped based off what their deferral policy is set at. For feature updates, this can be up to 120 days.
+- A deferral of zero days means the device has WUfB configured, but is set to not defer the update. These devices will be under “0” for the Update Deferred field.
+- Devices that are not configured to use WUfB deferral policies have a “-1” for their deferral days. In this table, the devices will show up as “Not Configured (-1)”.
+
+### Feature Update Deployment Status
+
+As stated earlier in this section, the Feature Updates blade focuses on how Current your devices are. A device is only Current when it is on the latest feature update and quality update Microsoft offers. Thus, the Deployment Status blade displays the deployment status for devices regarding their deployment to the latest feature update. See the following example:
+
+
+
+
+
+This blade breaks down the main states a device can be in through the deployment of a feature update. The possible states are as follows:
+
+
+
+| Deployment State | Description
+ | | Update completed | When a device has completely finished the update process and is on the given update, it will show up here as **Update completed**.
+ | | Inprogress | Devices “in progress” of installing the given update will fall within this category. This category is iterated on with further granularity in the proceeding blade, “Detailed Deployment Status”.
+ | | Update deferred | If a device’s WUfB deferral policy dictates that it is not set to receive this update yet, the device will show as Update deferred.
+ | | Cancelled | A device will report that the update has been cancelled if the user, at some point, cancelled the update on the device.
+ | | Blocked | Devices that are blocked are prevented from proceeding further with the given update. This could be because another update is paused, or some other task on the device must be performed before the update process can proceed.
+ |
+
+
+
+
+
+
+
+
+### Feature Update Detailed Deployment Status
+
+This blade provides more detail on the deployment process for the update in the Deployment Status blade. This blade is more of a deployment funnel for devices, enabling you to see at a more granular level how devices are progressing along in their deployment. See the following example:
+
+
+
+
+
+The following table displays all states a device can report:
+
+
+
+| Detailed Deployment State | Description
+ | | Update deferred | The WUfB policy of the device dictates the update is deferred.
+ | | Pre-Download Tasks Passed | The device has finished all tasks necessary prior to downloading the update.
+ | | Download Started | The update has begun downloading on the device.
+ | | Download Succeeded | The device has successfully downloaded the update.
+ | | Pre-Install Tasks Passed | The device has downloaded the update successfully, and successfully passed all checks prior to beginning installation of the update.
+ | | Install Started | The device has begun installing the update.
+ | | Reboot Required | The device has finished installing the update, and a reboot is required before the update can be completed.
+ | | Reboot Pending | The device is pending a scheduled reboot before the update can be completed.
+ | | Reboot Initiated | The device has reported to have initiated the reboot process for completing the update.
+ | | Update completed | The device has completed installing, rebooting, and applying the update.
+ |
+
+
+
+## List of Queries
+
+Operations Management Suite leverages its powerful Log Analytics querying to perform all data calculations. For this blade, we provide examples of queries that show useful data to the user about their organization’s devices. See the following example:
+
+
+
+
+
+The following **Common queries** are available:
+
+
+
+| Query Title | Description
+ | | OS Security Update Status | This query provides an all-up view with respect to how many devices are on the latest security update for their OS version. The table will detail an aggregated count of the number of devices, out of the total (so count, or percent) are on the latest security update for their OS build.
+ | | Update Deployment Failures | This query provides a chart view, displaying an aggregation of all devices that have reported a deployment failure for either feature or quality updates. The aggregation of the data is on the given update for which a given device has reported a deployment failure.
+ | | Devices pending reboot to complete update | This query will provide a table showing all devices that are at the stage of "Reboot Pending" In the update deployment process.
This query will show devices which are in this state for both feature and quality updates; the data will be organized on precisely which update the given device(s) are pending a reboot to install.
+ | | Servicing Option Distribution for the devices | This query provides a chart view that aggregates all devices seen by the solution on for each servicing option available for Windows 10 devices (CB, CBB, LTSB)
+OS Distribution for the devices This query provides a chart view displaying the distribution of the different editions of Windows 10 that devices seen by the solution are running (e.g., Enterprise, Professional, Education, etc.)
+ | | Deferral configurations for Feature Update | This query provides a chart view which displays a breakdown of the different Feature Update deferral configurations through WUfB that the devices seen by the solution are using.
The configuration is in days. 0 days means the device has WUfB deferrals configured, but is not set to defer feature updates. -1 means the device has no feature update deferral policies configured.
+ | | Pause configurations for Feature Update | The WUfB policy
+ | | Update deferred | This query provides a chart view displaying the breakdown of devices that are either paused, or not paused for feature updates.
“Not configured” means the device is not paused. “Paused” means it is currently paused.
+ | | Deferral configurations for Quality Update | This query provides a chart view which displays a breakdown of the different Quality Update deferral configurations through WUfB that the devices seen by the solution are using.
The configuration is in days. 0 days means the device has WUfB deferrals configured, but is not set to defer quality updates. -1 means the device has no quality update deferral policies configured.
+ | | Pause configurations for Quality Update | This query provides to a chart view displaying the breakdown of devices that are either paused, or not paused for quality updates.
**Not configured** means the device is not paused. **Paused** means it is currently paused.
+ |
\ No newline at end of file
diff --git a/windows/manage/waas-overview.md b/windows/manage/waas-overview.md
index fca1c64ad5..d597a74145 100644
--- a/windows/manage/waas-overview.md
+++ b/windows/manage/waas-overview.md
@@ -127,7 +127,9 @@ For many IT pros, gaining visibility into feature updates early—before they’
Microsoft recommends that all organizations have at least a few PCs enrolled in the Windows Insider Program and provide feedback on any issues they encounter. For information about how to sign up for the Windows Insider Program and enroll test devices, go to [https://insider.windows.com](https://insider.windows.com).
>[!NOTE]
->The Windows Insider Program isn’t intended to replace CB deployments in an organization. Rather, it provides IT pros and other interested parties with prerelease Windows builds that they can test and ultimately provide feedback on to Microsoft.
+>Microsoft recommends that all organizations have at least a few PCs enrolled in the Windows Insider Program, to include the Windows Insider Program in their deployment plans and to provide feedback on any issues they encounter to Microsoft via our Feedback Hub app.
+>
+>The Windows Insider Program isn’t intended to replace CB deployments in an organization. Rather, it provides IT pros and other interested parties with pre-release Windows builds that they can test and ultimately provide feedback on to Microsoft.
diff --git a/windows/manage/waas-servicing-branches-windows-10-updates.md b/windows/manage/waas-servicing-branches-windows-10-updates.md
index 7e62bcbf3a..322b7c07b2 100644
--- a/windows/manage/waas-servicing-branches-windows-10-updates.md
+++ b/windows/manage/waas-servicing-branches-windows-10-updates.md
@@ -90,10 +90,17 @@ Enrolling devices in the Windows Insider Program is simple and requires only a M
6. Click **Confirm**, and then select a time to restart the computer.
-7. After you restart the device, go to **Start** > **Settings** > **Update & security** > **Windows Insider Program** to select your Insider level. The device receives the most recent Windows Insider build for the Insider level you select. The options for Insider level are:
- - **Release Preview**: Insiders on this level receive builds of Windows just before Microsoft releases them for CB. Although these builds aren’t final, they are the most complete and stable builds available to Windows Insider Program participants. This level provides the best testing platform for organizations that conduct early application compatibility testing on Windows Insider PCs.
- - **Slow**: The Slow Windows Insider level is for users who enjoy seeing new builds of Windows with minimal risk to their devices but still want to provide feedback to Microsoft about their experience with the new build.
- - **Fast**: This level is best for Insiders who would like to be the first to experience new builds of Windows, participate in identifying and reporting issues to Microsoft, and provide suggestions on new functionality.
+## Install your first preview build from the Windows Insider Program
+
+After enrolling your devices, you are ready to install your first preview build. To do so, go to **Start** > **Settings** > **Update & security** > **Windows Insider Program** to select your Insider level. The device receives the most recent Windows Insider build for the Insider level you select.
+
+The options for Insider level are:
+- **Release Preview**: Insiders on this level receive builds of Windows just before Microsoft releases them for CB. Although these builds aren’t final, they are the most complete and stable builds available to Windows Insider Program participants. This level provides the best testing platform for organizations that conduct early application compatibility testing on Windows Insider PCs.
+- **Slow**: The Slow Windows Insider level is for users who enjoy seeing new builds of Windows with minimal risk to their devices but still want to provide feedback to Microsoft about their experience with the new build.
+- **Fast**: This level is best for Insiders who would like to be the first to experience new builds of Windows, participate in identifying and reporting issues to Microsoft, and provide suggestions on new functionality.
+
+>[!NOTE]
+>Once your machine is updated to Windows 10 and you select your desired flight ring, the process known as "Compatibility check" will need to run in the background. There is no manual way to force this process to run. This process allows for the discovery of your OS type (32-bit, 64-bit), build edition (Home, Pro, Enterprise), country and language settings, and other required information. Once this process is complete, your machine will be auto-targeted for the next available flight for your selected ring. For the first build on any given machine, this may take up to 24 hours to complete.
## Block access to Windows Insider Program
diff --git a/windows/manage/waas-update-windows-10.md b/windows/manage/waas-update-windows-10.md
index f257330910..353a7bf43d 100644
--- a/windows/manage/waas-update-windows-10.md
+++ b/windows/manage/waas-update-windows-10.md
@@ -34,6 +34,7 @@ Windows as a service provides a new way to think about building, deploying, and
| [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md) | Explains the decisions you need to make in your servicing strategy. |
| [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) | Explains how to make use of servicing branches and update deferrals to manage Windows 10 updates. |
| [Assign devices to servicing branches for Windows 10 updates](waas-servicing-branches-windows-10-updates.md) | Explains how to assign devices to Current Branch (CB) or Current Branch for Business (CBB) for feature and quality updates, and how to enroll devices in Windows Insider. |
+| [Monitor Windows Updates with Update Compliance](update-compliance-monitor.md) | Explains how to use Windows Analytics: Update Compliance to monitor and manage Windows Updates on devices in your organization. |
| [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) | Explains the benefits of using Delivery Optimization or BranchCache for update distribution. |
| [Manage updates for Windows 10 Mobile Enterprise and Windows 10 IoT Mobile](waas-mobile-updates.md) | Explains updates for Windows 10 Mobile Enterprise and Windows 10 IoT Mobile. |
| [Manage updates using Windows Update for Business](waas-manage-updates-wufb.md) | Explains how to use Windows Update for Business to manage when devices receive updates directly from Windows Update. Includes walkthroughs for configuring Windows Update for Business using Group Policy and Microsoft Intune. |
|
|
|
|
|
|
|
|
|
+ 
+ 
