Role assignment
A role assignment is an access-control configuration that grants a principal an authorization role or specified permissions for a defined scope.
Azure Security
A role assignment is an Azure authorization object that binds a role definition to a security principal at a specified scope.
- How it is used
- Grants Azure resource permissions by linking a security principal, role definition, and scope.
- How deep it goes
- Walks through scopes, required assignment permissions, Azure CLI creation, returned fields, and PIM active versus eligible assignments.
- Examples
- Uses Virtual Machine Contributor at subscription scope and an exercise assigning Storage Blob Data Contributor to a service principal at resource scope.
- What you can do after
- Apply it via Azure CLI to grant a user, group, or service principal a selected role at a selected scope.
Microsoft Azure in Action
A role assignment is a configuration that grants a specified authorization role to an identity for a scope such as a resource or resource group.
- How it is used
- Grants users, applications, or managed identities permissions to Azure resources at a selected scope.
- How deep it goes
- Defines the three-part RBAC model and demonstrates portal assignments, but does not detail custom role authoring.
- Examples
- Demonstrates Contributor access for a service principal and Storage Blob Data Contributor access for an AI Foundry managed identity.
- What you can do after
- Operate/configure Azure access through Access Control (IAM) by assigning built-in roles to identities at appropriate scopes.
Read how Microsoft Azure in Action explains role assignment →
Authorization in Action
A role assignment is a configuration that associates a principal with an authorization role.
- How it is used
- Deploys role-based authorization by associating principals with permissions through organizational roles.
- How deep it goes
- Explains runtime evaluation, inherited roles, and separation-of-duty constraints, but stops short of dynamic authorization conditions.
- Examples
- Uses healthcare access scenarios and engineering decisions involving code approval and production deployment.
- What you can do after
- Evaluate authorization requests by tracing assigned roles, inherited permissions, and separation-of-duty constraints.
Related concepts
- principalhas part · A principal is a security identity representing an entity, such as a person, application, service, machine, or process, in an authentication or authorization system.
- role configurationhas part · A role configuration specifies a role and its associated responsibilities, permissions, or expected behavior within a system or organization.
- scopehas part · Scope is a defined boundary specifying which entities, activities, resources, or conditions are included or governed in a particular context.
- role-based access controlused by · Role-based access control is an authorization model that assigns permissions to roles and grants users or other principals access through their assigned roles.
- Kubernetesconfigures · Kubernetes is an open-source platform for orchestrating and automating the deployment, scaling, and management of containerized workloads across computing clusters.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.