Skip to content

Commit 98673ab

Browse files
Added note to enrollment portion
(Verify I did the hyperlink correctly, should link to https://docs.microsoft.com/en-us/mem/intune/enrollment/enrollment-restrictions-set) Adding note to deflect future support cases based on users having the default enrollment restriction set to block all windows and the higher priority windows restrictions not being utilized because no user is associated with the request.
1 parent 9138fb9 commit 98673ab

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -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) 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)]

0 commit comments

Comments
 (0)