Additional changes.

This commit is contained in:
tiaraquan
2022-07-07 14:24:31 -07:00
parent 04ee527e0f
commit 3e7d5315c0
2 changed files with 3 additions and 3 deletions

View File

@ -58,10 +58,10 @@
href: operate/windows-autopatch-teams.md
- name: Deregister a device
href: operate/windows-autopatch-deregister-devices.md
- name: Un-enroll your tenant
href: operate/windows-autopatch-unenroll-tenant.md
- name: Submit a support request
href: operate/windows-autopatch-support-request.md
- name: Un-enroll your tenant
href: operate/windows-autopatch-unenroll-tenant.md
- name: Reference
href:
items:

View File

@ -125,7 +125,7 @@ Registering your devices in Windows Autopatch does the following:
Once devices or Azure AD groups containing devices are added to the **Windows Autopatch Device Registration** group, Windows Autopatch discovers these devices and runs software-based prerequisite checks to try to register them with its service.
> [!IMPORTANT]
> It might take up to an hour for a device to change its status from **Ready for User** to **Active** in the Ready tab during the public preview.
> It might take up to an hour for a device to change its status from **Ready for User** to **Active** in the Ready tab.
## Device management lifecycle scenarios