Skip to content

Commit 45375e8

Browse files
committed
fix MicrosoftDocs/memdocs#2765
1 parent d31a7fd commit 45375e8

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

memdocs/configmgr/comanage/how-to-prepare-Win10.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn how to prepare your Windows internet-based devices for co-man
55
author: mestew
66
ms.author: mstewart
77
manager: dougeby
8-
ms.date: 04/05/2022
8+
ms.date: 05/19/2022
99
ms.topic: how-to
1010
ms.prod: configuration-manager
1111
ms.technology: configmgr-comanage
@@ -26,7 +26,7 @@ For more information, see [How to enroll with Autopilot](autopilot-enrollment.md
2626
> [!NOTE]
2727
> As we talk with our customers that are using Microsoft Endpoint Manager to deploy, manage, and secure their client devices, we often get questions regarding co-managing devices and hybrid Azure Active Directory (Azure AD) joined devices. Many customers confuse these two topics. Co-management is a management option, while Azure AD is an identity option. For more information, see [Understanding hybrid Azure AD and co-management scenarios](https://techcommunity.microsoft.com/t5/microsoft-endpoint-manager-blog/understanding-hybrid-azure-ad-join-and-co-management/ba-p/2221201). This blog post aims to clarify hybrid Azure AD join and co-management, how they work together, but aren't the same thing.
2828
>
29-
> You can't deploy the Configuration Manager client while provisioning a new computer in Windows Autopilot user-driven mode for hybrid Azure AD join. This limitation is due to the identity change of the device during the Azure AD-join process. Deploy the Configuration Manager client after the Autopilot process.<!-- CMADO-10205503 --> For alternative options to install the client, see [Client installation methods in Configuration Manager](../core/clients/deploy/plan/client-installation-methods.md).
29+
> You can't deploy the Configuration Manager client while provisioning a new computer in Windows Autopilot user-driven mode for hybrid Azure AD join. This limitation is due to the identity change of the device during the hybrid Azure AD-join process. Deploy the Configuration Manager client after the Autopilot process.<!-- CMADO-10205503 --> For alternative options to install the client, see [Client installation methods in Configuration Manager](../core/clients/deploy/plan/client-installation-methods.md).
3030
3131
### Gather information from Configuration Manager
3232

0 commit comments

Comments
 (0)