Merge pull request #10739 from tiaraquan/ap-updates-040225

Added 48hour note about registration time
This commit is contained in:
Tiara Quan
2025-04-02 09:23:21 -07:00
committed by GitHub
2 changed files with 6 additions and 0 deletions

View File

@ -17,6 +17,9 @@ ms.collection:
# Autopatch group registration overview
> [!IMPORTANT]
> If you're new to Autopatch, it might take up to 48 hours for devices to appear as Registered in the [Autopatch groups membership report](../deploy/windows-autopatch-register-devices.md#autopatch-groups-membership-report). During this 48 hour period, devices undergo the necessary onboarding processes before appearing as registered.
When you assign a Microsoft Entra Group to an Autopatch policy or [create an Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md#create-an-autopatch-group), the device is registered with the Autopatch Service.
## Prerequisites for device registration

View File

@ -17,6 +17,9 @@ ms.collection:
# Register devices with Autopatch groups
> [!IMPORTANT]
> If you're new to Autopatch, it might take up to 48 hours for devices to appear as Registered in the [Autopatch groups membership report](../deploy/windows-autopatch-register-devices.md#autopatch-groups-membership-report). During this 48 hour 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.