Skip to content

Commit 1b695b1

Browse files
authored
Merge pull request #7567 from MicrosoftDocs/main
Publish 05/10/2022, 10:30 AM
2 parents f7da8b8 + e7ddfd3 commit 1b695b1

2 files changed

Lines changed: 5 additions & 2 deletions

File tree

memdocs/configmgr/comanage/tutorial-co-manage-clients.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -149,7 +149,7 @@ Automatic enrollment also lets users enroll their Windows 10 or later devices to
149149
> [!NOTE]
150150
> Some tenants may not have these options to configure.<!-- SCCMDocs#1230 -->
151151
>
152-
> **Microsoft Intune** is how you configure the MDM app for Azure AD. **Microsoft Intune Enrollment** is a specific Azure AD app that's created when you apply multi-factor authentication policies for iOS and Android enrollment. For more information, see [Require multi-factor authentication for Intune device enrollments](/intune/enrollment/multi-factor-authentication).
152+
> **Microsoft Intune** is how you configure the MDM app for Azure AD. **Microsoft Intune Enrollment** is a specific Azure AD app that's created when you apply multi-factor authentication policies for iOS and Android enrollment. For more information, see [Require multi-factor authentication for Intune device enrollments](../../intune/enrollment/multi-factor-authentication.md).
153153
154154
5. For MDM user scope, select **All**, and then **Save**.
155155

@@ -159,6 +159,9 @@ With hybrid Azure AD set-up and Configuration Manager client configurations in p
159159

160160
When you enable co-management, you'll assign a collection as a *Pilot group*. This is a group that contains a small number of clients to test your co-management configurations. We recommend you create a suitable collection before you start the procedure. Then you can select that collection without exiting the procedure to do so. You may need multiple collections since you can assign a different *Pilot group* for each workload.
161161

162+
> [!NOTE]
163+
> Since devices are enrolled in the Microsoft Intune service based on its Azure AD device token, and not a user token, only the default [Intune enrollment restriction](../../intune/enrollment/enrollment-restrictions-set.md) will apply to the enrollment.
164+
162165
### Enable co-management for versions 2111 and later
163166

164167
[!INCLUDE [Enable Co-management starting in version 2111](includes/enable-co-management-2111.md)]

windows-365/enterprise/in-development.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ In a future update, Windows 365 Enterprise Cloud PCs will support RDP Shortpath
6868

6969
### Provision Cloud PCs with Secure Boot<!--38012584-->
7070

71-
You'll be able to create Cloud PCs that use [Secure boot](/windows-hardware/design/device-experiences/oem-secure-boot) functionality.
71+
You'll be able to create Cloud PCs that use [Secure boot](/windows-hardware/design/device-experiences/oem-secure-boot) functionality. Europe and North American regions will receive this feature within the next few months.
7272

7373
<!-- ***********************************************-->
7474
## Monitor and troubleshoot

0 commit comments

Comments
 (0)