Merge pull request #6640 from MicrosoftDocs/main

Publish 01/27/2022, 10:30 AM

Author: v-dihans

memdocs/configmgr/comanage/faq.yml

@@ -7,7 +7,7 @@ metadata:
   ms.author: aaroncz
   ms.reviewer: crosorio
   manager: dougeby
-  ms.date: 01/10/2021
+  ms.date: 01/26/2022
   ms.topic: reference
   ms.prod: configuration-manager
   ms.technology: configmgr-comanage
@@ -122,6 +122,9 @@ sections:
 
           For more information, see [How to prepare internet-based devices for co-management](how-to-prepare-win10.md).
 
+          > [!NOTE]
+          > 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).
+
       - question: |
           How do I manage updates for Windows and Microsoft 365 apps?
         answer: |

memdocs/intune/fundamentals/deployment-guide-enrollment-ios-ipados.md

@@ -117,9 +117,9 @@ This task list provides an overview. For more specific information, see [Apple B
   > 
   >   During the Setup Assistant, users must enter their organization Azure AD credentials (`[email protected]`). When they enter their credentials, the enrollment starts, and the Company Portal app installs. If you want, users can also enter their Apple ID to access Apple specific features, such as Apple Pay.
   > 
-  >   After the Setup Assistant completes, users can use the device. When the home screen shows, the enrollment is complete, and user affinity is established. The device isn't fully registered with Azure AD, and doesn't show in a user's device list in Azure AD.
+  >   After the Setup Assistant completes, users can use the device. When the home screen shows, the enrollment is complete, and user affinity is established. The device isn't fully registered with Azure AD, and shows as non-compliant in a user's device list in Azure AD. The device shows as compliant in the Microsoft Endpoint Manager admin center.
   > 
-  >   After the Company Portal app installs, which takes some time, users open the Company Portal app, and sign with their organization Azure AD account (`[email protected]`) again. During this second login, any conditional access policies are evaluated, and Azure AD registration is complete. Users can install and use organizational resources, including LOB apps.
+  >   After the Company Portal app installs, which takes some time, users open the Company Portal app, and sign with their organization Azure AD account (`[email protected]`) again. During this second login, any conditional access policies are evaluated, and Azure AD registration is complete. Users can install and use organizational resources, including LOB apps. The device shows as compliant in Azure AD.
   > - If you don't want to use the device before the Company Portal app installs, then use the **Company Portal** app option. The **Company Portal** app option locks the device until the Company Portal app installs. When the install completes, the Company Portal app opens automatically. Users sign in with their Azure AD organization account (`[email protected]`), and can use the device.
 
 - If you use the Company Portal app, then decide how the Company Portal app will be installed on the devices. Make this decision before you create the enrollment profile.
@@ -201,9 +201,9 @@ When you create an enrollment profile in the [Endpoint Manager admin center](htt
 
   2. Setup Assistant prompts the user for additional information. When the home screen appears, setup is complete. The device is fully enrolled, and user device affinity is established. Users can use their devices and see your apps and policies on their devices.
 
-      At this point, the device isn't fully registered with Azure AD.
+      At this point, the device isn't fully registered with Azure AD and shows as non-compliant in Azure AD. The device shows it is compliant in the Microsoft Endpoint Manager admin center.
 
-  3. If you **Install Company Portal app with VPP** (recommended), then the Company Portal app automatically installs. Users open the Company Portal app, and sign in with their work or school account (`[email protected]`) again. They complete Azure AD registration in the Company Portal app, which fully registers the device with Azure AD. Users then gain access to corporate resources protected by conditional access policies.
+  3. If you **Install Company Portal app with VPP** (recommended), then the Company Portal app automatically installs. Users open the Company Portal app, and sign in with their work or school account (`[email protected]`) again. They complete Azure AD registration in the Company Portal app, which fully registers the device with Azure AD. Users then gain access to corporate resources protected by conditional access policies and the device shows as being compliant in Azure AD.
 
   4. If you don't **Install Company Portal app with VPP**, and want to use the Company Portal app, then: