Skip to content

Commit c03a863

Browse files
author
Angela Fleischmann
authored
Merge pull request #6623 from tktracker/patch-2
Update assign-role.md
2 parents 2464d2c + 394ab39 commit c03a863

1 file changed

Lines changed: 10 additions & 5 deletions

File tree

memdocs/intune/fundamentals/assign-role.md

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -40,15 +40,20 @@ To create, edit, or assign roles, your account must have one of the following pe
4040

4141
2. On the **Endpoint Manager roles - All roles** blade, choose the built-in role you want to assign > **Assignments** > **+ Assign**.
4242

43-
5. On the **Basics** page, enter an **Assignment name** and optional **Assignment description**, and then choose **Next**.
43+
3. On the **Basics** page, enter an **Assignment name** and optional **Assignment description**, and then choose **Next**.
4444

45-
6. On the **Admin Groups** page, select the group that contains the user you want to give the permissions to. Choose **Next**
45+
4. On the **Admin Groups** page, select the group that contains the user you want to give the permissions to. Choose **Next**.
4646

47-
7. On the **Scope (Groups)** page, choose a group containing the users/devices that the member above will be allowed to manage. You also have the option to choose all users and/or all devices. Choose **Next**.
47+
5. On the **Scope (Groups)** page, choose a group containing the users/devices that the member above will be allowed to manage. You also have the option to choose all users and/or all devices. Choose **Next**.
48+
49+
> [!NOTE]
50+
> The **All users** and **All devices** are [Intune virtual groups](groups-add.md) and not Azure Active Directory (Azure AD) security groups. As a result, for **Scope (Groups)** assignment purposes you cannot use them as parents of Azure AD security groups. If you need both **All users** and **All devices** and specific Azure AD security groups for **Scope (Groups)** assignments, you must add them separately with separate assignments. Otherwise, even if the **Scope (Groups)** assignment for a role is set to **All Users** the admin in this role won't have access to specific Azure AD user groups.
51+
>
52+
> For Azure AD security groups, nesting is supported.
4853
49-
8. On the **Scope (Tags)** page, choose tags where this role assignment will be applied. Choose **Next**.
54+
7. On the **Scope (Tags)** page, choose tags where this role assignment will be applied. Choose **Next**.
5055

51-
9. On the **Review + Create** page, when you're done, choose **Create**. The new assignment is displayed in the list of assignments.
56+
8. On the **Review + Create** page, when you're done, choose **Create**. The new assignment is displayed in the list of assignments.
5257

5358
## Next steps
5459
- [Learn more about role-based access control in Intune](role-based-access-control.md)

0 commit comments

Comments
 (0)