From c217f464703d2e39ccd27c83b022c4ea9f232940 Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Wed, 2 Apr 2025 08:56:26 -0700 Subject: [PATCH] Added 48hour note about registration time --- .../deploy/windows-autopatch-register-devices.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md index ac9de45be2..aaf372c8b1 100644 --- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md +++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md @@ -17,6 +17,9 @@ ms.collection: # Register devices with Autopatch groups +> [!IMPORTANT] +> Device registration might take up to 48 hours to reflect in the system. During this period, devices undergo the necessary onboarding processes before appearing as registered. + An Autopatch group is a logical container or unit that groups several [Microsoft Entra groups](/entra/fundamentals/groups-view-azure-portal), and software update policies. For more information, see [Windows Autopatch groups](../deploy/windows-autopatch-groups-overview.md). When you [create an Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md#create-an-autopatch-group) or [edit an Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md#edit-an-autopatch-group), the device-based Microsoft Entra groups you use are scanned on an ongoing basis to see if new devices need to be added to the Autopatch group.