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

title, ms.reviewer, manager, description, ms.prod, author, ms.author, ms.collection, ms.topic, ms.date

title	ms.reviewer	manager	description	ms.prod	author	ms.author	ms.collection	ms.topic	ms.date
Update Compliance (preview) data schema		dougeby	An overview of Update Compliance (preview) data schema	w10	mestew	mstewart	M365-analytics	reference	06/06/2022

Update Compliance version 2 schema

(Applies to: Windows 11 & Windows 10)

Important

• As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the CommercialID is no longer required. For more information, see Configure Update Compliance settings through the Microsoft 365 admin center.
• 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.

When the visualizations provided in the default experience don't fulfill your reporting needs, or if you need to troubleshoot issues with devices, it's valuable to understand the schema for Update Compliance and have a high-level understanding of the capabilities of Azure Monitor log queries to power additional dashboards, integration with external data analysis tools, automated alerting, and more.

Schema

The table below summarizes the different tables that are part of the Update Compliance solution. To learn how to navigate Azure Monitor Logs to find this data, see Get started with log queries in Azure Monitor.

Note

Data is collected daily. The TimeGenerated field shows the time data was collected. It's added by Log Analytics when data is collected. Device data from the past 28 days is collected, even if no new data has been generated since the last time. LastScan is a clearer indicator of data freshness (that is, the last time the values were updated), while TimeGenerated indicates the freshness of data within Log Analytics.

Table	Category	Description
UCClient	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	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	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.
UCDeviceAlert	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.
UCServiceUpdateStatus	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	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 won't necessarily contain client-side statuses and may be blank.