From 9a7f5b54e206ca0d5cf898d268c0657c8aa9e5ef Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Fri, 3 Feb 2023 08:42:56 -0800 Subject: [PATCH] Update windows-autopatch-register-devices.md --- .../deploy/windows-autopatch-register-devices.md | 3 --- 1 file changed, 3 deletions(-) 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 ca625dc2d8..a6540780aa 100644 --- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md +++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md @@ -39,9 +39,6 @@ Windows Autopatch automatically runs its discover devices function every hour to > [!NOTE] > Devices that are intended to be managed by the Windows Autopatch service **must** be added into the **Windows Autopatch Device Registration** Azure AD assigned group. Devices can only be added to this group if they have an Azure AD device ID. Windows Autopatch scans the Azure AD group hourly to discover newly added devices to be registered. You can also use the **Discover devices** button in either the **Ready** or **Not ready** tab to register devices on demand. -> [!IMPORTANT] -> Windows Autopatch supports only one level of group-nesting in the **Windows Autopatch Device Registration** Azure AD group. - #### Supported scenarios when nesting other Azure AD groups Windows Autopatch also supports the following Azure AD nested group scenarios: