Skip to content

Commit 60fe40d

Browse files
authored
Merge pull request #18949 from Brenduns/content-maintenance
Intune - CP > Update evaluation article for custom roles
2 parents 7448631 + 279a5cd commit 60fe40d

File tree

4 files changed

+51
-28
lines changed

4 files changed

+51
-28
lines changed
-41.2 KB
Loading
23.8 KB
Loading
-2.01 KB
Loading

intune/intune-service/fundamentals/quickstart-create-custom-role.md

Lines changed: 51 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -2,73 +2,96 @@
22
title: Create and assign a custom role in Intune
33
description: Create and assign a custom role for a remote device manager.
44
services: microsoft-intune
5-
author: BrenDuns
5+
author: brenduns
66
ms.author: brenduns
77
ms.topic: how-to
8-
ms.date: 03/26/2019
8+
ms.date: 10/16/2025
99

1010
ms.collection:
1111
- M365-identity-device-management
1212
---
1313

1414
# Step 10: Create and assign a custom role
1515

16-
In this Intune topic, you'll create a custom role with specific permissions for a security operations department. Then you'll assign the role to a group of such operators. There are several default roles that you can use right away. But by creating custom roles like this one, you have precise access control to all parts of your mobile device management system.
16+
This article guides you through creating a custom role for Intune role-based access control (RBAC) that has specific permissions for a security operations department and assign the role to a group of such operators. When you assign Intune RBAC roles and follow the principles of least privilege access, your admins can perform tasks on only those users and devices that they should are empowered to manage.
17+
18+
Although Intune includes several built-in RBAC roles that you can use right away, we recommend using the least-privileged role that can complete the task an administrator is expected to manage. This approach minimizes security risks and operational errors by avoiding over-privileged accounts like Global Administrator or Intune Administrator for routine work.
1719

1820
[!INCLUDE [intune-evaluate](../includes/intune-evaluate.md)]
1921

2022
If you don't have an Intune subscription, [sign up for a free trial account](free-trial-sign-up.md).
2123

2224
## Prerequisites
2325

24-
- To complete this evaluation step, you must [create a group](quickstart-create-group.md).
26+
To complete this evaluation step, you must have a group with at least one user. Creating a group is covered in [Step 3 - Create a group](quickstart-create-group.md) of this evaluation guide.
2527

2628
## Sign in to Intune
2729

28-
Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431) as the built-in **[Intune Administrator](/entra/identity/role-based-access-control/permissions-reference#intune-administrator)** Microsoft Entra role.
30+
Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431) using an account that is assigned the Microsoft Entra role of **[Intune Administrator](/entra/identity/role-based-access-control/permissions-reference#intune-administrator)**.
2931

30-
If you created an Intune Trial subscription, the account that created the subscription is a Microsoft Entra [Global Administrator](/entra/identity/role-based-access-control/permissions-reference#global-administrator).
32+
However, if this is a new trial subscription, sign in with the account that created the subscription, which is a Microsoft Entra [Global Administrator](/entra/identity/role-based-access-control/permissions-reference#global-administrator).
3133

3234
> [!CAUTION]
3335
> [!INCLUDE [global-admin](../includes/global-admin.md)]
3436
3537
## Create a custom role
3638

37-
When you create a custom role, you can set permissions for a wide range of actions. For the security operations role, we'll set a few Read permissions so that the operator can review a device's configurations and policies.
39+
When you create a custom role, you can set permissions for a wide range of actions. For the security operations role, you'll enable *Read* permissions for a few categories so that the operator can review a device's configurations and policies.
40+
41+
1. In the Intune admin center, go to **Tenant administrator** > **Roles**, and select **Create**. From the drop-down box, select **Intune role**. The *Add Custom Role* workflow opens.
42+
![Adding a role in the Intune roles All roles pane.](./media/quickstart-create-custom-role/add-custom-role.png)
43+
44+
2. On the **Basics** page:
45+
- For Name, enter *Security operations*.
46+
- For **Description**, enter *This role lets a security operator monitor device configuration and compliance information.*
47+
Select **Next** to continue.
48+
49+
3. On the **Permissions** page, expand the *Corporate device identifiers* category and set *Read* to **Yes**:
50+
![Set Read value for Corporate device identifiers.](./media/quickstart-create-custom-role/corp-device-id-read.png)
51+
52+
After configuring Read for Corporate device identifiers, expand the following additional categories, and make the same configuration; setting *Read* to **Yes**.
53+
54+
- *Device compliance policies*
55+
- *Device configurations*
56+
- *Organization*.
57+
58+
After the four categories are configured, select **Next** to continue.
59+
60+
4. On **Scope tags**, select **Next**. You don't need to configure scope tags for this evaluation scenario.
3861

39-
1. In Intune, choose **Roles** > **All roles** > **Add**.
40-
![Adding a role in the Intune roles All roles pane.](./media/quickstart-create-custom-role/add-custom-role.png)
41-
2. Under **Add custom role**, in the **Name** box, enter *Security operations*.
42-
3. In the **Description** box, enter *This role lets a security operator monitor device configuration and compliance information.*
43-
4. Choose **Configure** > **Corporate device identifiers** > **Yes** next to **Read** > **OK**.
44-
![Set Read value for Corporate device identifiers.](./media/quickstart-create-custom-role/corp-device-id-read.png)
45-
5. Choose **Device compliance policies** > **Yes** next to **Read** > **OK**.
46-
6. Choose **Device configurations** > **Yes** next to **Read** > **OK**.
47-
7. Choose **Organization** > **Yes** next to **Read** > **OK**.
48-
8. Choose **OK** > **Create**.
62+
5. On **Review + Create**, select *Create*. Intune creates the custom role, which now appears on the **Intune roles | All roles** page of the admin center, with a **Type** of *Custom Intune role*.
4963

5064
## Assign the role to a group
5165

52-
Before your security operator can use the new permissions, you must assign the role to a group that contains the security user.
66+
1. Sign in to the Microsoft Intune admin center and go to **Tenant administration** > **Roles** > **All roles**.
67+
68+
2. On the **Intune roles - All roles** page, select the custom role you created, **Security operations** to open the roles *Overview*. Select **Assignments** and then select **Assign**.
69+
70+
![Open the roles assignment workflow.](./media/quickstart-create-custom-role/assignment-workflow.png)
71+
72+
3. On the **Basics** page, for Name enter *Sec ops*, and then select **Next** to continue.
73+
74+
4. On the **Admin Groups** page, select **Add groups** and then choose a group that contains the users you want to assign the roles permissions to. If you created the **Contoso Testers** group in [Step 3](quickstart-create-group.md) of this evaluation guide, select that group.
75+
76+
After adding a group, choose **Select**, and then **Next** to continue to the next page of the workflow.
77+
78+
5. On the **Scope Groups** page, select **Add groups** and then add the same group you added in the previous step. As before, choose **Select**, and then **Next** to continue to the next page of the workflow.
79+
80+
6. On **Scope tags**, select **Next**. You don't need to configure scope tags for this evaluation scenario.
81+
82+
7. On the **Review + Create** page, when you're done, select **Create**.
5383

54-
1. In Intune, choose **Roles** > **All roles** > **Security operations**.
55-
2. Under **Intune roles**, choose **Assignments** > **Assign**.
56-
3. In the **Assignment name** box, enter *Sec ops*.
57-
4. Choose **Member (Groups)** > **Add**.
58-
5. Choose the **Contoso Testers** group.
59-
6. Choose **Select** > **OK**.
60-
7. Choose **Scope (Groups)** > **Select groups to include** > **Contoso Testers**.
61-
8. Choose **Select** > **OK** > **OK**.
84+
The new assignment is displayed in the list of assignments.
6285

6386
Now everyone in the group is a member of the *Security operations* role and can review the following information about a device: corporate device identifiers, device compliance policies, device configurations, and organization information.
6487

6588
## Clean up resources
6689

67-
If you don't want to use the new custom role anymore, you can delete it. Choose **Roles** > **All roles** > choose the ellipses next to the role > **Delete**.
90+
If you don't want to use the new custom role anymore, you can delete it. In the admin center, got to **Tenant administration** > **Roles** > **All roles**, locate the role and select the ellipses (...) to the left of the roles description, and then select **Delete**.
6891

6992
## Next steps
7093

71-
In this quickstart, you created a custom security operations role and assigned it to a group. For more information about roles in Intune, see [Role-based administration control (RBAC) with Microsoft Intune](role-based-access-control.md)
94+
In this evaluation step, you created a custom security operations role and assigned it to a group. For more information about roles in Intune, see [Role-based administration control (RBAC) with Microsoft Intune](role-based-access-control.md)
7295

7396
To continue to evaluate Microsoft Intune, go to the next step:
7497

0 commit comments

Comments
 (0)