mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
add table info for v1+v2
This commit is contained in:
parent
9441356efc
commit
6e5bd94944
@ -35,7 +35,7 @@ Use the product feedback option to offer suggestions for new features and functi
|
||||
|
||||
1. In the upper right corner of the Azure portal, select the feedback icon.
|
||||
1. Select either the smile or the frown to rate your satisfaction with your experience.
|
||||
1. In the text box, describe what you did or didn't like. When providing feedback about a problem, be sure to include enough detail in your description so it can be properly identified by the product group.
|
||||
1. In the text box, describe what you did or didn't like. When providinlg feedback about a problem, be sure to include enough detail in your description so it can be properly identified by the product group.
|
||||
1. Choose if you'd like to allow Microsoft to email you about your feedback.
|
||||
1. Select **Submit feedback** when you've completed the feedback form.
|
||||
:::image type="content" source="media/33771278-update-compliance-feedback.png" alt-text="Screenshot of the Azure portal showing the product feedback option flyout." lightbox="media/33771278-update-compliance-feedback.png":::
|
||||
@ -102,7 +102,7 @@ The first step in troubleshooting Update Compliance is ensuring that devices are
|
||||
|
||||
### Devices have been correctly configured but aren't showing up in Update Compliance
|
||||
|
||||
It takes some time for data to appear in Update Compliance for the first time or if a `Commercial ID`, has recently changed for a device. To learn more about data latencies for Update Compliance, review [Update Compliance data latency](update-compliance-v2-use.md#update-compliance-data-latency).
|
||||
It takes some time for data to appear in Update Compliance for the first time or if you moved to a new Log Analytics workspace. To learn more about data latencies for Update Compliance, review [Update Compliance data latency](update-compliance-v2-use.md#update-compliance-data-latency).
|
||||
|
||||
### Devices are appearing, but without a device name
|
||||
|
||||
|
@ -44,6 +44,8 @@ Currently, the technical preview contains the following features:
|
||||
- UCUpdateAlert
|
||||
- Client data collection to populate the new Update Compliance tables
|
||||
|
||||
Currently, these new tables are available to all Updates Compliance users. They will be displayed along with the original Updates Compliance tables.
|
||||
|
||||
:::image type="content" source="media/update-compliance-v2-query-table.png" alt-text="Screenshot of using a custom Kusto (KQL) query on Update Compliance data in Log Analytics." lightbox="media/update-compliance-v2-query-table.png":::
|
||||
|
||||
> [!IMPORTANT]
|
||||
@ -70,6 +72,9 @@ Since the data from your clients is stored in a Log Analytics workspace, you can
|
||||
- [Power BI](/azure/azure-monitor/logs/log-powerbi)
|
||||
- Other tools for [querying the data](/azure/azure-monitor/logs/log-query-overview)
|
||||
|
||||
|
||||
##
|
||||
|
||||
## Next steps
|
||||
|
||||
- Review the [Update Compliance prerequisites](update-compliance-v2-prerequisites.md)
|
||||
|
Loading…
x
Reference in New Issue
Block a user