diff --git a/windows/deployment/update/update-status-admin-center.md b/windows/deployment/update/update-status-admin-center.md index 37616ac7ef..d8dfad23e1 100644 --- a/windows/deployment/update/update-status-admin-center.md +++ b/windows/deployment/update/update-status-admin-center.md @@ -44,7 +44,7 @@ Windows Update for Business reports is a Windows service hosted in Azure that us ## The Windows tab -The **Windows** tab in the **Software updates** page in the Microsoft admin center is populated by data from [Windows Update for Business reports](wufb-reports-overview.md). The tab contains a high-level overview of update compliance for Windows clients in your environment. The tab displays two charts **Windows update status** and **End of service**. The Windows Update for Business reports data that populates these charts refreshes every 24 hours. For more information, see [Windows Update for Business reports data latency](wufb-reports-use.md#update-compliance-data-latency). +The **Windows** tab in the **Software updates** page in the Microsoft admin center is populated by data from [Windows Update for Business reports](wufb-reports-overview.md). The tab contains a high-level overview of update compliance for Windows clients in your environment. The tab displays two charts **Windows update status** and **End of service**. The Windows Update for Business reports data that populates these charts refreshes every 24 hours. For more information, see [Windows Update for Business reports data latency](wufb-reports-use.md#data-latency). ### Windows update status chart diff --git a/windows/deployment/update/wufb-reports-help.md b/windows/deployment/update/wufb-reports-help.md index 7e7cd5a137..acdd268217 100644 --- a/windows/deployment/update/wufb-reports-help.md +++ b/windows/deployment/update/wufb-reports-help.md @@ -103,7 +103,7 @@ The first step in troubleshooting Windows Update for Business reports is ensurin ### Devices have been correctly configured but aren't showing up in Windows Update for Business reports -It takes some time for data to appear in Windows Update for Business reports for the first time or if you moved to a new Log Analytics workspace. To learn more about data latencies for Windows Update for Business reports, review [Windows Update for Business reports data latency](wufb-reports-use.md#update-compliance-data-latency). +It takes some time for data to appear in Windows Update for Business reports for the first time or if you moved to a new Log Analytics workspace. To learn more about data latencies for Windows Update for Business reports, review [Windows Update for Business reports data latency](wufb-reports-use.md#data-latency). ### Devices are appearing, but without a device name diff --git a/windows/deployment/update/wufb-reports-use.md b/windows/deployment/update/wufb-reports-use.md index 94fef6d131..405b284562 100644 --- a/windows/deployment/update/wufb-reports-use.md +++ b/windows/deployment/update/wufb-reports-use.md @@ -36,7 +36,7 @@ UCUpdateAlert :::image type="content" source="media/wufb-reports-query-table.png" alt-text="Screenshot of using a custom Kusto (KQL) query on Windows Update for Business reports data in Log Analytics." lightbox="media/wufb-reports-query-table.png"::: -## Windows Update for Business reports data latency +## Data latency Windows Update for Business reports uses Windows client diagnostic data as its data source. After you add Windows Update for Business reports and appropriately configure your devices, it could take 48-72 hours before they first appear. diff --git a/windows/deployment/update/wufb-reports-workbook.md b/windows/deployment/update/wufb-reports-workbook.md index 3804392eed..380143a7ef 100644 --- a/windows/deployment/update/wufb-reports-workbook.md +++ b/windows/deployment/update/wufb-reports-workbook.md @@ -140,17 +140,22 @@ The **Device status** group for feature updates contains the following items: - **Device compliance status**: Table containing a list of devices getting a feature update and installation information including active alerts for the devices. - This table is limited to the first 250 rows. Select `...` to export the full list, or display the query in [Log Analytics](/azure/azure-monitor/logs/log-analytics-tutorial). -### Delivery Optimization (Preview) +## Delivery Optimization (preview tab) -The **Delivery Optimization** tab provides a summarized view of bandwidth efficiencies. With this new, revised report Microsoft Connected Cache has been included. +The **Delivery Optimization** tab provides a summarized view of bandwidth efficiencies. This new revised report also includes Microsoft Connected Cache (MCC) information. -At the top of the report, tiles demonstrate the total bandwidth savings percentage (from LAN or Group peers and Microsoft Connected Cache out of the total consumed bandwidth), device counts, percentages between peer-to-peer and Microsoft Connected Cache (MCC) of bytes delivered, and the breakdown of total download GBs. +At the top of the report, tiles display the following information: -The report is divided into easily navigable tabs: +- Total bandwidth savings percentage +- The percentage of the saved bandwidth broken down by peer-to-peer and MCC +- Device counts showing percentages of bytes delivered between peer-to-peer and MCC +- The breakdown of total downloaded GBs. -* **Device Configuration**: A chart differentiating the number of devices with and without peer-to-peer. And, a table of Download Mode configuration breakdown between numbers of devices. When selected, the devices within that group can be viewed, filtered in a separate table. -* **Content Distribution**: Includes charts showing percentage volumes and GB volumes by source by content types. All content types are linked to a table for deeper filtering by 'ContentType', 'AzureADTenantId', and 'GroupID'. -* **Efficiency By Group**: This view provides filters commonly used ways of grouping devices. The provied filters include: GroupID, City, Country, and ISP. +The Delivery Optimization tab is further divided into the following groups: + +- **Device Configuration**: A chart differentiating the number of devices with and without peer-to-peer. And, a table of Download Mode configuration breakdown between numbers of devices. When selected, the devices within that group can be viewed, filtered in a separate table. +- **Content Distribution**: Includes charts showing percentage volumes and GB volumes by source by content types. All content types are linked to a table for deeper filtering by **ContentType**, **AzureADTenantId**, and **GroupID**. +- **Efficiency By Group**: This view provides filters commonly used ways of grouping devices. The provided filters include: **GroupID**, **City**, **Country**, and **ISP**. ## Customize the workbook