2. Implementing & Managing Azure Identities & Governance
Welcome to Phase 2, where we elevate our understanding from foundational Azure concepts to the art of managing identities and implementing robust governance in the cloud. Building upon the core principles established in Phase 1, this phase marks a pivotal shift in your learning journey. You'll transition from understanding individual services to strategically integrating them for secure and compliant Azure environments.
This section is crucial for the AZ-104 exam, which demands not just recall, but the ability to apply knowledge to real-world administrative challenges. We'll explore architectural patterns and best practices that ensure your solutions are inherently secure, compliant, and well-managed at scale. The focus here is on comprehension and practical application, enabling you to implement solutions that meet stringent security and governance requirements.
Why care: identity and governance are where many real Azure incidents start. In production, a user given Owner at subscription scope can delete everything in it, a missing policy lets someone deploy into an unapproved region, and a guest invited for a short project keeps access long after it ends. Think of this domain as a building's security desk and its building code: Microsoft Entra ID and RBAC decide who gets in and which doors each badge opens, while Azure Policy and resource locks decide what may be built and what may never be torn down, no matter whose badge it is.
⚠️ Exam Trap: RBAC and Azure Policy answer different questions. RBAC controls who can perform an action; Policy controls what configurations are allowed, whoever deploys them. A requirement such as "even Owners must not create resources outside East US" is a Policy answer, and stopping an Owner from deleting a resource takes a lock, not a role.