From bb1e37c4f32246d3f5cfe2a8d99a4d6d80ff145b Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Tue, 31 May 2022 15:14:43 -0700
Subject: [PATCH] Update windows-autopatch-register-devices.md

fixed link
---
 .../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 39efb1d422..2a9c8e22e5 100644
--- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
+++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
@@ -33,7 +33,7 @@ Windows Autopatch also supports the following Azure AD nested group scenarios:
 
 - Azure AD groups synced up from:
 	- On-premises Active Directory groups (Windows server type).
-	- [Configuration Manager collections](https://docs.microsoft.com/mem/configmgr/core/clients/manage/collections/create-collections#bkmk_aadcollsync).
+	- [Configuration Manager collections](/mem/configmgr/core/clients/manage/collections/create-collections#bkmk_aadcollsync).
 
 > [!IMPORTANT]
 > The **Windows Autopatch Device Registration** Azure AD group only supports one level of Azure AD nested groups.