Merged PR 3759: rs3 push for WUFB\WIP for Biz\Update Compliance

windows/deployment/update/update-compliance-feature-update-status.md

@@ -0,0 +1,28 @@
+---
+title: Update Compliance - Feature Update Status report
+description: an overview of the Feature Update Status report
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.pagetype: deploy
+author: DaniHalfin
+ms.author: daniha
+ms.date: 10/17/2017
+---
+
+# Feature Update Status
+
+![The Feature Update Status report](images/uc-featureupdatestatus.png)
+
+The Feature Update Status section provides information about the status of [feature updates](waas-quick-start.md#definitions) across all devices. This section tile in the [Overview Blade](update-compliance-using.md#overview-blade) gives a percentage of devices that are on the latest applicable feature update; [Servicing Channel](waas-overview.md#servicing-channels) is considered in determining applicability. Within this section three **Deployment Status** tiles make up a blade, each charged with tracking the deployment for a different Servicing Channel. 
+
+To effectively track deployment, **Deployment Status Blades** are divided into each Servicing Channel chosen for the device. This is because Deployment for each channel will happen at different periods in time and feature updates are targeted separately for each channel. Within each Deployment Status tile, devices are aggregated on their feature update distribution, and the columns list the states each device is in.
+
+Refer to the following list for what each state means:
+* **Installed** devices are devices that have completed installation for the given update.
+* When a device is counted as **In Progress**, it has begun the feature update installation. 
+* Devices that are **scheduled next 7 days** are all devices that were deferred from installing the Feature update using [Windows Update for Business Settings](waas-manage-updates-wufb.md) and are set to begin installation in the next 7 days.
+* Devices that have failed the given feature update installation are counted as **Update failed**.
+* If a device should be, in some way, progressing toward this security update, but its status cannot be inferred, it will count as **Status Unknown**. Devices not using Windows Update are the most likely devices to fall into this category.
+
+Clicking on any row will navigate to the query relevant to that feature update. These queries are attached to [Perspectives](update-compliance-perspectives.md) that contain detailed deployment data for that update. 

windows/deployment/update/update-compliance-get-started.md

@@ -6,7 +6,9 @@ ms.prod: w10
 ms.mktglfcycl: deploy
 ms.sitesec: library
 ms.pagetype: deploy
-author: jaimeo
+author: DaniHalfin
+ms.author: daniha
+ms.date: 10/17/2017
 ---
 
 # Get started with Update Compliance
@@ -14,9 +16,9 @@ author: jaimeo
 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.
+1. Ensure that [prerequisites](#update-compliance-prerequisites) are met.
-2.	[Add Update Compliance](#add-update-compliance-to-microsoft-operations-management-suite) to Microsoft Operations Management Suite.
+2. [Add Update Compliance](#add-update-compliance-to-microsoft-operations-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.
+3. [Deploy your Commercial ID](#deploy-your-commercial-id-to-your-windows-10-devices) to your organization’s devices.
 
 ## Update Compliance prerequisites
 
@@ -34,7 +36,7 @@ Update Compliance has the following requirements:
 
  4. To use Windows Defender Antivirus Assessment, devices must be protected by Windows Defender AV (and not a 3rd party AV program), and must have enabled [cloud-delivered protection](/windows/threat-protection/windows-defender-antivirus/utilize-microsoft-cloud-protection-windows-defender-antivirus). See the [Troublehsoot Windows Defender Antivirus reporting](/windows/threat-protection/windows-defender-antivirus/troubleshoot-reporting.md) topic for help on ensuring the configuration is correct.
  
-     For endpoints running Windows 10, version 1607 or earlier, [Windows telemetry must also be set to **Enhanced**](https://docs.microsoft.com/en-us/windows/configuration/configure-windows-telemetry-in-your-organization#enhanced-level). 
+     For endpoints running Windows 10, version 1607 or earlier, [Windows telemetry must also be set to **Enhanced**](https://docs.microsoft.com/en-us/windows/configuration/configure-windows-telemetry-in-your-organization#enhanced-level), to be compatible with Windows Defender Antivirus. 
     
     See the [Windows Defender Antivirus in Windows 10](/windows/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10) content library for more information on enabling, configuring, and validating Windows Defender AV.
 
@@ -43,62 +45,36 @@ Update Compliance has the following requirements:
 
 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-premise 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. While you're in the Solutions Gallery, you should consider installing the [Upgrade Readiness](../upgrade/use-upgrade-readiness-to-manage-windows-upgrades.md)  and [Device Health](device-health-monitor.md) solutions as well, if you haven't already.
+If you are already using OMS, skip to step **6** to add Update Compliance to 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](https://www.microsoft.com/en-us/cloud-platform/operations-management-suite) on Microsoft.com and click **Sign in**.   
-
+  ![Operations Management Suite bar with sign-in button](images/uc-02a.png)  
-
-   [![Operations Management Suite bar with sign-in button](images/uc-02a.png)](images/uc-02.png)
-
   
 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.   
-
+  ![OMS Sign-in dialog box for account name and password](images/uc-03a.png)  
-
-   [![OMS Sign-in dialog box for account name and password](images/uc-03a.png)](images/uc-03.png)
-
   
 3.	Create a new OMS workspace.   
-
+  ![OMS dialog with buttons to create a new OMS workspace or cancel](images/uc-04a.png)  
-
-   [![OMS dialog with buttons to create a new OMS workspace or cancel](images/uc-04a.png)](images/uc-04.png)
    
 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**.   
-
+  ![OMS Create New Workspace dialog](images/uc-05a.png)](images/uc-05.png)
-
-   [![OMS Create New Workspace dialog](images/uc-05a.png)](images/uc-05.png)
-
   
 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.  
-
+  ![OMS dialog to link existing Azure subscription or create a new one](images/uc-06a.png)  
-
-   [![OMS dialog to link existing Azure subscription or create a new one](images/uc-06a.png)](images/uc-06.png)
-
   
 6.	To add the Update Compliance solution to your workspace, go to the Solutions Gallery.  While you have this dialog open, you should also consider adding the [Upgrade Readiness](../upgrade/use-upgrade-readiness-to-manage-windows-upgrades.md) and [Device Health](device-health-monitor.md) solutions as well, if you haven't already. To do so, just select the check boxes for those solutions.   
-
+  ![OMS workspace with Solutions Gallery tile highlighted](images/uc-07a.png)   
-
-   [![OMS workspace with Solutions Gallery tile highlighted](images/uc-07a.png)](images/uc-07.png)
-
   
 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 in your workspace.   
-
+  ![Workspace showing Solutions Gallery](images/uc-08a.png)  
- 
-   [![Workspace showing Solutions Gallery](images/uc-08a.png)](images/uc-08.png)
-
   
 8.	Click the **Update Compliance** tile to configure the solution. The **Settings Dashboard** opens.   
-
+  ![OMS workspace with new Update Compliance tile on the right side highlighted](images/uc-09a.png)  
-
-   [![OMS workspace with new Update Compliance tile on the right side highlighted](images/uc-09a.png)](images/uc-09.png)
-
   
 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.   
-
+  ![Series of blades showing Connected Sources, Windows Telemetry, and Upgrade Analytics solution with Subscribe button](images/uc-10a.png)  
-
-   [![Series of blades showing Connected Sources, Windows Telemetry, and Upgrade Analytics solution with Subscribe button](images/uc-10a.png)](images/uc-10.png)
-
   
 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.
 

windows/deployment/update/update-compliance-monitor.md

@@ -6,7 +6,9 @@ ms.prod: w10
 ms.mktglfcycl: deploy
 ms.sitesec: library
 ms.pagetype: deploy
-author: greg-lindsay
+author: DaniHalfin
+ms.author: daniha
+ms.date: 10/17/2017
 ---
 
 # Monitor Windows Updates and Windows Defender Antivirus with Update Compliance
@@ -15,7 +17,7 @@ author: greg-lindsay
 
 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 the new servicing strategy from Microsoft: [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 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/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, Windows Defender Antivirus 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. 
 
@@ -52,7 +54,7 @@ These steps are illustrated in following diagram:
 ![Update Compliance architecture](images/uc-01-wdav.png)
 
 >[!NOTE]
->This process assumes that Windows telemetry is enabled and you [have assigned your Commercial ID to devices](update-compliance-get-started#deploy-your-commercial-id-to-your-windows-10-devices.
+>This process assumes that Windows telemetry is enabled and you [have assigned your Commercial ID to devices](update-compliance-get-started.md#deploy-your-commercial-id-to-your-windows-10-devices).
 
 
 

windows/deployment/update/update-compliance-need-attention.md

@@ -0,0 +1,38 @@
+---
+title: Update Compliance - Need Attention! report
+description: an overview of the Update Compliance Need Attention! report
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.pagetype: deploy
+author: DaniHalfin
+ms.author: daniha
+ms.date: 10/17/2017
+---
+
+# Need Attention!
+
+![Need Attention! report](images/uc-needattentionoverview.png)
+
+The “Need Attention!” section provides a breakdown of all device issues detected by Update Compliance. The summary tile for this section counts the number of devices that have issues, while the blades within break down the issues encountered. Finally, a [list of queries](#list-of-queries) blade is shown within this section that contains queries that provide values but do not fit within any other main section. 
+
+>[!NOTE]
+>The summary tile counts the number of devices that have issues, while the blades within the section break down the issues encountered. A single device can have more than one issue, so these numbers may not add up.
+
+The different issues are broken down by Device Issues and Update Issues, which are iterated below:
+
+## Device Issues
+
+* **Missing multiple security updates:** This issue occurs when a device is behind by two or more security updates. These devices may be more vulnerable and should be investigated and updated.
+* **Out of support OS Version:** This issue occurs when a device has fallen out of support due to the version of Windows 10 it is running. When a device has fallen out of support, it will no longer be serviced, and may be vulnerable. These devices should be updated to a supported version of Windows 10.
+
+## Update Issues
+
+* **Failed:** This issue occurs when an error halts the process of downloading and applying an update on a device. Some of these errors may be transient, but should be investigated further to be sure.
+* **Progress stalled:** This issue occurs when an update is in progress, but has not completed over a period of 10 days.
+
+Clicking on any of the issues will navigate you to the Log Search view with all devices that have the given issue.
+
+## List of Queries
+
+The List of Queries blade resides within the “Need Attention!” section of Update Compliance. This blade contains a list of queries with a description and a link to the query. These queries contain important meta-information that did not fit within any specific section or were listed to serve as a good starting point for modification into custom queries. 

windows/deployment/update/update-compliance-perspectives.md

@@ -0,0 +1,56 @@
+---
+title: Update Compliance - Perspectives
+description: an overview of Update Compliance Perspectives
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.pagetype: deploy
+author: DaniHalfin
+ms.author: daniha
+ms.date: 10/17/2017
+---
+
+# Perspectives
+
+![Perspectives data view](images/uc-perspectiveupdatedeploymentstatus.png)
+
+Perspectives are elaborations on specific queries hand-crafted by developers which data views that provide deeper insight into your data. Perspectives are loaded whenever clicking into more detailed views from both the Security Update Status section and Feature Update Status section of Update Compliance. 
+
+There is only one perspective framework; it is for **Update Deployment Status**. The same framework is utilized for both feature and quality updates. 
+
+The first blade is the **Build Summary** blade. This blade summarizes the most important aspects of the given build being queried, listing the total number of devices, the total number of update failures for the build, and a breakdown of the different errors encountered. 
+
+The second blade is the **Deferral Configurations** blade, breaking down Windows Update for Business deferral settings (if any). 
+
+The third blade is the **Deployment Status** blade. This defines how many days it has been since the queried version has been released, and breaks down the various states in the update funnel each device has reported to be in. The possible states are as follows:
+
+| State | Description |
+| --- | --- |
+| Update Completed | When a device has finished the update process and is on the queried update, it will display here as Update completed. |
+| In Progress |	Devices that report they are “In Progress” are one of the various stages of installing an update; these stages are reported in the Detailed Deployment Status blade. |
+| Deferred | When a device’s Windows Update for Business deferral policy dictates that the update is not yet applicable due to deferral, it will report as such in this blade. |
+| Progress stalled | Devices that report as “Progress stalled” have been stuck at “In progress” for more than 7 days. |
+| Cancelled | The update was cancelled. |
+| Blocked | There is a hard block on the update being completed. This could be that another update must be completed before this one, or some other task is blocking the installation of the update. |
+| Unknown | Devices that do not report detailed information on the status of their updates will report Unknown. This is most likely devices that do not use Windows Update for deployment. |
+| Update paused | These devices have Windows Update for Business pause enabled, preventing this update from being installed. |
+
+The final blade is the **Detailed Deployment Status** blade. This blade breaks down the detailed stage of deployment a device is in, beyond the generalized terms defined in Deployment Status. The following are the possible stages a device can report:
+
+| State | Description |
+| --- | --- |
+| Update deferred |	When a device’s Windows Update for Business policy dictates the update is deferred. |
+| Update paused | The device’s Windows Update for Business policy dictates the update is paused from being offered. |
+| Update offered | The device has been offered the update, but has not begun downloading it. |
+| Pre-Download tasks passed | The device has finished all necessary tasks prior to downloading the update. |
+| Download Started | The update has begun downloading on the device. |
+| Download Succeeded | The update has successfully completed downloading. |
+| Pre-Install Tasks Passed | Tasks that must be completed prior to installing the update have been completed. |
+| Install Started |	Installation of the update has begun. |
+| Reboot Required |	The device has finished installing the update, and a reboot is required before the update can be completed.
+| Reboot Pending | The device has a scheduled reboot to apply the update. |
+| Reboot Initiated | The scheduled reboot has been initiated. |
+| Update Completed/Commit |	The update has successfully installed. |
+
+>[!NOTE]
+>Interacting with any rows in the perspective view will automatically apply the given value to the query and execute it with the new parameter, narrowing the perspective to devices that satisfy that criteria. For example, clicking “Not configured (-1)” devices in Deferral Configurations will filter the query to only contain devices that do not have a deferral configuration. These filters can also be applied to queries via the filter sidebar.

windows/deployment/update/update-compliance-security-update-status.md

@@ -0,0 +1,32 @@
+---
+title: Update Compliance - Security Update Status report
+description: an overview of the Security Update Status report
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.pagetype: deploy
+author: DaniHalfin
+ms.author: daniha
+ms.date: 10/17/2017
+---
+
+# Security Update Status
+
+![The Security Update Status report](images/uc-securityupdatestatus.png)
+
+The Security Update Status section provides information about [quality updates](waas-quick-start.md#definitions) across all devices. The section tile within the O[verview Blade](update-compliance-using.md#overview-blade) lists the percentage of devices on the latest security update to provide the most essential data without needing to navigate into the section. However, within the section the Overall Quality Update Status blade also considers whether devices are up-to-date on non-security updates. 
+
+>[!NOTE]
+>It is possible for the percentage of devices on the latest security update to differ from devices that are up-to-date on all quality updates. This is because some devices may have non-security updates that are applicable to them. 
+
+The **Overall Quality Update Status** blade provides a visualization of devices that are and are not up-to-date on the latest quality updates (not just security updates). Below the visualization are all devices further broken down by OS Version and a count of how many are up-to-date and not up-to-date. Within the “Not up-to-date” column, the count of update failures is also given.
+ 
+The **Latest Security Update Status** and **Previous Security Update Status** tiles are stacked to form one blade. The **Latest Security Update Status** provides a visualization of the different deployment states devices are in regarding the latest update for each build (or version) of Windows 10, along with the revision of that update. The **Previous Security Update Status** blade provides the same information without the accompanying visualization. 
+
+What follows is a breakdown of the different deployment states reported by devices:
+* **Installed** devices are devices that have completed installation for the given update.
+* When a device is counted as **In Progress or Deferred**, it has either begun the installation process for the given update or has been intentionally deferred or paused using WU for Business Settings.
+* Devices that have **Update Failed**, failed updating at some point during the installation process of the given security update.
+* If a device should be, in some way, progressing toward this security update, but its status cannot be inferred, it will count as **Status Unknown**. Devices not using Windows Update are the most likely devices to fall into this category.
+
+The rows of each tile in this section are interactive; clicking on them will navigate you to the query that is representative of that row and section. These queries are also attached to [Perspectives](update-compliance-perspectives.md) with detailed deployment data for that update.

windows/deployment/update/update-compliance-using.md

@@ -5,12 +5,14 @@ ms.prod: w10
 ms.mktglfcycl: deploy
 ms.sitesec: library
 ms.pagetype: deploy
-author: greg-lindsay
+author: DaniHalfin
+ms.author: daniha
+ms.date: 10/17/2017
 ---
 
-# Use Update Compliance to monitor Windows Updates
+# Use Update Compliance
 
-This section describes how to use Update Compliance to monitor Windows Updates and troubleshoot update failures on your network.
+In this section you'll learn how to use Update Compliance to monitor your device's Windows updates and Windows Defender Antivirus status. To configure your environment for use with Update Compliance, refer to [Get started with Update Compliance](update-compliance-get-started.md).
 
 
 Update Compliance: 
@@ -18,470 +20,59 @@ Update Compliance:
 - 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.
+- Summarizes Windows Defender Antivirus status for devices that use it.
 
 >[!NOTE]
 >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 <I>blades</I>. 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 <I>queries</I>. <I>Perspectives</I> 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. 
+In Update Compliance, data is separated into vertically-sliced sections. Each section is referred to as a blade. Within a blade, there may or may not be multiple tiles, which serve to represent the data in different ways. Blades are summarized by their title in the upper-left corner above it. Every number displayed in OMS is the direct result of one or more queries. Clicking on data in blades will often navigate you to the query view, with the query used to produce that data. Some of these queries have perspectives attached to them; when a perspective is present, an additional tab will load in the query view. These additional tabs provide blades containing more information relevant to the results of the query.
 
-Update Compliance has the following primary blades: 
+## The Update Compliance Tile
 
+After Update Compliance has successfully been added from the solution gallery, you’ll see this tile:
+![Empty Update Compliance Tile](images/uc-emptyworkspacetile.png)
 
-1. [OS Update Overview](#os-update-overview)
+When the solution is added, data is not immediately available. Data will begin to be collected after data is sent up that is associated with the Commercial ID associated with the device. If you haven’t read about assigning your Commercial ID to your devices, refer to [this topic](update-compliance-get-started.md#deploy-your-commercial-id-to-your-windows-10-devices). After Microsoft has collected and processed any device data associated with your Commercial ID, the tile will be replaced with the following summary:
-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. [Windows Defender Antivirus Assessment](#wdav-assessment)
-7. [List of Queries](#list-of-queries)
 
+![Filled Update Compliance Tile](images/uc-filledworkspacetile.png)
 
-## OS Update Overview
+The summary details the total number of devices that Microsoft has received data from with your Commercial ID. It also provides the number of devices that need attention if any. Finally, it details the last point at which your Update Compliance workspace was updated. 
 
-The first blade of OMS Update Compliance is the General **OS Update Overview** blade: 
+## The Update Compliance Workspace
 
-![OS Update Overview](images/uc-11.png)
+![Update Compliance workspace view](images/uc-filledworkspaceview.png)
 
+Upon clicking the tile, you will be redirected to the Update Compliance workspace. The workspace is organized with the Overview Blade providing a hub from which to navigate to different reports of your device’s data. 
 
+### Overview Blade
 
-This blade is divided into three sections: 
+![The Overview Blade](images/uc-overviewblade.png)
-- 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. 
+Update Compliance’s overview blade provides a summarization of all the data Update Compliance focuses on. It functions as a hub from which different sections can be navigated to. The total number of devices detected by Update Compliance are counted within the title of this blade. What follows is a distribution for all devices as to whether they are up to date on:
+* Quality updates: A device is up to date on quality updates whenever it has the latest applicable quality update installed. Quality updates are monthly cumulative updates that are specific to a version of Windows 10.
+* Feature updates: A device is up to date on feature updates whenever it has the latest applicable feature update installed. Update Compliance considers [Servicing Channel](waas-overview.md#servicing-channels) when determining update applicability. 
+* AV Signature: A device is up to date on Antivirus Signature when the latest Windows Defender Signatures have been downloaded. This distribution only considers devices that are running Windows Defender Antivirus. 
 
+The blade also provides the time at which your Update Compliance workspace was refreshed. 
 
-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:
+Below the “Last Updated” time, a list of the different sections follows that can be clicked on to view more information, they are:
+* [Need Attention!](update-compliance-need-attention.md) - This section is the default section when arriving to your Update Compliance workspace. It counts the number of devices encountering issues and need attention; clicking into this provides blades that summarize the different issues that devices are encountering, and provides a List of Queries that Microsoft finds useful.
+* [Security Update Status](update-compliance-security-update-status.md) - This section lists the percentage of devices that are on the latest security update released for the version of Windows 10 it is running. Clicking into this section provides blades that summarize the overall status of Quality updates across all devices; including deployment. 
+* [Feature Update Status](update-compliance-feature-update-status.md) - This section lists the percentage of devices that are on the latest feature update that is applicable to a given device. Clicking into this section provides blades that summarize the overall feature update status across all devices, with an emphasis on deployment progress. 
+* [Windows Defender AV Status](update-compliance-wd-av-status.md) - This section lists the percentage of devices running Windows Defender Antivirus that are not sufficiently protected. Clicking into this section provides a summary of signature and threat status across all devices that are running Windows Defender Antivirus. This section is not applicable to devices not running Windows Defender Antivirus.  
 
+Use [Perspectives](update-compliance-perspectives.md) for data views that provide deeper insight into your data.
 
-<TABLE>
+## Utilizing Log Analytics
-<TR><TD BGCOLOR="#cceeff">Needs Attention<TD BGCOLOR="#cceeff" ALIGN=left>Definition
-<TR><TD>Out of Support<TD>Total number of devices that are no longer receiving servicing updates
-<TR><TD>Update failed<TD>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.
-<TR><TD>Missing 2+ Security Updates<TD>Total number of devices that are missing two or more security updates
-<TR><TD>Update Progress Stalled<TD>Total number of devices where an update installation has been “in progress” for more than 7 days
-</TABLE>
 
+Update Compliance is built upon the Log Analytics platform that is integrated into Operations Management Suite. All data within the workspace is the direct result of a query. Understanding the tools and features at your disposal, all integrated within OMS, can deeply enhance your experience and complement Update Compliance. 
 
-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:<BR>
+See below for a few topics related to Log Analytics: 
+* Learn how to effectively execute custom Log Searches by referring to Microsoft Azure’s excellent documentation on [querying data in Log Analytics](https://docs.microsoft.com/azure/log-analytics/log-analytics-log-searches).
+* To develop your own custom data views in Operations Management Suite or [Power BI](https://powerbi.microsoft.com/); check out documentation on [analyzing data for use in Log Analytics](https://docs.microsoft.com/azure/log-analytics/log-analytics-dashboards). 
+* [Gain an overview of Log Analytics’ alerts](https://docs.microsoft.com/azure/log-analytics/log-analytics-alerts) and learn how to utilize it to always stay informed about the most critical issues you care about. 
 
 
-![Device states](images/uc-12.png)
-
-
-Update Status Summary definitions:
-
-
-<TABLE>
-<TR><TD BGCOLOR="#cceeff">Update Status<TD BGCOLOR="#cceeff" ALIGN=left>Definition
-<TR><TD>Current and Up-to-date<TD>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.
-<TR><TD>Up-to-date<TD>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.
-<TR><TD>Not up-to-date<TD>A device does not have the latest quality update for its servicing option.  
-</TABLE>
-
-
-## 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: 
-
-
-![OS Quality Update Status](images/uc-13.png)
-
-
-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. 
-
-
-![Latest security update status](images/uc-14.png)
-
-
-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:
-
-
-<TABLE>
-<TR><TD BGCOLOR="#cceeff">Term<TD BGCOLOR="#cceeff" ALIGN=left>Definition
-<TR><TD>OS Build<TD>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.
-<TR><TD>Version<TD>The OS Version corresponding to the OS build.
-<TR><TD>Installed<TD>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.
-<BR><BR>For the previous security update, a device will display as **Installed** until it has at least installed the latest security update.
-<TR><TD>In Progress or Deferred<TD>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.
-<BR><BR> All devices in this category for Previous Security Update Status are missing 2 or more security updates, and therefore qualify as needing attention.
-<TR><TD>Update Failed<TD>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**.
-<TR><TD>Status Unknown<TD>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.
-</TABLE>
-
-
-## 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:
-
-
-![Overall feature update status](images/uc-15.png)
-
-
-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. 
-
-<a id="wdav-assessment"></a>
-## Windows Defender Antivirus Assessment
-
-You'll notice some new tiles in the Overview blade which provide a summary of Windows Defender AV-related issues, highlighted in the following screenshot.
-
-![Overview blade showing a summary of key Windows Defender Antivirus issues](images/update-compliance-wdav-overview.png)
-
->[!IMPORTANT]
->If your devices are not showing up in the Windows Defender AV assessment section, check the [Troublshoot Windows Defender Antivirus reporting](/windows/threat-protection/windows-defender-antivirus/troubleshoot-reporting) topic for help.
-
-The **AV Signature** chart shows the number of devices that either have up-to-date [protection updates (also known as signatures or definitions)](/windows/threat-protection/windows-defender-antivirus/manage-updates-baselines-windows-defender-antivirus), while the **Windows Defender AV Status** tile indicates the percentage of all assessed devices that are not updated and do not have real-time protection enabled. The Windows Defender Antivirus Assessment section provides more information that lets you investigate potential issues.
-
-If you're using [Windows Defender Antivirus in Windows 10](/windows/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10) to protect devices in your organization and have enabled [cloud-delivered protection](/windows/threat-protection/windows-defender-antivirus/utilize-microsoft-cloud-protection-windows-defender-antivirus), you can use this section to review the overall status of key protection features, including the number of devices that have [always-on real-time protection](/windows/threat-protection/windows-defender-antivirus/configure-real-time-protection-windows-defender-antivirus) and up-to-date definitions.
-
-There are two blades in the Windows Defender AV Assessment section:
-
-- Protection status
-- Threats status
-
-![Windows Defender Antivirus Assessment blade in Update Compliance](images/update-compliance-wdav-assessment.png)
-
-The **Protection Status** blade shows three key measurements:
-
-1. How many devices have old or current signatures (also known as protection updates or definitions)
-2. How many devices have the core Windows Defender AV always-on scanning feature enabled, called real-time protection
-
-
-![Windows Defender Antivirus protection status in Update Compliance](images/update-compliance-wdav-prot-status.png)
-
-See the [Manage Windows Defender AV updates and apply baselines](/windows/threat-protection/windows-defender-antivirus/manage-updates-baselines-windows-defender-antivirus) topic for an overview on how updates work, and further information on applying updates.
-
-The **Threats Status** blade shows the following measurements:
-
-1. How many devices that have threats that have been remediated (removed or quarantined on the device)
-2. How many devices that have threats where remediation was not successful (this may indicate a manual reboot or clean is required)
-
-
-![Windows Defender Antivirus threat status in Update Compliance](images/update-compliance-wdav-threat-status.png)
-
-Devices can be in multiple states at once, as one device may have multiple threats, some of which may or may not be remediated.
-
-> [!IMPORTANT]
-> The data reported in Update Compliance can be delayed by up to 24 hours. 
-
-See the [Customize, initiate, and review the results of Windows Defender AV scans and remediation](/windows/threat-protection/windows-defender-antivirus/customize-run-review-remediate-scans-windows-defender-antivirus) topic for more information on how to perform scans and other manual remediation tasks.
-
-As with other blades in Update Compliance, clicking on a specific measurement or item will open the associated query that you can use to investigate individual devices and issues, as described below. 
-
-
-### Investigate individual devices and threats
-
-
-Click on any of the status measurements to be taken to a pre-built log query that shows the impacted devices for that status.
-
-![Sample Windows Defender AV query in Update Compliance](images/update-compliance-wdav-status-log.png)
-
-You can also find a pre-built query on the main Update Compliance screen, under the **Queries** blade, that lists devices that have not been assessed for Windows Defender AV.
-
-![Overview blade showing a summary of key Windows Defender Antivirus issues](images/update-compliance-wdav-query-not-assessed.png)
-
-
-
-
-
-
-
-
-You can further filter queries by clicking any of the measurement labels for each incident, changing the values in the query filter pane, and then clicking **Apply**.
-
-![Click the Apply button on the left pane](images/update-compliance-wdav-status-filter-apply.png)
-
-
-
-Click **+Add** at the bottom of the filter pane to open a list of filters you can apply.
-
-![Click Add to add more filters](images/update-compliance-wdav-status-add-filter.png)
-
-
-You can also click the **. . .** button next to each label to instantly filter by that label or value.
-
-![Click the elipsis icon to instantly filter by the selected label](images/update-compliance-wdav-status-filter.png)
-
-You can create your own queries by using a query string in the following format:
-
-```
-Type:<Group type> <Label>="<Value>"
-```
-
-You can use the following `<Group type>` options to scope your query:
-- `Type:WDAVStatus` to query information related to signature and real-time protection status
-- `Type:WDAVThreat` to query information about threat remediation and specific threats
-
-
-The `<Label>`, and `<Value>` fields are listed in the following table. All labels and values are case sensitive and must be entered as written below (including spaces).
-
-
-For queries that use `Type:WDAVStatus`, you can use the following labels and values.
-
-Label | Value
----|---
-`Computer`|\<computer name>
-`ComputerID`|\<computer ID>
-`OSName`|\<Operating system name>
-`UpdateStatus`|`Not assessed` <br />`Signature up-to-date` <br />`Signature out-of-date`
-`DetailedStatus`|`Unknown` <br />`Non-Microsoft AV` <br />`No AV` <br />`AV expired` <br />`Disabled by GP` <br />`Disabled by LP` <br />`Recently disappeared`
-`ProtectionState`|`Real-time protection is off `<br />`Real-time protection is on`
-`MoreInformation`| \<free text string>
-`LastScan`| \<date and time of the last scan>
-
-
-
-For queries that use `Type:WDAVThreat`, you can use the following labels and values.
-
- Label | Value
- ---|---
-`Computer`|\<computer name>
-`ComputerID`|\<computer ID>
-`ThreatName`|\<detected threat name>
-`ThreatStatus`|`Remediation failed`<br/>`Remediated`
-`ThreatAction`|`Remediation pending reboot`
-`ThreatError`|`Disk full`<br/>`Network issue`<br/>`Operation aborted`
-`MoreInformation`|\<free text string>
-`LastScan`|\<date and time of the last scan>
-
-
-You can add multiple label-value pairs in the same query to refine and filter the results.
-
-![Add multiple value and name pairs in your query, separated by spaces](images/update-compliance-wdav-status-query.png)
-
-
-
-## 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:
-
-
-![CB deployment status](images/uc-16.png)
-
-
-The three tables break down devices by feature update. For each OS version, the following columns provide counts of the possible device states:
-
-
-<TABLE>
-<TR><TD BGCOLOR="#cceeff">Deployment Status<TD BGCOLOR="#cceeff" ALIGN=left>Description
-<TR><TD>Feature Update<TD>A concatenation of servicing branch (CB, CBB, LTSB) and OS Version (e.g., 1607)
-<TR><TD>Installed<TD>The number of devices that have reported to be on the given servicing train and feature update.
-<TR><TD>In progress<TD>The number of devices that have reported to be at some stage in the installation process for the given feature update.
-<BR><BR>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**. 
-<TR><TD>Scheduled next 7 days<TD>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.
-<BR><BR>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**
-<TR><TD>Update Failed<TD>The total number of devices that were **In progress** with the installation for the given feature update, but encountered a failure.
-<BR><BR>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**.
-<TR><TD>Status Unknown<TD>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**.
-<BR><BR>Devices that Update Compliance knows belongs to your organization, but it does not know update failures or installation progress, will be counted here. 
-</TABLE>
-
-
-## 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 build summary](images/uc-17.png)
-
- 
-### 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 Deferral Configurations](images/uc-18.png)
-
- 
-### 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:
-
-
-![Quality Update Deployment Status](images/uc-19.png)
-
-
-See the following table for a description of last reported states for devices deploying that quality update. 
-
-
-<TABLE>
-<TR><TD BGCOLOR="#cceeff">Deployment State<TD BGCOLOR="#cceeff" ALIGN=left>Description
-<TR><TD>Update Completed<TD>When a device has finished the update process and is on the given update, it will display here as **Update completed**.
-<TR><TD>In Progress<TD>Devices that are “in progress” installing an update will fall within this category. This category is detailed in the following blade: **Detailed Deployment Status**.
-<TR><TD>Deferred<TD>If a device’s WUfB deferral policy dictates that it is not set to receive this update, the device will show as Update deferred.
-<TR><TD>Cancelled<TD>A device will report that the update has been cancelled if the user, at some point, cancelled the update on the device.
-<TR><TD>Blocked<TD>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.
-</TABLE>
-
-<P>
-
-
-### 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:
-
-
-![Quality Update Detailed Deployment Status](images/uc-20.png)
-
-
->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:
-
-
-<TABLE>
-<TR><TD BGCOLOR="#cceeff">Detailed Deployment State<TD BGCOLOR="#cceeff" ALIGN=left>Description
-<TR><TD>Update deferred<TD>The WUfB policy of the device dictates the update is deferred. 
-<TR><TD>Pre-Download Tasks Passed<TD>The device has finished all tasks necessary prior to downloading the update. 
-<TR><TD>Download Started<TD>The update has begun downloading on the device. 
-<TR><TD>Download Succeeded<TD>The device has successfully downloaded the update. 
-<TR><TD>Pre-Install Tasks Passed<TD>The device has downloaded the update successfully, and successfully passed all checks prior to beginning installation of the update. 
-<TR><TD>Install Started<TD>The device has begun installing the update. 
-<TR><TD>Reboot Required<TD>The device has finished installing the update, and a reboot is required before the update can be completed. 
-<TR><TD>Reboot Pending<TD>The device is pending a scheduled reboot before the update can be completed. 
-<TR><TD>Reboot Initiated<TD>The device has reported to have initiated the reboot process for completing the update. 
-<TR><TD>Update completed<TD>The device has completed installing, rebooting, and applying the update. 
-</TABLE>
-
-
-## 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 Build Summary](images/uc-21.png)
-
-### Feature Update Deferral Configuration
-
-
-This blade shows all deferral configurations for the devices on the given build. See the following example:
-
-
-![Feature Update Deferral Configuration](images/uc-22.png)
-
-
-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:
-
-
-![Feature Update Deployment Status](images/uc-23.png)
-
-
-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:
-
-
-<TABLE>
-<TR><TD BGCOLOR="#cceeff">Deployment State<TD BGCOLOR="#cceeff" ALIGN=left>Description
-<TR><TD>Update completed<TD>When a device has completely finished the update process and is on the given update, it will show up here as **Update completed**. 
-<TR><TD>Inprogress<TD>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”. 
-<TR><TD>Update deferred<TD>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.
-<TR><TD>Cancelled<TD>A device will report that the update has been cancelled if the user, at some point, cancelled the update on the device. 
-<TR><TD>Blocked<TD>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. 
-</TABLE>
-
-<P>
-
-
-
-
-
-
-### 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:
-
-
-![Feature Update Detailed Deployment Status](images/uc-24.png)
-
-
-The following table displays all states a device can report:
-
-
-<TABLE>
-<TR><TD BGCOLOR="#cceeff">Detailed Deployment State<TD BGCOLOR="#cceeff" ALIGN=left>Description
-<TR><TD>Update deferred<TD>The WUfB policy of the device dictates the update is deferred.
-<TR><TD>Pre-Download Tasks Passed<TD>The device has finished all tasks necessary prior to downloading the update.
-<TR><TD>Download Started<TD>The update has begun downloading on the device.
-<TR><TD>Download Succeeded<TD>The device has successfully downloaded the update.
-<TR><TD>Pre-Install Tasks Passed<TD>The device has downloaded the update successfully, and successfully passed all checks prior to beginning installation of the update.
-<TR><TD>Install Started<TD>The device has begun installing the update.
-<TR><TD>Reboot Required<TD>The device has finished installing the update, and a reboot is required before the update can be completed.
-<TR><TD>Reboot Pending<TD>The device is pending a scheduled reboot before the update can be completed.
-<TR><TD>Reboot Initiated<TD>The device has reported to have initiated the reboot process for completing the update.
-<TR><TD>Update completed<TD>The device has completed installing, rebooting, and applying the update.
-</TABLE>
-
-
-
-## 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:
-
-
-![List of Queries](images/uc-25.png)
-
-
-The following **Common queries** are available:
-
-
-<TABLE>
-<TR><TD BGCOLOR="#cceeff">Query Title<TD BGCOLOR="#cceeff" ALIGN=left>Description
-<TR><TD>OS Security Update Status<TD>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. 
-<TR><TD>Update Deployment Failures<TD>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. 
-<TR><TD>Devices pending reboot to complete update<TD>This query will provide a table showing all devices that are at the stage of "Reboot Pending" In the update deployment process.<BR><BR>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.
-<TR><TD>Servicing Option Distribution for the devices<TD>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.) 
-<TR><TD>Deferral configurations for Feature Update<TD>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.<BR><BR>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. 
-<TR><TD>Pause configurations for Feature Update<TD>The WUfB policy 
-<TR><TD>Update deferred<TD>This query provides a chart view displaying the breakdown of devices that are either paused, or not paused for feature updates.<BR><BR>“Not configured” means the device is not paused. “Paused” means it is currently paused.
-<TR><TD>Deferral configurations for Quality Update<TD>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.<BR><BR>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.
-<TR><TD>Pause configurations for Quality Update<TD>This query provides to a chart view displaying the breakdown of devices that are either paused, or not paused for quality updates.<BR><BR>**Not configured** means the device is not paused. **Paused** means it is currently paused. 
-</TABLE>
-
 ## Related topics
 
 [Get started with Update Compliance](update-compliance-get-started.md)

windows/deployment/update/update-compliance-wd-av-status.md

@@ -0,0 +1,28 @@
+---
+title: Update Compliance - Windows Defender AV Status report
+description: an overview of the Windows Defender AV Status report
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.pagetype: deploy
+author: DaniHalfin
+ms.author: daniha
+ms.date: 10/17/2017
+---
+
+# Windows Defender AV Status
+
+![The Windows Defender AV Status report](images/uc-windowsdefenderavstatus.png)
+
+The Windows Defender AV Status section deals with data concerning signature and threat status for devices that use Windows Defender Antivirus. The section tile in the [Overview Blade](update-compliance-using.md#overview-blade) provides the percentage of devices with insufficient protection – this percentage only considers devices using Windows Defender Antivirus. 
+
+The **Protection Status** blade gives a count for devices that have either out-of-date signatures or real-time protection turned off. Below, it gives a more detailed breakdown of the two issues. Clicking any of these statuses will navigate you to a Log Search view containing the query. 
+
+The **Threat Status** blade provides a visualization of, for devices that have encountered threats, how many were and were not remediated successfully. It also provides a detailed count. Clicking either of these will navigate to the respective query in Log Search for further investigation. 
+
+Here are some important terms to consider when utilizing the Windows Defender AV Status section of Update Compliance:
+* **Signature out of date** devices are devices with signature older than 14 days.
+* **No real-time protection** devices are devices who are using Windows Defender AV but have turned off Real-time protection.
+* **Recently disappeared** devices are devices that were previously seen by Windows Defender AV and are no longer seen in the past 7 days.
+* **Remediation failed** devices are devices where Windows Defender AV failed to remediate the threat. This can be due to reason like disk full, network error, operation aborted, etc. Manual intervention may be needed from IT team.
+* **Not assessed** devices are devices where either a third-party AV solution is used or it has been more than 7 days since the device recently disappeared.

windows/deployment/update/waas-windows-insider-for-business-aad.md

@@ -16,7 +16,7 @@ ms.author: daniha
 
 - Windows 10
 
-> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
+> **Looking for information about Windows 10 for personal or home use?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
 
 We recently added features and benefits to better support the IT Professionals and business users in our Insider community. This includes the option to download Windows 10 Insider Preview builds using your corporate credentials in Azure Active Directory (AAD). By enrolling devices in AAD, you increase the visibility of feedback submitted by users in your organization – especially on features that support your specific business needs. 
 
@@ -30,15 +30,25 @@ We recently added features and benefits to better support the IT Professionals a
 
 In order to get the most benefit out of the Windows Insider Program for Business, organizations should not use a test tenant of AAD. There will be no modifications to the AAD tenant to support the Windows Insider Program as it will only be used as an authentication method.
 
+## Register your organization's Azure AD domain to the Windows Insider Program for Business
+Rather than have each user in your organization register for Windows 10 Insider Preview builds, you can now simply register your domain – and cover all users with just one registration.
+
+1. On the [Windows Insider](https://insider.windows.com) website, go to **For Business > Getting Started** to [register you organizational Azure AD account](https://insider.windows.com/en-us/insidersigninaad/).
+2. **Register your domain**. Rather than have each user register individually for Insider Preview builds, administrators can simply [register their domain](https://insider.windows.com/en-us/for-business-organization-admin/) and control settings centrally.
+
+>[!IMPORTANT]
+>The signed-in user needs to be a **Global Administrator** of the Azure AD domain in order to be able to register the domain.
+
 ## Check if a device is connected to your company’s Azure Active Directory subscription
 Simply go to **Settings > Accounts > Access work or school**. If a corporate account is on Azure Active Directory and it is connected to the device, you will see the account listed as highlighted in the image below.
 
 ![Device connected to Work Account](images/waas-wipfb-work-account.jpg)
 
 ## Enroll a device with an Azure Active Directory account
-1. Visit [insider.windows.com](https://insider.windows.com). Sign-in with your corporate account in AAD and follow the on-screen registration directions. 
+1. Navigate to the [**Getting Started**](https://insider.windows.com/en-us/getting-started/) page on [Windows Insider](https://insider.windows.com).
-2. On your Windows 10 device, go to **Settings > Updates & Security >  Windows Insider Program**. 
+2. Go to the **Register your organization account** and follow the instructions.
-3. Enter the AAD account that you used to register and follow the on-screen directions. 
+3. On your Windows 10 device, go to **Settings > Updates & Security >  Windows Insider Program**. 
+4. Enter the AAD account that you used to register and follow the on-screen directions. 
 
 >[!NOTE]
 >Make sure that you have administrator rights to the machine and that it has latest Windows updates. 
@@ -61,7 +71,7 @@ With the current version of the Feedback Hub app, we need the user's consent to
 
 ![Feedback Hub consent to AAD pop-up](images/waas-wipfb-aad-consent.png)
 
-Once agreed, everything will work fine and that user won't be prompted for permission again.
+Once agreed, everything will work fine, and that user won't be prompted for permission again.
 
 ### Something went wrong
 
@@ -73,7 +83,7 @@ In case the administrators blocked this option, when the user signs in with the
 
 This blocks the user from signing in, which means they won't be able to use the Feedback Hub app with their AAD credentials.
 
-**To fix this issue**, an adminsitrator of the AAD directory will need to enable user consent for apps to access their data.
+**To fix this issue**, an administrator of the AAD directory will need to enable user consent for apps to access their data.
 
 To do this through the **classic Azure portal**:
 1. Go to https://manage.windowsazure.com/ .

windows/deployment/update/waas-windows-insider-for-business-faq.md

@@ -16,13 +16,13 @@ ms.author: daniha
 
 - Windows 10
 
-> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
+> **Looking for information about Windows 10 for personal or home use?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
 
 ### Are the Windows Insider Program and Windows Insider Program for Business separate programs?
 No, in fact just the opposite. The Windows Insider Program was created in 2014 to help Microsoft engage with Windows Fans worldwide. Windows Insiders are the first to be able to try new Windows features that we introduce through Windows 10 Insider Preview Builds. At the same time, they can provide feedback through the Feedback Hub App which helps create even better versions of Windows for all users. The Windows Insider Program for Business enables you to incorporate Insider Preview builds into your deployment plans using your corporate credentials, deepen connections with the IT Pro community, collect feedback within your organization, and increase the visibility of your organization’s feedback – especially on features that support productivity and business needs. Together we can resolve blocking or critical issues to better support your organization’s needs sooner. Incorporating the Windows Insider Program for Business into your deployment plans enables you to prepare your organization for the next update of Windows 10, to deploy new services and tools more quickly, to help secure your applications, and to increase productivity and confidence in the stability of your environment. Windows Insider Program for Business participants collaborate with the Windows team to build and document features, infuse innovation, and plan for what’s around the bend. We’ve architected some great features together, received amazing feedback, and we’re not done.
 
 ### What Languages are available? 
-Insider Preview builds are available in the following languages: English (United States), English (United Kingdom), Chinese (Simplified), Chinese (Traditional), Portuguese (Brazilian), Japanese,Russian, German, French, French (Canada), Korean, Italian, Spanish, Spanish (Latin America), Swedish, Finnish, Turkish, Arabic, Dutch, Czech, Polish, Thai, Catalan, Hindi, and Vietnamese.
+Insider Preview builds are available in the following languages: English (United States), English (United Kingdom), Chinese (Simplified), Chinese (Traditional), Portuguese (Brazilian), Japanese, Russian, German, French, French (Canada), Korean, Italian, Spanish, Spanish (Latin America), Swedish, Finnish, Turkish, Arabic, Dutch, Czech, Polish, Thai, Catalan, Hindi, and Vietnamese.
 
 If your Windows build is not in one of the available base languages, you will not receive Insider Preview builds.
 
@@ -31,7 +31,7 @@ Hindi, Catalan, and Vietnamese can only be installed as a language pack over [su
 >[!NOTE]
 > To learn how to install a language pack, see [How to add an input language to your PC Additional](https://support.microsoft.com/instantanswers/60f32ff8-8697-4452-af7d-647439c38433/how-to-add-and-switch-input-languages-on-your-pc).
 
-### How do I register for  the Windows Insider Program for Business? 
+### How do I register for the Windows Insider Program for Business? 
 To register for the Windows Insider Program for Business, follow the steps below using your corporate account in Azure Active Directory (AAD). This account is the same account that you use for Office 365 and other Microsoft services. 
 
 1. Visit https://insider.windows.com and click **Get Started**. 
@@ -41,12 +41,23 @@ To register for the Windows Insider Program for Business, follow the steps below
 >[!NOTE]
 >Make sure that you have administrator rights to your machine and that it has latest Windows updates.
 
+### Are there any management capabilities that allow an IT admin to manage settings for a corporate environment? 
+Yes. Starting with Windows 10, version 1709, the Windows Insider Program for Business now enables administrators to apply the following group policies to help them manage their organization’s preview builds: 
+ 
+**Manage preview builds:** Administrators can enable or prevent builds from installing on a device. You also have an option to disable preview builds once the release is public.    
+**Branch Readiness Level:** Administrators can set the Windows readiness level, including Fast, Slow, Release Preview Rings of Windows Insider Preview) and allows administrators to defer or pause delivery of updates.  
+
+See more information on the [Getting started with Windows Insider Program for Business](waas-windows-insider-for-business.md#getting-started-with-windows-insider-program-for-business) section.
+
 ### How can I find out if my corporate account is on Azure Active Directory? 
 On your PC, go to **Settings > Accounts > Access work or school**. If your organization has set up your corporate account in Azure Active Directory and it is connected to your PC, you will see the account listed.  
 
 ### I have more than one Azure Active Directory account. Which should I use? 
 Register for Windows Insider Program for Business with the same active account that you use to access your corporate email in Office 365 and other Microsoft services. To ensure you get the most benefit out of the Windows Insider Program for Business and that your company is fully represented, do not set up a separate tenant for testing activities. There will be no modifications to the AAD tenant to support Windows Insider Program for Business, and it will only be used as an authentication method. 
 
+### Can I register multiple users from my organization at the same time for the Windows Insider Program for Business? 
+Yes. The Windows Insider Program for Business now allows organizations to register their domain and control settings centrally rather than require each user to register individually for Insider Preview builds. In order to register, follow instructions on the [Getting started with Windows Insider Program for Business](waas-windows-insider-for-business.md#getting-started-with-windows-insider-program-for-business) section.
+
 ### My account is listed in Active Directory but not Azure Active Directory. Can I still register using my Active Directory credentials?
 No. At this point, we are only supporting Azure Active Directory as a corporate authentication method. If you’d like to suggest or upvote another authentication method, please visit this [forum](https://answers.microsoft.com/en-us/insider/forum/insider_wintp).
 

windows/deployment/update/waas-windows-insider-for-business.md

@@ -16,35 +16,54 @@ ms.author: daniha
 
 - Windows 10
 
-> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
+> **Looking for information about Windows 10 for personal or home use?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
 
-For many IT pros, gaining visibility into feature updates early—before they’re available to the CB servicing branch—can be both intriguing and valuable for future end user communications as well as provide additional prestaging for CB machines. With Windows 10, feature flighting enables Windows Insiders to consume and deploy preproduction code to their test machines, gaining early visibility into the next build. Testing the early builds of Windows 10 helps both Microsoft and its customers because they have the opportunity to discover possible issues before the update is ever publicly available and can report it to Microsoft. Also, as flighted builds get closer to their release to CB, organizations can test their deployment on test devices for compatibility validation.
+For many IT pros, gaining visibility into feature updates early, before they’re available to the Semi-Annual Channel, can be both intriguing and valuable for future end user communications as well as provide additional prestaging for Semi-Annual Channel devices. With Windows 10, feature flighting enables Windows Insiders to consume and deploy preproduction code to their test devices, gaining early visibility into the next build. Testing the early builds of Windows 10 helps both Microsoft and its customers because they have the opportunity to discover possible issues before the update is ever publicly available and can report it to Microsoft. Also, as flighted builds get closer to their release to the Semi-Annual Channel, organizations can test their deployment on test devices for compatibility validation.
 
 The Windows Insider Program for Business gives you the opportunity to: 
 * Get early access to Windows Insider Preview Builds. 
 * Provide feedback to Microsoft in real-time via the Feedback Hub app.
 * Sign-in with corporate credentials (Azure Active Directory) and increase the visibility of your organization's feedback with Microsoft – especially on features that support your productivity and business needs.
+* Register your Azure AD domain into the program, to cover all users within your organization with just one registration.
+* Starting with Windows 10, version 1709, enable, disable, defer and pause the installation of preview builds through policies.
+* Track feedback provided through the Feedback Hub app, across your organization.
 
 
 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. 
+The Windows Insider Program isn’t intended to replace Semi-Annual Channel 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. 
+
+>[!IMPORTANT]
+>The **Allow Telemetry** setting has to be set to 2 or higher, to receive Insider preview builds.
+>
+>The setting is available in **Group Policy**, through **Computer Configuration/Administrative Templates/Windows Components/Data Collection and Preview Builds - Allow Telemetry** or in **MDM**, through **System/AllowTelemetry**. 
 
 ## Getting started with Windows Insider Program for Business
 
 To get started with the Windows Insider Program for Business, you will need to follow a few simple steps:
 
-1. Navigate to [insider.windows.com](https://insider.windows.com) and go to **Get Started**.
+1. On the [Windows Insider](https://insider.windows.com) website, go to **For Business > Getting Started** to [register you organizational Azure AD account](https://insider.windows.com/en-us/insidersigninaad/).
-2. Sign-in with you desired account. It can be either a Microsoft Account or your organizational Azure Active Directory Account.
+2. **Register your domain**. Rather than have each user register individually for Insider Preview builds, administrators can simply [register their domain](https://insider.windows.com/en-us/for-business-organization-admin/) and control settings centrally.</br>**Note:** The signed-in user needs to be a **Global Administrator** of the Azure AD domain in order to be able to register the domain.
+3. Make sure the **Allow Telemetry** setting is set to **2** or higher.
+4. Starting with Windows 10, version 1709, set policies to manage preview builds and their delivery:
 
-![Account Types](images/waas-wipfb-accounts.png)
+The **Manage preview builds** setting, gives administrators control over enabling or disabling preview build installation on a device. You can also decide to stop preview builds once the release is public.
+* Group Policy: **Computer Configuration/Administrative Templates/Windows Components/Windows Update/Windows Update for Business** - *Manage preview builds*
+* MDM: **Update/ManagePreviewBuilds**
 
+The **Branch Readiness Level** settings, allows you to choose between preview flight rings, and allows you to defer or pause the delivery of updates.
+* Group Policy: **Computer Configuration/Administrative Templates/Windows Components/Windows Update/ Windows Update for Business** - *Select when Preview Builds and Feature Updates are received*
+* MDM: **Update/BranchReadinessLevel**
+
+![Select when Preview Builds and Feature Updates are received group policy](images/waas-wipfb-policy1.png)
+
+If you want to control Windows 10 devices prior to version 1709, follow these simple steps:
+
+1. Navigate to the [**Getting Started**](https://insider.windows.com/en-us/getting-started/) page on [Windows Insider](https://insider.windows.com).
+2. Go to the **Register your organization account** and follow the instructions.
 3. Enroll your device by going to **Start > Settings > Update & security > Windows Insider Program** and selecting **Get Started**. Sign-in using the account you used to register for the Windows Insider Program.
 4. After reading the privacy statement and clicking **Next**, **Confirm** and schedule a restart.
-
+5. 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. 
-## 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. 
 
 >[!TIP]
 >Flighting rings are used to evaluate the quality of our software as it is released to progressively larger audiences. We will flight a Feature Update, application, etc. to the first ring if it passes all required automated testing in the lab. The flight will continue to be evaluated against a set of criteria to ensure it is ready to progress to the next ring.
@@ -53,12 +72,12 @@ The options for Insider level are:
 
 ### Release Preview
 
-Best for Insiders who enjoy getting early access to updates for the Current Branch, Microsoft applications, and drivers, with minimal risk to their devices, and still want to provide feedback to make Windows devices great.
+Best for Insiders who enjoy getting early access to updates for the Semi-Annual Channel, Microsoft applications, and drivers, with minimal risk to their devices, and still want to provide feedback to make Windows devices great.
 
-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.
+Insiders on this level receive builds of Windows just before Microsoft releases them to the Semi-Annual Channel. 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.
 
-* The Release Preview Ring will only be visible when your Windows build version is the same as the Current Branch.
+* The Release Preview Ring will only be visible when your Windows build version is the same as the Semi-Annual Channel.
-* The easiest way to go between the Development Branch to the Current Branch is to use the [Media Creation Tool](http://go.microsoft.com/fwlink/?LinkId=691209) (for PC) or [Windows Device Recovery Tool](http://go.microsoft.com/fwlink/p/?LinkId=522381) (for Mobile) to reinstall Windows.  
+* The easiest way to go from a Preview build to the Semi-Annual Channel is to use the [Media Creation Tool](http://go.microsoft.com/fwlink/?LinkId=691209) (for PC) or [Windows Device Recovery Tool](http://go.microsoft.com/fwlink/p/?LinkId=522381) (for Mobile) to reinstall Windows.  
 
 ### Slow
 
@@ -70,12 +89,12 @@ The Slow Windows Insider level is for users who enjoy seeing new builds of Windo
 
 ### Fast
 
-Best for Insiders who enjoy being the first to get access to builds and feature upgrades, with some risk to their devices in order to identify issues, and provide suggestions and ideas to make Windows software and devices great.
+Best for Insiders who enjoy being the first to get access to builds and feature updates, with some risk to their devices in order to identify issues, and provide suggestions and ideas to make Windows software and devices great.
 
 * Windows Insiders with devices in the Fast Ring should be prepared for more issues that may block key activities that are important to you or may require significant workarounds. 
 * Because we are also validating a build on a smaller set of devices before going to Fast, there is also a chance that some features may work on some devices but may fail in other device configurations. 
 * Windows Insiders should be ready to reinstall Windows using the [Media Creation Tool](http://go.microsoft.com/fwlink/?LinkId=691209) or [Windows Device Recovery Tool](http://go.microsoft.com/fwlink/p/?LinkId=522381) when you are significantly blocked.
-* Please remember to report any issue to us through the Windows Insider Feedback Hub or the Windows Insider community Forum.
+* Please remember to report any issue to us through the Windows Insider Feedback Hub or the Windows Insider community forum.
 
 >[!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.
@@ -90,11 +109,16 @@ During your time in the Windows Insider Program, you may want to change between
   * [Windows Insider Slow](#slow)
   * [Release Preview](#release-preview)
 
+Starting with Windows 10, version 1709, use the **Branch Readiness Level** to switch between flight rings. 
+* Group Policy: **Computer Configuration/Administrative Templates/Windows Components/Windows Update/ Windows Update for Business** - *Select when Preview Builds and Feature Updates are received*
+* MDM: **Update/BranchReadinessLevel**
+
 ## How to switch between your MSA and your Corporate AAD account
 
 The Windows Insider Program for Business now gives users the option to register and enroll devices using a corporate account in [Azure Active Directory](https://azure.microsoft.com/services/active-directory/) (AAD) as well as their Microsoft Account (MSA).
 
 To switch between accounts, go to **Settings > Updates & Security >  Windows Insider Program**, and under **Windows Insider account** select **Change**.
+
 ![Change Windows Insider account](images/waas-wipfb-change-user.png)
 
 >[!NOTE]
@@ -108,6 +132,9 @@ When providing feedback, please consider the following:
 2. Check for existing feedback on the topic you are preparing to log. Another user may have already shared the same feedback. If they have, please “upvote” the existing feedback to help prevent duplicate submissions. Adding additional comments to existing feedback can help others by providing clarity to existing information or additional scenarios to review. 
 3. Provide as much information to us as possible: include reproduction steps, screenshots, any detail you think would help us experience the issue as you have, so that we can work on a fix and get it into a new build as soon as possible.
 
+>[!TIP]
+>You can then track feedback provided by all users in your organization through the Feedback Hub. Simply filter by **My Organization**. 
+
 ### How to use your corporate AAD account for additional Feedback Hub benefits 
 Get even more out of the Feedback Hub by signing in to the Feedback Hub using the same corporate account in AAD that you're using to flight builds. One of the benefits of submitting feedback using your AAD account is the addition of a page to the Feedback Hub for your organization. Simply click the **My Company** page in the feedback hub to see and upvote all feedback submitted by other Insiders in your organization.
 
@@ -115,9 +142,9 @@ Get even more out of the Feedback Hub by signing in to the Feedback Hub using th
 >If you signed into the Feedback Hub previously with your MSA, your feedback and badges will not be transferred to your AAD sing-in. However, you can switch back to your MSA account in the Feedback Hub to access feedback you’ve submitted and badges you’ve earned.
 
 >[!IMPORTANT]
->With the current version of the Feedback Hub app, we need the user's consent to access their AAD account profile data (We read their name, organizational tenant ID and user ID). When they sign in for the first time with the AAD account, they will se a popup asking for their permissions. Once agreed, everything will work fine and that user won't be asked for permissions again.
+>With the current version of the Feedback Hub app, we need the user's consent to access their AAD account profile data (We read their name, organizational tenant ID and user ID). When they sign in for the first time with the AAD account, they will see a popup asking for their permissions. Once agreed, everything will work fine, and that user won't be asked for permissions again.
 >
-> If something goes wrong, it is possible that users aren't enabled to give persmissions to access their data. This can be resolved through the AAD portal. For more information about this, please see [User consent requirement](waas-windows-insider-for-business-aad.md#user-consent-requirement).
+> If something goes wrong, it is possible that users aren't enabled to give permissions to access their data. This can be resolved through the AAD portal. For more information about this, please see [User consent requirement](waas-windows-insider-for-business-aad.md#user-consent-requirement).
 
 ## Not receiving Windows 10 Insider Preview build updates?
 
@@ -142,10 +169,10 @@ Open **Settings > Update & Security > Windows Insider Program** and select your
 If so, please double-check your flight settings under **Settings > Update & Security > Windows Insider Program**.
 
 ### Did you do a clean install? 
-After a clean-install and initial setup of a Microsoft or coporate account (even one that has been used previously for flighting) the appropriate targeting needs to take place for your PC. This background process is known as Compatibility Checker and will run during idle time on your PC. This process may take up to 24 hours. Please leave your PC turned on to ensure this occurs in timely manner. 
+After a clean-install and initial setup of a Microsoft or corporate account (even one that has been used previously for flighting) the appropriate targeting needs to take place for your PC. This background process is known as Compatibility Checker and will run during idle time on your PC. This process may take up to 24 hours. Please leave your PC turned on to ensure this occurs in timely manner. 
 
 ### Are there known issues for your current build?
-On rare occasion, there may be an issue with a build that could lead to issues with updates being received. Please check the most recent Blog Post or reach out to the Windows Insider team on Twitter for verification (*@WindowsInsider*). You can also check the **Feedback Hub** for announcments and known issues.
+On rare occasion, there may be an issue with a build that could lead to issues with updates being received. Please check the most recent Blog Post or reach out to the Windows Insider team on Twitter for verification (*@WindowsInsider*). You can also check the **Feedback Hub** for announcements and known issues.
 
 ## Exiting flighting
 
@@ -154,6 +181,7 @@ After you’ve tried the latest Insider Preview builds, you may want to opt out.
 ## Additional help resources
 
 * [**Windows Blog**](https://blogs.windows.com/blog/tag/windows-insider-program/) - With each new build release we publish a Windows Blog post that outlines key feature changes as well as known issues that Insiders may encounter while using the build.
+* [**Microsoft Technical Community for Windows Insiders**](https://techcommunity.microsoft.com/t5/Windows-Insider-Program/bd-p/WindowsInsiderProgram) - Engage with Windows Insiders around the world in a community dedicated to the Windows Insider Program.
 * [**Windows Insider Preview community forum**](https://answers.microsoft.com/en-us/insider/forum/insider_wintp) - Answers is Microsoft’s forum platform and there is an entire area dedicated to the Windows Insider Program. Insiders can filter between PC, Office, Edge, and many others.
 
 ## Learn More
@@ -165,7 +193,7 @@ After you’ve tried the latest Insider Preview builds, you may want to opt out.
 - [Overview of Windows as a service](waas-overview.md)
 - [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md)
 - [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md)
-- [Assign devices to servicing branches for Windows 10 updates](waas-servicing-branches-windows-10-updates.md)
+- [Assign devices to servicing channels for Windows 10 updates](waas-servicing-channels-windows-10-updates.md)
 - [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md)
 - [Manage updates using Windows Update for Business](waas-manage-updates-wufb.md)
 - [Manage Windows 10 updates using Windows Server Update Services (WSUS)](waas-manage-updates-wsus.md)

windows/whats-new/get-started-with-1709.md

@@ -0,0 +1,45 @@
+---
+title: Get started with Windows 10, version 1709
+description: All the information to get you started with Windows 10, version 1709.
+keywords: ["get started", "windows 10", "fall creators update", "1709"]
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+author: DaniHalfin
+ms.author: daniha
+ms.date: 10/17/2017
+ms.localizationpriority: high
+---
+
+# Get started with Windows 10, version 1709
+
+**Applies to**
+
+-   Windows 10
+
+> **Looking for information about Windows 10 for personal or home use?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq) 
+
+Welcome to Windows 10, version 1709, also known as the Fall Creators Update. Use the following information to learn about new features, review system requirements, and plan your deployment of the latest version of Windows 10.
+
+## Specification and systems requirements 
+
+Before you install any version of Windows 10, make sure you visit the [Windows 10 Specifications & Systems Requirements](https://www.microsoft.com/windows/windows-10-specifications) page. This page contains the minimum systems requirements and important notes to install Windows 10, as well as feature deprecation information and additional requirements to use certain features.
+
+## What's new in Windows 10, version 1709 IT pro content
+
+Take a look at the [What's new in Windows 10, version 1709 IT pro content](whats-new-windows-10-version-1709), for the latest updates in content. Use this topic to easily navigate the documentation for the new features in Windows 10, version 1709.
+
+## Windows 10 release information and update history
+
+To view availability dates and servicing options for each version and update of Windows, including version 1709, visit the [Windows 10 release information](https://technet.microsoft.com/windows/mt679505.aspx) page. For further details on each update, go to the [Windows 10 update history](https://support.microsoft.com/help/4018124/windows-10-update-history) page.
+
+## Windows 10 Roadmap
+
+If you'd like to gain some insight into preview, or in-development features, visit the [Windows 10 Roadmap](https://www.microsoft.com/en-us/WindowsForBusiness/windows-roadmap) page. You'll be able to filter by feature state and product category, to make this information easier to navigate.
+
+## Top support solutions for Windows 10
+
+Having problems with your latest deployment of Windows 10, version 1709? Check out the [Top support solutions for Windows 10](/windows/client-management/windows-10-support-solutions) topic, where we've collected the top Microsoft Support solutions for the most common issues experienced when using Windows 10 in an enterprise or IT pro environment.
+
+
+> Want even more information? Visit the [Windows 10 lifecycle page](https://www.microsoft.com/itpro/windows-10) on the [Windows IT Pro Center](https://itpro.windows.com).