From 78fb73a1bd363d28f44631953053b7a03a1683c6 Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Tue, 25 Oct 2022 09:55:04 -0700 Subject: [PATCH] Fixing 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 5c32c2f651..890e6533c4 100644 --- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md +++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md @@ -202,7 +202,7 @@ For ease of deployment, we recommend nesting a dynamic device group in your Auto Support is available either through Windows 365, or the Windows Autopatch Service Engineering team for device registration-related incidents. - For Windows 365 support, see [Get support](/mem/get-support). -- For Azure Virtual Desktop support, see [Get support](/support/create-ticket/). +- For Azure Virtual Desktop support, see [Get support](https://azure.microsoft.com/support/create-ticket/). - For Windows Autopatch support, see [Submit a support request](/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request). ## Device management lifecycle scenarios