From 66826e4976d9de576aec1bef1e82dcb4554ad40a Mon Sep 17 00:00:00 2001 From: rlianmsft <112862018+rlianmsft@users.noreply.github.com> Date: Tue, 6 Sep 2022 11:14:27 +0100 Subject: [PATCH] Update windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- .../deploy/windows-autopatch-register-devices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 2dabad0015..ffd3cf4cbf 100644 --- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md +++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md @@ -30,7 +30,7 @@ Windows Autopatch can take over software update management control of devices th You must choose what devices to manage with Windows Autopatch by adding them to the **Windows Autopatch Device Registration** Azure AD assigned group. Devices can be added using the following methods: -- Direct Membership +- Direct membership - Nesting other Azure AD dynamic/assigned groups - Bulk operations – Import members