"Who Holds the Keys? Mastering Azure RBAC Without Compromising Security"
AZ-104 Series: Post 3
RBAC: The Key Master of the Cloud
Imagine you run a world-class luxury hotel. Would you give the receptionist, the chef, the cleaning crew, and the guests the exact same master key card? Of course not.
In the cloud, giving everyone "Global Admin" or "Owner" permissions is a recipe for absolute disaster. That's where RBAC (Role-Based Access Control) comes in. It ensures people can do their jobs—and absolutely nothing else.
The Anatomy of an RBAC Assignment
An RBAC rule is just a simple sentence that connects three puzzle pieces:
- Who (Security Principal): The user, group, or application that needs access.
- What (Role Definition): The list of allowed actions (e.g., Read, Write, Delete).
- Where (Scope): The boundary where that rule applies (Management Group, Subscription, or Resource Group).
The Big Three Core Roles
Azure has hundreds of specialized roles, but for the AZ-104 exam, you must master the fundamental built-in roles:
-
Owner
Has full access to all resources, including the power to grant access to other people. (Limit this to very few people!) -
Contributor
Can create and manage all types of Azure resources but cannot grant access to others. -
Reader
Can view existing Azure resources but cannot create, modify, or delete anything. Safest bet for auditors!
⚠️ The Ultimate AZ-104 Exam Trap
Many students confuse Azure RBAC Roles with Microsoft Entra ID Roles. They are completely different!
- Microsoft Entra ID Roles manage your identity directory (creating users, changing passwords, managing licenses).
- Azure RBAC Roles manage your cloud infrastructure (spinning up virtual machines, configuring networks, creating storage accounts).
⚓ Cloud-Clipper Challenge
In your free tier sandbox, create a test user and assign them the Reader role on a specific Resource Group. Log in as that user and try to create a storage account. Watch how beautifully Azure blocks the attempt!
Next Up: Turning on the Engines — Our First Look at Azure Storage Tiers! 📦