RousselTMLEARNING

Cloud computing

Microsoft Entra ID, RBAC and Azure Policy: identities, permissions and governance

Manage identities and access on Azure: Microsoft Entra ID (users, groups, MFA, conditional access), managed identities for applications, RBAC access control and built-in roles, PIM, Azure Policy, locks and tags.

1. Microsoft Entra ID #

The identity directory.

Principles #

Microsoft Entra ID (formerly Azure Active Directory) authenticates users and applications for Azure, Microsoft 365 and thousands of SaaS applications (SSO). It synchronizes with an on-premises Active Directory through Entra Connect.

  • MFA for everyone, and conditional access: require MFA or a compliant device based on risk, location and application.
  • Managed identities: an application on Azure (VM, App Service, Functions) gets an identity with no secret to store.
  • PIM (Privileged Identity Management): administration roles activated on demand, time-limited, with approval.

2. RBAC #

Who can do what, where.

Assigning roles #

Azure role assignment
Explicit denial only exists through deny assignments (Blueprints, managed applications): RBAC is additive.
Built-in rolePermissions
OwnerEverything, including assigning roles
ContributorEverything except assigning roles
ReaderRead only
User Access AdministratorManage role assignments
az role assignment create --assignee-object-id <id-groupe> --assignee-principal-type Group \
  --role "Contributor" --scope /subscriptions/<abonnement>/resourceGroups/rg-app
az role assignment list --scope /subscriptions/<abonnement>/resourceGroups/rg-app -o table
az vm identity assign -g rg-app -n vm-web           # identité managée système

3. Governance #

Azure Policy, locks, tags.

Azure Policy #

Azure Policy enforces rules on resources: allowed regions, mandatory tags, encryption, forbidden SKUs. Effects: deny, audit, modify, deployIfNotExists. Initiatives group policies together (for example the Microsoft cloud security benchmark).

az policy assignment create --name regions-ue --scope /subscriptions/<abonnement> \
  --policy e56962a6-4747-49cd-b67b-bf8b01975c4c \
  --params '{"listOfAllowedLocations":{"value":["francecentral","westeurope"]}}'
az lock create --name ne-pas-supprimer --lock-type CanNotDelete -g rg-prod
az tag update --resource-id /subscriptions/<abonnement>/resourceGroups/rg-app --operation merge --tags centre_cout=1234
Good practice: RBAC says who can act; Azure Policy says what is allowed. The two are complementary.

Related articles

Observability on Azure: Azure Monitor, Log Analytics, Application Insights, managed Prometheus and Grafana

A complete overview of observability on Azure: Azure Monitor (metrics, logs and Log Analytics, KQL), Applicat…

Understanding Azure: regions, resource hierarchy, tools and pricing

Microsoft Azure basics: geographies, regions, region pairs and availability zones, the hierarchy of managemen…

Azure networking: VNet, NSG, peering, load balancing and hybrid connectivity

Design networking on Azure: virtual networks and subnets, network security groups (NSG), peering and hub-and-…

Keep learning

Support us

♥ SUPPORT US

Support RousselTM Learning

Courses, articles, labs and certificates stay free with no intrusive ads. A voluntary contribution, of any amount you choose, pays for hosting, lab environments and new content.

Contribute with PayPal Any amount · card or PayPal accountLearn more
QR code PayPal
Or scan this QR code with your phone

Thank you, every contribution counts!