From 92f1aebce4069196ae9035ac1d0e27f768c685c8 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Fri, 26 Mar 2021 15:14:13 -0700 Subject: [PATCH] Update update-compliance-get-started.md --- windows/deployment/update/update-compliance-get-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/update-compliance-get-started.md b/windows/deployment/update/update-compliance-get-started.md index f9e75ca43b..e686447597 100644 --- a/windows/deployment/update/update-compliance-get-started.md +++ b/windows/deployment/update/update-compliance-get-started.md @@ -21,7 +21,7 @@ This topic introduces the high-level steps required to enroll to the Update Comp 1. Ensure you can [meet the requirements](#update-compliance-prerequisites) to use Update Compliance. 2. [Add Update Compliance](#add-update-compliance-to-your-azure-subscription) to your Azure subscription. -3. [Configure devices](#enroll-devices-in-update-compliance) to send data to Update Compliance. +3. [Configure devices](#enroll-devices-in-update-compliance) to send data to Update Compliance. After adding the solution to Azure and configuring devices, there will be a waiting period of up to 72 hours before you can begin to see devices in the solution. Before or as devices appear, you can learn how to [Use Update Compliance](update-compliance-using.md) to monitor Windows Updates and Delivery Optimization.