Study guide
3.3 Authorization for Azure Resources
Exam AZ-305: Designing Microsoft Azure Infrastructure Solutions Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Orientation
1.1 AZ-305 Current Exam Facts & Format 1.2 Candidate Profile, Prerequisites & the AZ-104 Requirement 1.3 Skills Outline, Domain Weights & How to Use This Guide
2 Chapter 2: Logging, Monitoring & Diagnostics Design
2.1 Logging Solution Design 2.2 Log Routing Design 2.3 Azure Monitor Metrics & Alerting Design 2.4 Application Insights & Diagnostic Monitoring Design
3 Chapter 3: Authentication & Authorization Design
3.1 Authentication Solution Design 3.2 Identity Management Design 3.3 Authorization for Azure Resources 3.4 Authorization for On-Premises Resources 3.5 Secrets, Certificates & Key Management Design
4 Chapter 4: Governance, Compliance & Identity Governance Design
4.1 Management Group & Subscription Hierarchy Design 4.2 Resource Group Organization & Tagging Strategy Design 4.3 Compliance Management Design 4.4 Identity Governance Design
5 Chapter 5: Relational Data Storage Design
5.1 Relational Data Storage Selection 5.2 Database Service & Compute Tier Design 5.3 Database Scalability Design 5.4 Relational Data Protection Design
6 Chapter 6: Semi-Structured & Unstructured Data Storage Design
6.1 Semi-Structured Data Storage Design 6.2 Unstructured Data Storage Design 6.3 Storage Tier & Cost-Performance Trade-off Design 6.4 Unstructured Data Protection & Durability Design
7 Chapter 7: Data Integration & Analytics Design
7.1 Data Integration Pipeline Design 7.2 Event-Based & Real-Time Data Integration Design 7.3 Data Analytics Platform Design
8 Chapter 8: Backup & Disaster Recovery Design
8.1 Recovery Objectives Design: Calculating and Meeting RTO/RPO 8.2 Azure Site Recovery Architecture for Hybrid Workloads 8.3 Compute Backup & Recovery Design 8.4 Database Backup & Recovery Design 8.5 Unstructured Data Backup & Recovery Design
9 Chapter 9: High Availability Design
9.1 Compute High Availability: Availability Sets & Availability Zones 9.2 Compute High Availability: Load Balancing & VM Scale Set Design 9.3 Relational Data High Availability Design 9.4 Semi-Structured & Unstructured Data High Availability Design
10 Chapter 10: Compute Solution Design
10.1 Compute Requirements Analysis & Virtual Machine-Based Solution Design 10.2 Container-Based Solution Design (AKS, Container Apps, Azure Container Instances) 10.3 Serverless-Based Solution Design (Azure Functions, Logic Apps) 10.4 Batch Processing Solution Design (Azure Batch, HPC Workloads)
11 Chapter 11: Application Architecture Design
11.1 Messaging Architecture Design (Service Bus, Queue Storage) 11.2 Event-Driven Architecture Design (Event Grid, Event Hub) 11.3 API Integration & Application Caching Design (API Management, Azure Cache for Redis, CDN) 11.4 Application Configuration Management & Automated Deployment Design (App Configuration, DevOps Pipelines, Deployment Slots)
12 Chapter 12: Migration Design
12.1 Migration Assessment: Cloud Adoption Framework & On-Premises Evaluation 12.2 IaaS & PaaS Workload Migration Design 12.3 Database Migration Design (Data Migration Service, Database Migration Assistant) 12.4 Unstructured Data Migration Design (AzCopy, Data Box, Storage Migration Service)
13 Chapter 13: Network Solution Design
13.1 Internet Connectivity Design 13.2 Hybrid Connectivity Design 13.3 Network Security Optimization Design 13.4 Network Performance Optimization & Load-Balancing/Routing Design
14 Chapter 14: Final Review, Exam Strategy & Career Path
14.1 Cross-Domain Scenario Practice: Combining Identity, Data, Continuity & Infrastructure Decisions 14.2 Common AZ-305 Decision Traps 14.3 Final Study Plan & Practice Assessment Strategy 14.4 After AZ-305: Retake Policy, Renewal & Career Path
3.3 Authorization for Azure Resources
Key Takeaways Explain This Topic AI
Azure RBAC access exists only where security principal + role definition + scope are combined in a role assignment.
Scope inherits downward through management group -> subscription -> resource group -> resource; assign at the lowest scope that satisfies the requirement.
Owner can manage access for others; Contributor can manage resources but not access; Reader is view-only; User Access Administrator manages access without managing resources.
Custom roles use Actions/NotActions for management-plane permissions and DataActions/NotDataActions for data-plane permissions, scoped by AssignableScopes.
Deny assignments block access and are system-generated (e.g., by Azure Blueprints or Managed Applications) — architects do not author them directly.
Last updated: July 2026
Why Azure RBAC Design Matters
Every Azure resource — from a management group down to a single storage blob container — is protected by the same authorization system: Azure role-based access control (Azure RBAC) . Because RBAC is universal, AZ-305 tests it more heavily than almost any other single mechanism in the identity domain, and it appears embedded inside data storage, networking, and business-continuity scenarios as well as standalone governance questions. An architect who cannot correctly reason about scope inheritance or the difference between a built-in and a custom role will get scenario questions wrong even when the "headline" topic is something else, like Key Vault or Cosmos DB.
Core RBAC Vocabulary
Security principal — the identity being granted access: a user, group, service principal (app identity), or managed identity.
Role definition — a collection of permissions (what can be done): a list of allowed and denied actions.
Scope — where the permissions apply: management group, subscription, resource group, or a specific resource.
Role assignment — the binding of a security principal + role definition + scope. Access exists only where all three are attached together.
Built-In Roles You Must Know
- Role Grants Typical scenario
- Owner Full access, including managing role assignments Full control over a subscription for a platform team
Contributor Full access to manage resources, but cannot grant or change access for others App teams that need to create/modify resources but not manage RBAC
Reader View-only access to all resources Auditors, monitoring dashboards
User Access Administrator Manage user access to resources, without managing the resources themselves Delegate identity administration without granting resource-modify rights
Scope Hierarchy and Inheritance
Azure RBAC scope forms a hierarchy: management group → subscription → resource group → resource . A role assignment made at a higher scope is inherited by everything beneath it. Assigning Reader at the management group level, for example, grants read access to every subscription, resource group, and resource nested under that management group — a design choice that saves dozens of individual assignments but also means a mistake at a high scope has a wide blast radius. AZ-305 scenarios frequently test whether you assign at the lowest scope that satisfies the requirement (least privilege) rather than defaulting to subscription-wide grants for convenience.
Custom Roles
When no built-in role matches a requirement precisely, Azure RBAC supports custom roles , defined with this structure: {
- "Name": "VM Operator (No Delete)",
- "Actions": [
- "Microsoft.Compute/virtualMachines/start/action",
- "Microsoft.Compute/virtualMachines/restart/action",
- "Microsoft.Compute/virtualMachines/read"
- ],
- "NotActions": [],
- "DataActions": [],
- "NotDataActions": [],
- "AssignableScopes": [
- "/subscriptions/{subscription-id}"
- ]
- }
Actions — management-plane operations the role allows (e.g., start/restart a VM).
NotActions — carve-outs subtracted from Actions (useful for taking a broad built-in-like role and removing one sensitive permission).
DataActions / NotDataActions — data-plane operations, such as reading blobs inside a storage account or reading secrets inside a Key Vault, which are governed separately from management-plane actions.
AssignableScopes — which management groups, subscriptions, or resource groups the custom role is allowed to be assigned within.
A common exam scenario: "Operations staff should be able to restart virtual machines to resolve incidents but must never be able to delete them." A built-in role either grants too much (Contributor can delete) or too little (Reader cannot restart) — the correct recommendation is a custom role scoped to start/action and restart/action only.
Deny Assignments
Deny assignments work like role assignments but block actions instead of granting them, and — unlike custom roles — they cannot be authored directly by most administrators. Azure creates deny assignments automatically in specific system scenarios, such as protecting resources deployed through Azure Blueprints or Azure Managed Applications, so that even a subscription Owner cannot accidentally modify a protected resource. Recognize deny assignments as a system-generated protection mechanism, not a tool you design directly.
Exam Scenario
A design requires that a finance team's read-only reporting dashboard service principal can read cost and usage data across the entire tenant, while a separate DevOps service principal can only modify resources inside a single resource group used for a specific application. The correct design assigns Reader to the finance service principal at the management group scope (broad, read-only, minimal risk) and Contributor to the DevOps service principal at the resource group scope (narrow, write access, contained blast radius) — two different scopes chosen deliberately to match each principal's actual need, not a single subscription-wide assignment for both.
Common Traps
Confusing Azure RBAC (who can do what to a resource) with Azure Policy (what configurations are allowed to exist) — Policy enforcement is covered in Chapter 4; RBAC is strictly about access, not compliance rules.
Assigning Owner when Contributor plus a narrower access-management role would satisfy least privilege.
Forgetting that DataActions are separate from Actions — a role with full management-plane Actions on a storage account still cannot read blob data unless DataActions explicitly grant it (or Azure RBAC is enabled as the storage account's data-plane authorization mode).
Assuming a role assignment at a resource automatically limits inherited higher-scope assignments — inheritance flows down only; it does not get revoked by a narrower assignment below it (you would need a deny assignment or narrower custom role instead).