Role-Based Access Control (RBAC) in Azure - Step-by-Step Execution

Process Flow - Role-Based Access Control (RBAC)

User requests access

↓

Check user's assigned roles

↓

Match role permissions with requested action

Yes No↓

Allow access

↓

Log access decision

RBAC checks what roles a user has, then allows or denies actions based on those roles' permissions.

Execution Sample

Azure

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

Assigns the Reader role to a user for a specific subscription scope.

Process Table

Step	Action	Input	Check	Result
1	User requests to read resource	User: [e-mail], Action: read	Check roles assigned to user	Roles found: Reader
2	Check if Reader role allows read	Role: Reader, Action: read	Reader role includes read permission	Permission granted
3	Allow access	User: [e-mail], Action: read	Access allowed	User can read resource
4	Log access decision	User: [e-mail], Action: read	Log success	Access logged
5	User requests to write resource	User: [e-mail], Action: write	Check roles assigned to user	Roles found: Reader
6	Check if Reader role allows write	Role: Reader, Action: write	Reader role does not include write permission	Permission denied
7	Deny access	User: [e-mail], Action: write	Access denied	User cannot write resource
8	Log access decision	User: [e-mail], Action: write	Log failure	Access denied logged

💡 Access decisions made based on role permissions; no further checks needed.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 5	After Step 6	Final
User Roles	None	Reader	Reader	Reader	Reader	Reader
Requested Action	None	read	read	write	write	write
Permission Check Result	None	Pending	Granted	Pending	Denied	Denied
Access Decision	None	Pending	Allowed	Pending	Denied	Denied

Key Moments - 2 Insights

Why does the user get denied when trying to write even though they have the Reader role?

Because the Reader role only allows read permissions, not write. This is shown in execution_table rows 5 and 6 where the write action is checked against Reader role permissions and denied.

What happens if a user has multiple roles with conflicting permissions?

Azure RBAC grants the most permissive access from all assigned roles. So if any role allows the action, access is granted. This is implied in the role check step where all roles are evaluated.

Visual Quiz - 3 Questions

Look at the execution_table, what is the permission check result at step 2?

A Pending

B Denied

C Granted

D Not checked

💡 Hint

Check the 'Permission Check Result' column for step 2 in execution_table.

At which step does the user get denied access for writing?

A Step 4

B Step 7

C Step 6

D Step 8

💡 Hint

Look for the 'Access Decision' column where access is denied for write action.

If the user was assigned the Contributor role instead of Reader, how would step 6 change?

A Permission check would grant write

B Permission check would be pending

C Permission check would still deny write

D No permission check needed

💡 Hint

Contributor role includes write permissions, so permission check would grant write.

Concept Snapshot

Role-Based Access Control (RBAC) in Azure:
- Assign roles to users/groups at scopes (subscription, resource group, resource).
- Roles define allowed actions (read, write, delete).
- When user requests action, Azure checks assigned roles for permission.
- Access granted if any role allows the action.
- Use Azure CLI or portal to assign roles.

Full Transcript

Role-Based Access Control (RBAC) in Azure works by assigning roles to users or groups. Each role has permissions that allow certain actions like reading or writing resources. When a user tries to do something, Azure checks their roles to see if the action is allowed. If yes, access is granted; if not, access is denied. For example, a user with the Reader role can read resources but cannot write. This process ensures secure and organized access management in cloud environments.

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