For a while now, Scope Tags have been an odd concept for me to understand. Partly because, i thought i understood it, and partly due to me not getting my hands dirty and bringing myself to understand how they work.

However, as with all things tech, there comes a time where you just have to get stuck in and learn by doing – the best way of learning.

So what did i have to accomplish? My scenario and requirements are below;

The entertainment department recently purchased 70 iPhones.

They wanted these iPhones to be managed by Intune.

Required custom device settings e.g Hide all apps possible, Move all others to a single folder except for the settings app Never Auto-Lock Bluetooth always Off

Required some restrictions on the device Safari disabled Camera Disabled Siri Disabled



Once the settings had been configured. They wanted to be provided with access to maintain and modify the device configuration profile for all future changes. This is where the scope tags come in to play. But first, i had to understand how RBAC worked on Azure and Intune.

Understanding RBAC

As per Microsoft documentation – You can use role-based access control and scope tags to make sure that the right admins have the right access and visibility to the right Intune objects.

Roles determine what access admins have to which objects.

Scope tags determine which objects admins can see.

Understanding Scope Tags

Scope Tags can be applied to different objects on Azure and Intune. The tag is essentially your unique identifier which you then use to link with scopes. Your objects can have multiple Scope Tags and a Scope can have multiple Scope Tags linked with it.

Things to keep in mind:

To be assigned an intune role, the user must have an intune license.

When an admin creates an object in Intune, all scope tags assigned to that admin will be automatically assigned to the new object.

Intune RBAC doesn’t apply to Azure Active Directory roles. So, the Intune Service Admins and Global Admins roles have full admin access to Intune no matter what scope tags they have.

How to use Scope Tags

Here is the scenario;

The entertainment team would like to be able to manage their own device configuration profile for their iPhones – and as such, we want to separate them from an administrative perspective.

Entertainment Team

We will create three groups for the Team.

Devices Group: All devices that they manage

Users

Admins Group: All admins who will manage the profile

How to create a Scope Tag

Navigate to portal.azure.com and open Intune. From here, go to Roles > Scope Tags and click on Create. Enter a name for your Scope Tag and assign the tag to a group of your target devices.

How to assign a role to a Scope Tag

Now that we have our scope tag, the next step is to assign it our desired role (permissions).

Navigate to portal.azure.com and open Intune. From here, go to roles, and click on “All roles”. Click on the role you want to assign, in this case i am going with “Policy and profile manager” Click on Assign

Enter a name for your assignment If you wish, enter a description Click on Members (Groups) Member group users are the administrators assigned to this role, enter the group you have created which contains all the administrators. Click on Scope (Groups) The scope groups entered here are the policies, applications or remote tasks that administrators in this role assignment can target. Click on Scope (Tags) Enter the Scope Tag, this is the tag that will apply to this role.

It is worth remembering that the administrators who you are applying these permissions to will require a “Microsoft Intune” license for RBAC to work.

I hope that this blog post can help fellow admins.

If you have any questions, feedback, constructive criticisms, or anything else. Please dont hesitate to comment below.

Thank you for reading.

Share this: Twitter

Facebook

