liveBook · Manning

Role configuration

A role configuration specifies a role and its associated responsibilities, permissions, or expected behavior within a system or organization.

How 2 Manning books explain it

Azure Security

A role definition is an authorization specification that groups permissions into a role assignable to identities.

How it is used
Defines the permissions assigned to identities over specific Azure resource scopes.
How deep it goes
Explains concrete and granular permissions, built-in roles, and custom-role rationale, but does not provide detailed custom-role creation steps.
Examples
Uses Virtual Machine Contributor inspection and a custom role that permits restarting but not creating or deleting virtual machines.
What you can do after
Build custom permission sets or evaluate built-in role definitions against required Azure operations.

Read how Azure Security explains role configuration →

Microsoft Azure in Action

A role definition is a named collection of permissions that specifies the actions allowed by an authorization role.

How it is used
Defines the permissions used by Azure RBAC to control identity access to resources.
How deep it goes
Explains permissions, built-in and custom options, and their combination with principals and scopes; stops short of custom-role syntax.
Examples
Uses Owner, Contributor, Reader, DNS Zone Contributor, and a Contributor assignment to the AlpacaRG resource group.
What you can do after
Apply it via Azure RBAC by selecting a role, scope, and members in Access Control (IAM).

Read how Microsoft Azure in Action explains role configuration →

Related concepts

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.