Study guide

3.1 Azure RBAC, Custom Roles, and Governance

Microsoft Azure Security Technologies AZ-500

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Azure Security Architecture Foundation

1.1 Azure Security Engineer Role & Exam Logistics 1.2 Microsoft Cybersecurity Reference Architecture & Zero Trust Principles

2 Chapter 2: Secure Identity and Access - Authentication, MFA & PIM

2.1 Microsoft Entra ID Security, Users, and Groups 2.2 Authentication Methods, MFA, and Conditional Access Policy Design 2.3 Microsoft Entra Privileged Identity Management (PIM)

3 Chapter 3: Secure Identity and Access - RBAC & Workload Identity

3.1 Azure RBAC, Custom Roles, and Governance 3.2 Workload Identities and Managed Identities 3.3 External Identities and Cross-Tenant Collaboration

4 Chapter 4: Microsoft Entra Application Access & Consent Governance

4.1 Enterprise Applications, OAuth Permission Grants & Consent Governance 4.2 App Registrations, Permission Scopes & Service Principal Credentials

5 Chapter 5: Secure Azure Networking - Boundary & Perimeter Protection

5.1 Virtual Network Security & Micro-segmentation 5.2 Azure Firewall and Firewall Manager 5.3 Web Application Firewall (WAF) & Azure Front Door

6 Chapter 6: Secure Azure Networking - Private Access & Monitoring

6.1 Private Connectivity with Private Endpoints & Private Link 6.2 Azure Bastion & Remote Management Security 6.3 Network Perimeter Protection & Flow Monitoring

7 Chapter 7: Network Architecture, Routing & Hybrid Connectivity

7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes 7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub 7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance

8 Chapter 8: Public and Edge Access Protection

8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication 8.2 Azure Front Door, CDN Caching & TLS for App Service and API Management

9 Chapter 9: Compute, Container & Registry Security

9.1 Azure Virtual Machine Hardening & Host Security 9.2 Azure Key Vault Deep Dive & Secrets Lifecycle 9.3 Container & Azure Kubernetes Service (AKS) Security 9.4 Azure Container Instances, Container Apps & Registry Access Control

10 Chapter 10: Storage Security, Access Methods & Data Protection

10.1 Storage Account Security & Access Controls 10.2 Selecting and Configuring Access to Azure Files 10.3 Selecting and Configuring Access to Azure Blob Storage 10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup

11 Chapter 11: Data Platform & Database Security

11.1 Azure SQL Database Security & Always Encrypted 11.2 Database Auditing & Vulnerability Assessment 11.3 Data Discovery, Classification, & Microsoft Purview Integration

12 Chapter 12: Cloud Governance, Key Lifecycle & Asset Protection

12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation 12.2 Key Vault Backup, Recovery & Automated Key Rotation 12.3 Implementing Security Controls to Protect Backups 12.4 Security Controls for Asset Management: Locks, Tags, Resource Graph & Azure Arc

13 Chapter 13: Microsoft Defender for Cloud - Posture & Workload Protection

13.1 Microsoft Defender for Cloud & Secure Score 13.2 Defender Cloud Workload Protection (CWP) Plans 13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards 13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud

14 Chapter 14: External Attack Surface & Vulnerability Management

14.1 Microsoft Defender External Attack Surface Management (EASM) 14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs 14.3 Defender for Cloud DevOps Security: GitHub, Azure DevOps & GitLab

15 Chapter 15: Security Monitoring, Microsoft Sentinel & Automation

15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring 15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization 15.3 Microsoft Sentinel Workspace & KQL Threat Hunting 15.4 Sentinel Incident Management & SOAR Automation

3.1 Azure RBAC, Custom Roles, and Governance

Key Takeaways Explain This Topic AI

Azure RBAC manages permissions on the ARM control plane (resources), whereas Microsoft Entra ID roles govern directory-level objects and administrative functions.

Built-in Azure RBAC roles include Owner, Contributor, Reader, User Access Administrator, and Security Admin, each with distinct permission boundaries.

Custom roles are defined in JSON using Actions, NotActions, DataActions, NotDataActions, and AssignableScopes; NotActions subtracts operations but does NOT act as a Deny rule.

Azure RBAC follows top-down scope inheritance (Management Group -> Subscription -> Resource Group -> Resource), where total permissions are strictly additive across assignments.

Deny Assignments are system-managed rules applied by services like Azure Blueprints that override allow permissions, while Azure Policy enforces compliance via effects like Deny, AuditIfNotExists, and DeployIfNotExists.

Last updated: August 2026

3.1 Azure RBAC, Custom Roles, and Governance

Securing identity in Microsoft Azure requires a clear distinction between resource access management and directory identity management. Azure Role-Based Access Control (RBAC) is the core Authorization framework used to manage access to Azure infrastructure resources, while Microsoft Entra ID roles govern directory-level objects and administrative functions. Mastering Azure RBAC architecture, custom role creation, scope inheritance, deny assignments, and Azure Policy enforcement is critical for passing the AZ-500 exam and architecting zero-trust Azure environments.

1. Azure RBAC Architecture vs. Microsoft Entra ID Roles

Azure security administrators must understand the functional boundary between the Azure Resource Manager (ARM) control plane and the Microsoft Entra ID directory control plane .

  • Architecture Dimension Azure RBAC Roles Microsoft Entra ID Roles
  • Control Plane Azure Resource Manager (ARM) Control Plane Microsoft Entra Directory Control Plane

Target Entities Subscriptions, Resource Groups, VMs, Key Vaults, VNets, Storage Accounts Users, Groups, Enterprise Apps, Domains, Licenses, PIM Settings

Scope Hierarchy Management Group ⟶ \longrightarrow ⟶ Subscription ⟶ \longrightarrow ⟶ Resource Group ⟶ \longrightarrow ⟶ Resource Tenant-wide or Administrative Unit (AU)

Primary Use Case Managing deployment, configuration, and data plane access for Azure services Managing identity lifecycle, directory administration, and security configurations

Built-in Examples Owner, Contributor, Reader, User Access Administrator Global Administrator, User Administrator, Application Administrator, Security Admin

Important

A user assigned the Global Administrator role in Microsoft Entra ID does NOT automatically have permissions to manage Azure resources (such as reading storage accounts or managing Virtual Machines). To manage Azure resources, a Global Administrator must explicitly enable the "Access management for Azure resources" toggle in Entra ID properties, which temporarily elevates their account to the User Access Administrator role at the Root Management Group ( / ) scope.

2. Built-in Azure RBAC Roles

Azure provides over 100 built-in roles. The AZ-500 exam heavily tests the operational boundaries of the primary fundamental roles:

Owner ( /providers/Microsoft.Authorization/roleDefinitions/8e3af657-a8ff-443c-a75c-2fe8c4bcb635 ) :

Grants full access to manage all resources, including the ability to assign roles in Azure RBAC ( Microsoft.Authorization/* ).

Contributor ( /providers/Microsoft.Authorization/roleDefinitions/b24988ac-6180-42a0-ab88-20f7382dd24c ) :

Grants full access to manage all resources (create, edit, delete ARM resources), but cannot grant access to others ( NotActions: ["Microsoft.Authorization/*/Write", "Microsoft.Authorization/*/Delete"] ).

Reader ( /providers/Microsoft.Authorization/roleDefinitions/acdd72a7-3385-48ef-bd42-f606fba81ae7 ) :

Grants read-only access to view ARM resources and configurations. Cannot make changes or read data plane content unless explicitly allowed.

User Access Administrator ( /providers/Microsoft.Authorization/roleDefinitions/18d50206-a5e3-4b86-8234-45016c74990d ) :

Grants permissions to manage user access to Azure resources (assign and remove RBAC roles) without granting control over resource deployment or configuration.

Security Admin ( /providers/Microsoft.Authorization/roleDefinitions/fb355c54-9285-4728-b570-1463945138f6 ) :

Grants permissions to view security recommendations, security policies, alerts, and configure Microsoft Defender for Cloud, but cannot grant user permissions or delete resources.

3. Custom Role Creation Deep Dive

When built-in roles do not meet specific organizational least-privilege requirements, security engineers must construct custom Azure RBAC roles. Custom roles are defined using JSON structures containing five key properties: {

  • "Name": "Virtual Machine Operator and Security Auditor",
  • "IsCustom": true,
  • "Description": "Allows restarting VMs, inspecting network interfaces, and reading storage data.",
  • "Actions": [
  • "Microsoft.Compute/virtualMachines/read",
  • "Microsoft.Compute/virtualMachines/restart/action",
  • "Microsoft.Network/networkInterfaces/read",
  • "Microsoft.Insights/alertRules/*"
  • ],
  • "NotActions": [
  • "Microsoft.Compute/virtualMachines/delete"
  • ],
  • "DataActions": [
  • "Microsoft.Storage/storageAccounts/blobServices/containers/blobs/read"
  • ],
  • "NotDataActions": [],
  • "AssignableScopes": [
  • "/subscriptions/a1b2c3d4-e5f6-7a8b-9c0d-1e2f3a4b5c6d",
  • "/providers/Microsoft.Management/managementGroups/mg-core-infrastructure"
  • ]
  • }

Understanding Role JSON Elements:

Actions : Operations allowed on ARM control plane resources. Supports wildcards ( * ).

NotActions : Operation exclusions subtracted from the Actions set.

Warning

NotActions is NOT a Deny rule! It is simply a subtraction helper. If a user is assigned a role with NotActions: ["Microsoft.Compute/virtualMachines/delete"] , but is also assigned the Contributor role elsewhere, the user CAN STILL DELETE the Virtual Machine because permissions in Azure RBAC are strictly additive across assignments.

DataActions : Operations allowed on data plane resources (e.g., reading messages from Azure Storage Queues, blobs, or Key Vault secret values).

NotDataActions : Exclusions subtracted from DataActions .

AssignableScopes : Specifies the Management Groups, Subscriptions, or Resource Groups where the custom role can be assigned.

Custom roles can be assigned at Management Group scope (must be enabled for Management Groups).

You cannot set an individual Resource scope (e.g., specific VM path) directly as an AssignableScope in the JSON definition.

4. Scope Hierarchy and Permission Inheritance

Azure RBAC permissions follow a strict structural hierarchy: Management Group ⟶ Subscription ⟶ Resource Group ⟶ Resource \text{Management Group} \longrightarrow \text{Subscription} \longrightarrow \text{Resource Group} \longrightarrow \text{Resource} Management Group ⟶ Subscription ⟶ Resource Group ⟶ Resource

Core Inheritance Rules:

Top-Down Inheritance : Role assignments created at higher scopes (e.g., Management Group) are automatically inherited by all child containers and resources (Subscriptions ⟶ \longrightarrow ⟶ Resource Groups ⟶ \longrightarrow ⟶ Resources).

Additive Permission Model : Total effective permission is the union of all explicit and inherited role assignments. You cannot revoke inherited permissions at a child scope via standard RBAC assignments.

Resource Limits : A single Azure subscription supports up to 4,000 role assignments .

5. Deny Assignments

Unlike normal RBAC assignments (which are strictly additive allow rules), Deny Assignments explicitly block specific actions from being performed by security principals, even if an allow role assignment grants access.

System-Managed Only : Deny assignments cannot be created directly by tenant administrators via Portal or CLI.

Created by Services : Applied automatically by Azure Blueprints or Azure Managed Applications to prevent users (including Subscription Owners) from altering managed infrastructure components.

Deny Assignment Exclusions : Can exclude specific deployment service principals while blocking user accounts from modifying protected resources.

6. Azure Policy Security Baselines and Governance

Azure Policy enforces organizational security standards and assesses compliance at scale across management groups and subscriptions. Azure Policy Engine

  • │
  • ┌───────────┴───────────┐
  • ▼ ▼
  • Initiatives Policy Definitions
  • (Policy Sets) (Single Evaluation Rules)
  • │ │
  • └───────────┬───────────┘
  • ▼
  • Policy Assignments
  • (Scope: MG / Sub / RG / Resource)
  • Policy Definitions vs. Initiatives

Policy Definition : A single rule condition expressed in JSON that evaluates a specific resource property (e.g., requiring tag Environment , restricting allowed VM SKUs, or enforcing storage HTTPS).

Initiative (Policy Set) : A collection of related policy definitions grouped together to achieve a broader compliance goal (e.g., the Microsoft Cloud Security Benchmark or Regulatory Compliance initiatives like PCI-DSS).

Azure Policy Effects (Execution Order):

Disabled : Policy rule is not evaluated.

Audit : Evaluates resource compliance and logs a non-compliant event in Azure Policy reporting without blocking resource deployment.

Deny : Evaluates resource creation or update request in ARM; if non-compliant, ARM immediately rejects the API call with a 403 Forbidden error.

AuditIfNotExists : Checks if a related sub-resource or setting exists (e.g., verifying if diagnostic logs are configured for a Key Vault). If absent, logs an audit event.

DeployIfNotExists (DINE) : Checks if a sub-resource or setting exists; if non-compliant, automatically triggers a remediation task via a Managed Identity to deploy the missing resource (e.g., deploying the Defender for Cloud agent).

Modify : Adds, alters, or removes specified tags or resource properties during creation or update (e.g., automatically appending default tags).