add readiness schema, edits

windows/deployment/TOC.yml

@@ -211,18 +211,20 @@
                 href: update/update-compliance-v2-schema.md
               - name: UCClient
                 href: update/update-compliance-v2-schema-ucclient.md
+              - name: UCClientReadinessStatus
+                href: update/update-compliance-v2-schema-ucclientreadinessstatus.md               
               - name: UCClientUpdateStatus
                 href: update/update-compliance-v2-schema-ucclientupdatestatus.md
+              - name: UCDeviceAlert
+                href: update/update-compliance-v2-schema-ucdevicealert.md                                
               - name: UCServiceUpdateStatus
                 href: update/update-compliance-v2-schema-ucserviceupdatestatus.md
               - name: UCUpdateAlert
-                href: update/update-compliance-v2-schema-ucupdatealert.md
+                href: update/update-compliance-v2-schema-ucupdatealert.md                                                                         
-              - name: UCDeviceAlert
+          - name: Monitor updates with Update Compliance
-                href: update/update-compliance-v2-schema-ucdevicealert.md                                                                              
-          - name: Monitor updates with Update Compliance (GA)
             href: update/update-compliance-monitor.md
             items:
-            - name: Get started (GA)
+            - name: Get started
               items: 
               - name: Get started with Update Compliance
                 href: update/update-compliance-get-started.md
@@ -232,7 +234,7 @@
                 href: update/update-compliance-configuration-manual.md
               - name: Configuring devices for Update Compliance in Microsoft Endpoint Manager
                 href: update/update-compliance-configuration-mem.md
-            - name: Update Compliance monitoring (GA)
+            - name: Update Compliance monitoring
               items: 
               - name: Use Update Compliance
                 href: update/update-compliance-using.md

windows/deployment/update/update-compliance-v2-schema-ucclient.md

@@ -80,3 +80,7 @@ UCClient acts as an individual device's record. It contains data such as the cur
 | **WUServiceURLConfigured** |  [string](/azure/kusto/query/scalar-data-types/string) | `http://abcd-srv:8530` | CSP:UpdateServiceUrl. The following list shows the supported values: </br> </br> Not configured: The device checks for updates from Microsoft Update. </br> </br>     Set to a URL, such as `http://abcd-srv:8530`: The device checks for updates from the WSUS server at the specified URL.|
 | **WUUXDisabled** | [int](/azure/kusto/query/scalar-data-types/int) | `1` | CSP:SetDisableUXWUAccess.This policy allows the IT admin to remove access to scan Windows Update. When this policy is enabled, the user can't access the Windows Update scan, download, and install features. Default is 0. Supported values 0, 1. |
 
+## Next steps
+
+- [Update Compliance overview](update-compliance-v2-overview.md)
+- [Use Update Compliance](update-compliance-v2-use.md)

windows/deployment/update/update-compliance-v2-schema-ucclientreadinessstatus.md

@@ -0,0 +1,54 @@
+---
+title: Update Compliance Data Schema - UCClientReadinessStatus
+ms.reviewer: 
+manager: dougeby
+description: UCClientReadinessStatus schema
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.pagetype: deploy
+audience: itpro
+author: mestew
+ms.author: mstewart
+ms.collection: M365-analytics
+ms.topic: reference
+ms.date: 06/06/2022
+---
+
+# UCClientReadinessStatus
+<!--37063317, 30141258, 37063041-->
+***(Applies to: Windows 10)***
+
+> [!Important]
+> This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available.
+
+UCClientReadinessStatus is an individual device's record about its readiness for updating to Windows 11. If the device isn't capable of running Windows 11, the record includes which Windows 11 [hardware requirements](../../whats-new/windows-11-requirements.md#hardware-requirements) the device doesn't meet.
+
+|Field |Type |Example |Description |
+|---|---|---|---|
+| **DeviceName** |  [string](/azure/kusto/query/scalar-data-types/string) | `JohnPC-Contoso` | Client-provided device name |
+| **GlobalDeviceId** |  [string](/azure/kusto/query/scalar-data-types/string) | `g:9832741921341` | The global device identifier. |
+| **SCCMClientId** |  [string](/azure/kusto/query/scalar-data-types/string) | `5AB72FAC-93AB-4954-9AB0-6557D0EFA245` | Configuration Manager Client ID, if available. |
+| **AzureADTenantId** |  [string](/azure/kusto/query/scalar-data-types/string) | `69ca04b0-703d-4b3a-9184-c4e3c15d6f5e` | Azure AD Tenant ID |
+| **AzureADDeviceId** |  [string](/azure/kusto/query/scalar-data-types/string) | `71db1a1a-f1a6-4a25-b88f-79c2f513dae0` | Azure AD Device ID |
+| **OSName** |  [string](/azure/kusto/query/scalar-data-types/string) | `Windows 10` | The operating system name. |
+| **OSVersion** | [string](/azure/kusto/query/scalar-data-types/string) | `1909` | The Win10 OS Version (such as 19H2, 20H1, 20H2) currently installed on the device. |
+| **OSBuild** |  [string](/azure/kusto/query/scalar-data-types/string) | `10.0.18363.836` | The full OS build installed on this device, such as Major.Minor.Build.Revision  |
+| **TargetOSName** | [string](/azure/kusto/query/scalar-data-types/string) | `Windows 11` | The name of the operating system being targeted to the device for this readiness record.|
+| **TargetOSVersion** |  [string](/azure/kusto/query/scalar-data-types/string)  | `21H2` | The operating system version being targeted to the device for this readiness record.|
+| **TargetOSBuild** |  [string](/azure/kusto/query/scalar-data-types/string) | `10.0.22000.1` | The full operating system build number that's being targeted to the device for this readiness record.|
+| **ReadinessStatus** |  [string](/azure/kusto/query/scalar-data-types/string) | `Not capable` | The readiness status of the device is either capable, not capable, or
+unknown. This status is determined by the Windows Update applicability.|
+| **ReadinessReason** | [string](/azure/kusto/query/scalar-data-types/string) | `CPU;TPM` | Lists which [hardware requirements](../../whats-new/windows-11-requirements.md#hardware-requirements) are blocking the device from being capable of installing Windows 11. Field is null if the device is capable. This status is determined by the Windows Update applicability. |
+| **ReadinessScanTime** | [datetime](/azure/kusto/query/scalar-data-types/datetime) | `2020-05-14 09:26:03.478039` | The date and time when readiness was assessed and the assessment was sent.|
+| **ReadinessExpiryTime**| [datetime](/azure/kusto/query/scalar-data-types/datetime) | `2020-05-14 09:26:03.478039` | The date and time when the  readiness assessment will expire.|
+| **SetupReadinessStatus**| [string](/azure/kusto/query/scalar-data-types/string) | `Not capable` | The readiness status of the device is either capable, not capable, or
+unknown. This status is determined by Windows setup.|
+| **SetupReadinessReason** | Lists which [hardware requirements](../../whats-new/windows-11-requirements.md#hardware-requirements) are blocking the device from being capable of installing Windows 11. Field is null if the device is capable. This status is determined by Windows setup. |
+| **SetupReadinessTime** | [datetime](/azure/kusto/query/scalar-data-types/datetime) | `2020-05-14 09:26:03.478039` | The date and time when readiness was assessed by setup and the assessment was sent.|
+| **SetupReadinessExpiryTime** |  [datetime](/azure/kusto/query/scalar-data-types/datetime) | `2020-05-14 09:26:03.478039` | The date and time when the setup readiness assessment will expire.|
+| **TimeGenerated** |  [datetime](/azure/kusto/query/scalar-data-types/datetime) | `2020-05-14 10:26:03.478039` | The date and time when Azure Monitor Logs ingested this record for your Log Analytics workspace.|
+
+## Next steps
+
+- [Update Compliance overview](update-compliance-v2-overview.md)
+- [Use Update Compliance](update-compliance-v2-use.md)

windows/deployment/update/update-compliance-v2-schema-ucclientupdatestatus.md

@@ -65,3 +65,7 @@ Update Event that combines the latest client-based data with the latest service-
 | **UpdateReleaseTime** |  [datetime](/azure/kusto/query/scalar-data-types/datetime)  | `2020-05-14 09:26:03.478039` | The release date of the update |
 | **UpdateSource** |  [string](/azure/kusto/query/scalar-data-types/string) | `UUP` | The source of the update - UUP, MUv6, Media |
 
+## Next steps
+
+- [Update Compliance overview](update-compliance-v2-overview.md)
+- [Use Update Compliance](update-compliance-v2-use.md)

windows/deployment/update/update-compliance-v2-schema-ucdevicealert.md

@@ -80,3 +80,7 @@ These alerts are activated as a result of an issue that is device-specific. It i
 | **WUServiceURLConfigured** | [string](/azure/kusto/query/scalar-data-types/string) | `http://abcd-srv:8530` | CSP:UpdateServiceUrl. The following list shows the supported values: </br> </br> Not configured. The device checks for updates from Microsoft Update. </br> </br> Set to a URL, such as `http://abcd-srv:8530`, the device checks for updates from the WSUS server at the specified URL.|
 | **WUUXDisabled** | [int](/azure/kusto/query/scalar-data-types/int) | `1` | CSP:SetDisableUXWUAccess.This policy allows the IT admin to remove access to scan Windows Update. When this policy is enabled, the user can't access the Windows Update scan, download, and install features. Default is 0. Supported values 0, 1. |
 
+## Next steps
+
+- [Update Compliance overview](update-compliance-v2-overview.md)
+- [Use Update Compliance](update-compliance-v2-use.md)

windows/deployment/update/update-compliance-v2-schema-ucserviceupdatestatus.md

@@ -45,3 +45,8 @@ Update Event that comes directly from the service-side. The event has only servi
 | **UpdateDisplayName** | [string](/azure/kusto/query/scalar-data-types/string) | `2022-04 Cumulative Update for Windows 10 Version 21H1 for x64-based Systems (KB5012599)` | Friendly update display name. For Windows OS updates, there's a naming convention. For D&F, it's DriverFileName |
 | **UpdateManufacturer** | [string](/azure/kusto/query/scalar-data-types/string) | `Microsoft` | Manufacturer of update. Microsoft for WU FU/QU, for D&F name of driver manufacturer such as NVIDIA |
 | **UpdateReleaseTime** | [datetime](/azure/kusto/query/scalar-data-types/datetime) | `2020-05-14 09:26:03.478039` | DateTime of update's release date. |
+
+## Next steps
+
+- [Update Compliance overview](update-compliance-v2-overview.md)
+- [Use Update Compliance](update-compliance-v2-use.md)

windows/deployment/update/update-compliance-v2-schema-ucupdatealert.md

@@ -56,3 +56,8 @@ Alert for both client and service updates. Contains information that needs atten
 | **UpdateCategory** | [string](/azure/kusto/query/scalar-data-types/string) | `WindowsFeatureUpdate` | The type of content this DeviceUpdateEvent is tracking. |
 | **UpdateClassification** | [string](/azure/kusto/query/scalar-data-types/string) | `Upgrade` | Whether this content is an upgrade (feature update), Security (quality update), NonSecurity (quality update) |
 | **URL** | [string](/azure/kusto/query/scalar-data-types/string) | `aka.ms/errordetail32152` | An optional URL to get more in-depth information related to this alert.  |
+
+## Next steps
+
+- [Update Compliance overview](update-compliance-v2-overview.md)
+- [Use Update Compliance](update-compliance-v2-use.md)

windows/deployment/update/update-compliance-v2-schema.md

@@ -32,11 +32,12 @@ The table below summarizes the different tables that are part of the Update Comp
 
 |Table |Category |Description |
 |--|--|--|
-| [**UCClient**](update-compliance-v2-schema-ucclient.md) | Device record | UCClient acts as an individual device's record. It contains data such as the currently installed build, the device's name, the OS Edition, and active hours (quantitative). |
+| [**UCClient**](update-compliance-v2-schema-ucclient.md) | Device record | UCClient acts as an individual device's record. It contains data such as the currently installed build, the device's name, the operating system edition, and active hours (quantitative). |
+|[**UCClientReadinessStatus**](update-compliance-v2-schema-ucclientreadinessstatus.md) | Device record | UCClientReadinessStatus is an individual device's record about its readiness for updating to Windows 11. If the device isn't capable of running Windows 11, the record includes which Windows 11 hardware requirements the device doesn't meet.|
 | [**UCClientUpdateStatus**](update-compliance-v2-schema-ucclientupdatestatus.md) |  Device record |  Update Event that combines the latest client-based data with the latest service-based data to create a complete picture for one device (client) and one update. |
-| [**UCServiceUpdateStatus**](update-compliance-v2-schema-ucserviceupdatestatus.md) | Service record  | Update Event that comes directly from the service-side. The event has only service-side information for one device (client), and one update, in one deployment. This event has certain fields removed from it in favor of being able to show data in near real-time.  |
+| [**UCServiceUpdateStatus**](update-compliance-v2-schema-ucserviceupdatestatus.md) | Service record  | Update Event that comes directly from the service-side. The event has only service-side information for one device (client), and one update, in one deployment. |
-| [**UCUpdateAlert**](update-compliance-v2-schema-ucupdatealert.md) | Service and device records  |  Alert for both client and service update. Contains information that needs attention, relative to one device (client), one update, and one deployment (if relevant). Certain fields may be blank depending on the UpdateAlert's AlertType field; for example, ServiceUpdateAlert will not necessarily contain client-side statuses.  |
+| [**UCUpdateAlert**](update-compliance-v2-schema-ucupdatealert.md) | Service and device records  |  Alert for both client and service update. Contains information that needs attention, relative to one device (client), one update, and one deployment, if relevant. Certain fields may be blank depending on the UpdateAlert's AlertType field. For example, ServiceUpdateAlert will not necessarily contain client-side statuses and may be blank.  |
-| [**UCDeviceAlert**](update-compliance-v2-schema-ucdevicealert.md)| Service and device record  |  These alerts are activated as a result of an issue that is device-specific. It isn't specific to the combination of a specific update and a specific device. Like UpdateAlerts, the AlertType indicates where the Alert comes from (ServiceDeviceAlert, ClientDeviceAlert). For example, an EndOfService alert is a ClientDeviceAlert, as a build no longer being serviced (EOS) is a client-wide state. Meanwhile, DeviceRegistrationIssues in WUfB DS will be a ServiceDeviceAlert, as it's a device-wide state in the service to not be correctly registered.  |
+| [**UCDeviceAlert**](update-compliance-v2-schema-ucdevicealert.md)| Service and device record  |  These alerts are activated as a result of an issue that is device-specific. It isn't specific to the combination of a specific update and a specific device. Like UpdateAlerts, the AlertType indicates where the Alert comes from such as a ServiceDeviceAlert or ClientDeviceAlert. For example, an EndOfService alert is a ClientDeviceAlert, since a build that's no longer being serviced is a client-wide state. Meanwhile, DeviceRegistrationIssues in WUfB DS will be a ServiceDeviceAlert, as it's a device-wide state in the service to not be correctly registered.  |
 
 ## Next steps
 

windows/deployment/update/update-compliance-v2-use.md

@@ -49,9 +49,12 @@ The data powering Update Compliance is refreshed every 24 hours, and refreshes w
 
 | Data Type | Data upload rate from device | Data Latency |
 |--|--|--|
-|UCClient | Once per day |4 hours |
+| UCClient | Once per day |4 hours |
-|UCClientUpdateStatus|Every update event (Download, install, etc.)|24-36 hours |
+| UCClientUpdateStatus|Every update event (Download, install, etc.)|24-36 hours |
-|UCServiceUpdateStatus| Every update event (Download, install, etc.)|24-36 hours |
+| UCServiceUpdateStatus| Every update event (Download, install, etc.)|24-36 hours |
+| UCUpdateAlert |
+| UCDeviceAlert |
+| UCCientReadinesssStatus |
 |WUDOAggregatedStatus|On update event, aggregated over time|24-36 hours |
 |WUDOStatus|Once per day|12 hours |