liveBook · Manning

Control plane

As explained in Azure Security

A control plane action operates on the configuration or management of an Azure resource rather than on data stored within it.

A control plane action manages an Azure resource itself rather than the data stored inside it. Azure RBAC records these permissions in actions and notActions. section 2.3.2

Separate resource management from access to resource data:

  • A Reader role on a resource group lets Bob view a storage account but does not, by default, let him read its stored data. section 2.3.2
  • Assign control-plane permissions at resource, resource-group, subscription, or management-group scope to limit access. section 2.3.2
az role definition list --name "Virtual Machine Contributor"

Inspect a role definition to identify the control-plane actions it permits, such as virtual-machine management. section 2.3.2

How Azure Security covers it

How deep it goes
Defines action categories, RBAC properties, and scope levels, but does not detail service-specific data-plane permissions.
Examples
Uses a Reader role on a storage-account resource group and an Azure CLI role-definition listing for virtual-machine permissions.
What it assumes
Assumes familiarity with Azure resources and identities while distinguishing control-plane and data-plane permissions.
What you can do after
Apply via Azure RBAC by separating management permissions from data access and choosing a narrowly appropriate scope.
How it connects
Connects Azure RBAC, data plane, role definitions, role assignments, scope, security principals, and least privilege.

Also explained in

Compare how 8 books explain control plane →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Azure Security. The section links point to the parts of the book it draws on.