Identity and access
Microsoft Entra ID
Entra ID is the cloud directory: users, groups, devices, applications, and single sign-on to Azure, Microsoft 365 and thousands of SaaS apps. Key objects:
- Users and groups — humans; groups are the unit for role assignment.
- App registrations / service principals — identities for applications and automation (≈ IAM users/roles for apps). Credentials: client secrets (avoid), certificates, or federated credentials.
- Managed identities — identities for Azure resources with no credentials to manage (≈ IAM roles for EC2/instance profiles):
- System-assigned — tied to one resource's lifecycle.
- User-assigned — a standalone identity you can attach to several resources (and use for AKS workload identity).
- Workload identity federation — trust external tokens (GitHub Actions OIDC, Kubernetes service account tokens, other clouds) to get Entra tokens without secrets — the Azure equivalent of AWS OIDC role assumption and IRSA.
- Conditional Access, MFA, and Privileged Identity Management (PIM) for just-in-time elevation to privileged roles.
Azure RBAC
Authorisation for Azure resources = role assignment = security principal + role definition + scope.
- Scopes: management group → subscription → resource group → resource (inherited downward).
- Built-in roles:
- Owner — full access including assigning roles.
- Contributor — manage all resources but can't grant access.
- Reader — view only (least privilege for read access).
- User Access Administrator — manage access only.
- Hundreds of service-specific roles (AKS Cluster User, Key Vault Secrets User, Storage Blob Data Reader...).
- Custom roles with specific actions/dataActions.
- Deny assignments exist but are created by the platform (e.g. by Blueprints/managed apps), not ad hoc.
Note the control plane vs data plane split: "Contributor" on a storage account doesn't automatically let you read blobs via Entra auth — you need a data role like "Storage Blob Data Reader". Same with Key Vault (RBAC mode) and AKS (Kubernetes RBAC with Entra integration).
Entra/RBAC vs AWS IAM in one paragraph
AWS IAM combines identities and permission policies within each account (users, roles, policies attached to them or to resources). Azure separates the directory (Entra ID — identities for the whole organisation, shared with Microsoft 365) from authorisation (Azure RBAC role assignments at hierarchical scopes). Azure has no equivalent of resource-based IAM policies for most services; access is assigned on the resource scope instead.