Study guide

3.6 Azure Governance Features: Putting It All Together

Microsoft Azure Fundamentals AZ-900

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the Microsoft Azure Fundamentals (AZ-900) Exam Study Strategies and Exam Tips

2 Domain 1: Cloud Concepts (25-30%)

1.1 What Is Cloud Computing? 1.2 Cloud Service Models (IaaS, PaaS, SaaS) 1.3 Cloud Deployment Models (Public, Private, Hybrid) 1.4 The Consumption-Based Model

3 Domain 2A: Azure Architecture Components

2.1 Azure Regions and Availability Zones 2.2 Azure Resource Hierarchy (Management Groups, Subscriptions, Resource Groups) 2.3 Azure Resource Manager (ARM) Overview

4 Domain 2B: Azure Compute Services

2.3 Azure Virtual Machines 2.4 Azure App Service, Containers, and Serverless 2.5 Azure Virtual Desktop

5 Domain 2C: Azure Networking Services

2.6 Azure Virtual Networks (VNet) 2.7 Azure VPN Gateway and ExpressRoute 2.8 Azure Load Balancing and Content Delivery

6 Domain 2D: Azure Storage Services

2.9 Azure Storage Accounts and Services 2.10 Azure Database Services 2.11 Azure Data Services and Analytics

7 Domain 2E: Azure Identity, Access, and Security

2.11 Microsoft Entra ID (Azure Active Directory) 2.12 Azure RBAC, Zero Trust, and Defense in Depth 2.13 Azure Security Services

8 Domain 3A: Azure Cost Management

3.1 Factors That Affect Azure Costs 3.2 Azure Pricing Calculator and Cost Management 3.3 Using Tags for Cost Management and Organization

9 Domain 3B: Azure Governance and Compliance

3.3 Azure Policy 3.4 Resource Locks and Tags 3.5 Azure Blueprints, ARM Templates, and Bicep 3.6 Azure Governance Features: Putting It All Together

10 Domain 3C: Azure Monitoring and Management Tools

3.6 Azure Monitor and Service Health 3.7 Azure Compliance, Privacy, and Trust 3.8 Azure Activity Log, Diagnostics, and Resource Health

11 Additional Azure Services and Exam Review

Azure AI and Machine Learning Services Azure IoT and DevOps Services AZ-900 Exam Review: Key Concepts Summary Common AZ-900 Exam Scenarios and Practice

12 Advanced Azure Topics and Service Deep Dives

Azure Migration Services and Tools High Availability and Disaster Recovery in Azure Azure Networking: Private Link, Service Endpoints, and Bastion Azure Management Tools: Portal, CLI, PowerShell, and Cloud Shell Azure SLAs, Service Lifecycle, and Support Plans

3.6 Azure Governance Features: Putting It All Together

Key Takeaways Explain This Topic AI

Governance combines Management Groups (scope), Azure Policy (rules), RBAC (access), Resource Locks (protection), and Tags (organization).

Policy applied at a management group inherits down to every subscription, resource group, and resource beneath it.

RBAC answers WHO, Azure Policy answers WHAT — a request must satisfy both gates inside Azure Resource Manager.

Microsoft Purview Compliance Manager gives a compliance score and prioritized improvement actions mapped to standards.

Exam scenarios test intent: access → RBAC, resource rules → Policy, prevent deletion → Locks, organize for cost → Tags.

Last updated: October 2026

Quick Answer: Azure governance = Management Groups (scope) + Azure Policy (resource rules) + RBAC (access) + Resource Locks (protection) + Tags (organization) + Budgets (cost). These tools layer together so one request must pass every relevant gate before it succeeds.

The Azure Governance Stack

No single feature delivers governance; each plays one role and they compound.

Feature Purpose Concrete example

Management Groups Organize subscriptions into a hierarchy for shared governance All prod subscriptions under a "Production" management group

  • Azure Policy Enforce rules on resource configuration "All storage accounts must require HTTPS"
  • RBAC Control who can do what "Jane is Contributor on the Prod subscription"
  • Resource Locks Guard against accidental change/deletion CanNotDelete on the production SQL database
  • Tags Label resources for cost and ops CostCenter: CC-1001 on Finance resources
  • Budgets & Alerts Track spending and alert at thresholds Alert at 80% of the monthly budget

Microsoft Purview Compliance Manager Score compliance against standards A compliance score with improvement actions

The scope hierarchy that ties it together flows top-down: Management Group → Subscription → Resource Group → Resource . Both Policy and RBAC assignments inherit down this chain, so where you assign matters as much as what you assign.

  • How the Features Interact
  • Policy + RBAC (complementary gates)

RBAC decides: Can this identity perform the action?

Policy decides: Is the resulting resource configuration allowed?

Both run inside Azure Resource Manager, so an Owner can still be blocked by a Deny policy. Granting access does not exempt anyone from configuration rules.

Management Groups + Policy (inheritance)

Assign a policy once at the Dev management group and every dev subscription beneath it inherits it.

Example: "Deny VM SKUs above 4 vCPUs" at the Dev management group stops oversized VMs across all dev subscriptions in one move — far better than per-subscription assignments.

Tags + Cost Management (chargeback)

Tag resources with Department: Marketing , then filter Microsoft Cost Management by that tag to see Marketing's exact spend and set a tag-scoped budget.

Locks + RBAC (layered protection)

A CanNotDelete lock on a production resource group blocks accidental deletion even for Owners, while RBAC still governs who may edit — two independent safety nets.

Governance Decision Matrix

  • "I want to..." Use this feature
  • Organize subscriptions hierarchically Management Groups
  • Restrict which regions resources deploy to Azure Policy (Allowed locations)
  • Control who can manage resources RBAC role assignments
  • Prevent accidental deletion of critical resources Resource Locks (CanNotDelete)
  • Track spend by department or project Tags + Cost Management
  • Require encryption or HTTPS on resources Azure Policy
  • See compliance posture against standards Microsoft Purview Compliance Manager
  • Enforce tagging on every new resource Azure Policy (Require a tag)
  • Track spending with threshold notifications Budgets and Alerts
  • Microsoft Purview Compliance Manager

Microsoft Purview Compliance Manager quantifies your posture as a compliance score and lists prioritized improvement actions mapped to standards such as ISO 27001, GDPR, and NIST. It separates Microsoft-managed controls from your-managed controls so you know what you still owe.

On the Exam: Governance questions usually describe a goal and ask which feature fits. Decode the intent — who can act = RBAC, what config is allowed = Policy, don't let it be deleted = Locks, organize/track cost = Tags, apply broadly across subscriptions = assign at a Management Group.

An End-to-End Governance Scenario

A bank consolidates governance under one root management group , then creates child groups for Production and Non-Production . At the Production group it assigns RBAC so only the platform team holds Contributor, and an initiative that denies non-HTTPS storage and restricts regions to two approved data residencies. Those rules inherit to every production subscription automatically, so onboarding a new subscription requires no extra setup — it is compliant by inheritance the moment it joins the group.

Production databases receive CanNotDelete locks so an accidental deletion is impossible even for an Owner. Every resource is tagged with CostCenter and Environment , enabling Finance to chargeback spend per department in Cost Management and to set budget alerts at eighty percent of the monthly cap. Finally, the security team watches Microsoft Purview Compliance Manager to track the bank's compliance score against ISO 27001 and GDPR, working through the prioritized improvement actions it surfaces.

Notice how the layers reinforce each other: RBAC limits who , Policy constrains what , locks prevent accidents , tags drive cost visibility , and management groups make all of it scale through inheritance. A single misconfigured request is checked against every applicable gate before Azure Resource Manager allows it.

Common Traps

Assign at the management group when a rule must span many subscriptions — do not repeat per subscription.

A high RBAC role never bypasses a Deny policy ; the gates are independent.

Locks stop deletion, not size or region — those need Policy.

Compliance Manager measures posture ; it does not enforce — Policy enforces.