Role-Based Access Control (RBAC) in Azure - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Role-Based Access Control (RBAC)?

RBAC is a way to manage who can do what in a cloud environment by assigning roles to users or groups. Each role has specific permissions that control access to resources.

beginner

What are the three main components of RBAC in Azure?

The three main components are: 1) Security Principal (user, group, or service principal), 2) Role Definition (set of permissions), and 3) Scope (where the role applies, like subscription or resource group).

beginner

How does RBAC help improve security in Azure?

RBAC limits access by giving users only the permissions they need to do their job. This reduces the risk of accidental or malicious changes to resources.

intermediate

What is a 'scope' in Azure RBAC?

Scope defines where the permissions apply. It can be a management group, subscription, resource group, or a single resource. Permissions granted at a higher scope apply to all lower scopes.

beginner

Name two built-in roles in Azure RBAC and their purpose.

1) Owner - full access to all resources including managing access. 2) Reader - can view resources but cannot make changes.

Which component in Azure RBAC represents the user or group that gets permissions?

A Security Principal

B Role Definition

C Scope

D Resource Provider

The Security Principal is the user, group, or service that receives permissions.

What does the 'scope' in RBAC define?

A Where the role permissions apply

B The permissions assigned to a role

C The user who gets the role

D The type of resource

Scope defines the boundary where the role permissions apply, such as subscription or resource group.

Which built-in Azure RBAC role allows viewing resources but not changing them?

A Contributor

B Owner

C Reader

D User Access Administrator

The Reader role allows viewing resources without permission to modify them.

What is the main benefit of using RBAC in Azure?

A Unlimited access to all users

B Limits access to only what users need

C Simplifies billing

D Automatically creates resources

RBAC limits access by assigning only necessary permissions to users, improving security.

If you assign a role at the subscription scope, where does it apply?

A Only to management groups

B Only to that subscription

C Only to resource groups

D To all resources within that subscription

Assigning a role at the subscription scope applies permissions to all resources within that subscription.

Explain how RBAC works in Azure and why it is important for managing cloud resources.

Think about how you control who can do what in a team project.

Describe the difference between the Owner and Reader roles in Azure RBAC.

Compare a manager versus a viewer in a workplace.

Practice

1. What is the main purpose of Role-Based Access Control (RBAC) in Azure?

easy

A. To store data securely

B. To create virtual machines automatically

C. To monitor network traffic

D. To assign permissions to users based on their roles

Solution

1. Step 1: Understand RBAC concept

   RBAC is designed to control who can do what by assigning roles with specific permissions.

2. Step 2: Identify the main function

   Assigning permissions based on roles helps manage access securely and efficiently.

3. Final Answer:

   To assign permissions to users based on their roles -> Option D

4. Quick Check:

   RBAC controls access by roles = A [OK]

Hint: RBAC = roles control permissions [OK]

Common Mistakes:

• Confusing RBAC with resource creation
• Thinking RBAC monitors traffic
• Assuming RBAC stores data

2. Which of the following is the correct way to assign a role to a user in Azure CLI?

easy

A. az role create --user [e-mail] --role Contributor

B. az user assign role --email [e-mail] --role Contributor

C. az role assignment create --assignee [e-mail] --role Contributor --scope /subscriptions/12345

D. az assign role --user [e-mail] --role Contributor

Solution

1. Step 1: Recall Azure CLI syntax for role assignment

   The correct command uses 'az role assignment create' with --assignee, --role, and --scope parameters.

2. Step 2: Match the correct command

   az role assignment create --assignee [e-mail] --role Contributor --scope /subscriptions/12345 matches the correct syntax and parameters for assigning a role.

3. Final Answer:

   az role assignment create --assignee [e-mail] --role Contributor --scope /subscriptions/12345 -> Option C

4. Quick Check:

   Correct CLI syntax = D [OK]

Hint: Use 'az role assignment create' with assignee and scope [OK]

Common Mistakes:

• Using wrong command verbs like 'assign' or 'create' alone
• Missing the --scope parameter
• Incorrect parameter names

3. Given this Azure CLI command:

az role assignment create --assignee [e-mail] --role Reader --scope /subscriptions/12345/resourceGroups/myGroup

What permission level does the user get on the resource group?

medium

A. Read-only access to the resource group

B. Write access to all resources in the subscription

C. Full control over the subscription

D. No access because scope is incorrect

Solution

1. Step 1: Analyze the role and scope

   The role is 'Reader', which grants read-only permissions. The scope is a specific resource group, limiting access to that group.

2. Step 2: Determine permission level

   The user can only read resources inside 'myGroup' resource group, not modify or access other subscription parts.

3. Final Answer:

   Read-only access to the resource group -> Option A

4. Quick Check:

   Reader role + resource group scope = read-only access [OK]

Hint: Reader role means read-only at given scope [OK]

Common Mistakes:

• Assuming Reader grants write or full control
• Confusing subscription scope with resource group scope
• Thinking scope is invalid

4. You tried to assign the 'Owner' role to a user but got an error. Which of these is the most likely cause?

medium

A. You do not have permission to assign the Owner role

B. The user email is invalid

C. The role name 'Owner' does not exist

D. You forgot to specify the subscription ID

Solution

1. Step 1: Understand role assignment permissions

   Assigning the 'Owner' role requires you to have sufficient permissions, usually Owner or User Access Administrator.

2. Step 2: Identify common error causes

   If you lack permission, Azure blocks the assignment with an error. Other options are less likely because 'Owner' is a valid role and subscription ID is often optional if context is set.

3. Final Answer:

   You do not have permission to assign the Owner role -> Option A

4. Quick Check:

   Permission needed to assign Owner role = B [OK]

Hint: Only users with rights can assign Owner role [OK]

Common Mistakes:

• Assuming role name is wrong
• Ignoring permission requirements
• Forgetting subscription context

5. You want to give a service principal permission to manage only virtual machines in a resource group without affecting other resources. Which RBAC role and scope should you assign?

hard

A. Assign 'Contributor' role at the subscription scope

B. Assign 'Virtual Machine Contributor' role at the resource group scope

C. Assign 'Owner' role at the resource group scope

D. Assign 'Reader' role at the virtual machine resource scope

Solution

1. Step 1: Identify the least privilege role for VM management

   'Virtual Machine Contributor' allows managing VMs but not other resources.

2. Step 2: Choose the correct scope

   Assigning at the resource group scope limits permissions to that group only, not the whole subscription.

3. Step 3: Evaluate other options

   'Contributor' at subscription is too broad; 'Owner' is too powerful; 'Reader' only allows viewing, not managing.

4. Final Answer:

   Assign 'Virtual Machine Contributor' role at the resource group scope -> Option B

5. Quick Check:

   Least privilege VM management at resource group = A [OK]

Hint: Use specific role + resource group scope for least privilege [OK]

Common Mistakes:

• Using broad roles like Contributor or Owner unnecessarily
• Assigning at subscription scope when resource group is enough
• Choosing Reader role which lacks management permissions