diff --git a/windows/manage/images/uc-01.png b/windows/manage/images/uc-01.png new file mode 100644 index 0000000000..7f4df9f6d7 Binary files /dev/null and b/windows/manage/images/uc-01.png differ diff --git a/windows/manage/update-compliance-architecture.md b/windows/manage/update-compliance-architecture.md index 40464fab06..62bdff9658 100644 --- a/windows/manage/update-compliance-architecture.md +++ b/windows/manage/update-compliance-architecture.md @@ -10,17 +10,13 @@ author: greg-lindsay # Update Compliance Architecture -The following diagram summarizes the general flow of data between your devices and Update Compliance. +The following diagram summarizes the general flow of data between your devices and Update Compliance after enabling Windows telemetry on your Windows 10 devices and ensuring that they are assigned your Commercial ID. -After enabling Windows telemetry on your Windows 10 devices and ensuring that they are assigned your Commercial ID. +**(1)** user computers send computer, application and driver telemetry data to a secure Microsoft data center through the Microsoft Data Management Service.
+**(2)** After you configure Update Compliance, telemetry data is analyzed by the Update Compliance Service.
+**(3)** and pushed to your OMS workspace.
+**(4)** You can then use the Update Compliance solution.
+**(5)** to view Update compliance, track update deployment progress and troubleshoot matters that need your attention.
-(1) user computers send computer, application and driver telemetry data to a secure Microsoft data center through the Microsoft Data Management Service. - -(2) After you configure Update Compliance, telemetry data is analyzed by the Update Compliance Service. - -(3) and pushed to your OMS workspace. - -(4) You can then use the Update Compliance solution. - -(5) to view Update compliance, track update deployment progress and troubleshoot matters that need your attention. +![Update Compliance architecture](images/uc-01.png)