Governance, Management Groups and Compliance

AZ-305 AZ-305 · Design identity, governance, and monitoring solutions

By Abu Anns · Last updated 20 November 2026Exam version: AZ-305 (skills measured as of 17 April 2026)

Governance is how an organisation keeps a sprawling cloud estate under control: who can create what, where resources may live, which standards they must meet, and what everything costs. AZ-305 tests governance as a design discipline — the management-group hierarchy, the policy framework, the tagging strategy, and identity governance — because architects who ignore governance build environments that become unmanageable within a year.

The management hierarchy: management groups, subscriptions, resource groups

Azure organises resources in a four-level hierarchy. Management groups sit at the top and group subscriptions for governance: policies and RBAC assignments applied at a management group flow down to every subscription beneath it. Microsoft's Cloud Adoption Framework recommends a simple hierarchy: a root management group, then platform and landing-zone groups, with further groups for decommissioned or sandbox subscriptions. Keep the tree shallow — deep hierarchies are hard to reason about and a policy applied high up affects everything below it. Subscriptions are the unit of billing, quota, and access boundaries: use separate subscriptions to isolate environments (production vs non-production), workloads with different compliance needs, or business units that need separate billing. Note the limits that drive this design: a subscription has quotas, and some resources (like virtual networks) live within one subscription unless peered. Resource groups are deployment and lifecycle containers — resources that share a lifecycle go in one group so they can be deployed, managed, and deleted together. A resource group has a location, but the resources inside it can live in other regions; the group's location only governs where its metadata lives. Design rule: align the hierarchy to how the organisation actually operates, keep it as flat as possible, and put governance (policy, RBAC) at the highest level that is still safe.

Azure Policy: guardrails, not gates

Azure Policy enforces rules over resources. Policy definitions state a rule and an effect: Deny blocks non-compliant deployments; Audit reports them without blocking; Append and Modify add or change properties during deployment; DeployIfNotExists deploys something (like a diagnostic setting or an agent) when it is missing. Initiatives bundle definitions into a set — for example, the built-in regulatory compliance initiatives for ISO 27001, PCI DSS, or NIST. Policies are assigned at a scope (management group, subscription, or resource group) and support exemptions for justified exceptions. The exam's key design judgement is choosing the effect: use Audit first to measure the blast radius, then move to Deny once you know what will break. A classic trap is applying a Deny policy that blocks a legitimate deployment path — for example, denying all public IPs will break an Application Gateway deployment that needs one. Also remember that policies evaluate at deployment time and periodically afterwards for existing resources (via compliance scans), and that resource locks (CanNotDelete, ReadOnly) protect individual resources from accidental deletion or modification — locks are a different mechanism from policy and apply at the resource, group, or subscription level.

Tagging and naming

Tags are name-value pairs on resources, and a tagging strategy is a small design with outsized consequences: tags drive cost allocation, automation, and policy targeting. A typical strategy requires tags such as environment (prod/dev/test), owner, cost centre, and project. Enforce it with policy: an Append/Modify policy can add missing tags from the resource group, and a Deny policy can block deployments without required tags. Naming conventions matter too — consistent, descriptive names make resources findable and make policy and automation rules easier to write. The exam often embeds tagging in a cost-management scenario: "the finance team cannot tell which department owns each resource" is a tagging problem, solved with a required-tags policy plus cost analysis grouped by tag.

Identity governance

Governance also covers who has access and whether they should still have it. Entra ID Governance provides access reviews (periodic attestation that group memberships and role assignments are still needed), entitlement management (access packages that bundle the resources a role needs, with request and approval workflows), and Privileged Identity Management (covered in the authorisation guide). Lifecycle workflows automate joiner-mover-leaver processes: when an employee joins, moves team, or leaves, group memberships and access adjust automatically. In exam scenarios, "access must be reviewed every quarter" means access reviews; "contractors need a bundle of apps approved by their manager" means entitlement management access packages; "access must be removed automatically when someone leaves" means lifecycle workflows. Combine these with Conditional Access and PIM for a complete identity governance design.

Compliance and cost management

Microsoft Defender for Cloud provides the compliance dashboard: it maps your resources against regulatory standards (via built-in initiatives) and reports a secure score with remediation guidance. Use it to answer "are we compliant with ISO 27001?" — but remember it reports posture, it does not enforce it; enforcement is Policy's job. For cost, Microsoft Cost Management provides budgets, alerts, and cost analysis; Azure Advisor gives cost recommendations (rightsizing VMs, deleting idle resources); and reservations and Azure Hybrid Benefit reduce costs for steady-state workloads. A complete governance design ties these together: hierarchy for boundaries, policy for guardrails, tags for accountability, Defender for Cloud for posture, and Cost Management for spend.

Cost governance

Governance without cost control is incomplete. Microsoft Cost Management provides budgets with alert thresholds, cost analysis grouped by tag, subscription, or resource group, and anomaly detection. Design budgets at the level where accountability sits — usually per subscription or per cost-centre tag — and set alerts at 80 and 100 percent of budget so teams act before overspending. Azure Advisor continuously recommends cost savings: rightsizing underused VMs, deleting unattached disks and idle public IPs, and buying reservations for steady workloads. For large estates, Azure reservations and savings plans commit to one- or three-year terms for compute in exchange for deep discounts; the design judgement is reserving only the steady-state baseline and leaving variable load on pay-as-you-go. Azure Hybrid Benefit lets organisations reuse on-premises Windows Server and SQL Server licences in Azure. A complete governance design ties cost to ownership: every resource tagged with a cost centre, budgets per team, and a monthly review of Advisor recommendations. When an exam scenario mentions unexpected cloud spend, the answer is usually tagging plus budgets plus Advisor — not a new tool.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.A company is designing its Azure hierarchy. Production workloads must be billed separately from development, and a security policy must apply to every subscription in the company. Which design meets both requirements?

Report an error

Q2.An architect wants to enforce that all virtual machines are deployed only in the West Europe and North Europe regions. The team is unsure how many existing deployments would be affected. What is the best first step?

Report an error

Q3.The finance team cannot allocate Azure costs to departments because resources are inconsistently tagged. The architect must ensure every new resource carries a costCentre tag inherited from its resource group. Which policy effect should be used?

Report an error

Q4.A company must demonstrate compliance with ISO 27001 across its Azure estate and remediate gaps. Which combination should the architect recommend?

Report an error

Q5.A company hires many contractors who each need access to the same set of five applications, approved by their hiring manager, with access automatically expiring after six months. Which Entra ID Governance feature best delivers this?

Report an error

Q6.An administrator accidentally deleted a production resource group containing a critical database. The company wants to prevent this happening again while still allowing normal updates to the resources inside. What should the architect recommend?

Report an error

Q7.A company is planning its landing zone. The platform team will manage shared networking and identity, while application teams will deploy their own workloads. Which hierarchy best supports this operating model?

Report an error

Q8.An organisation must ensure that every virtual machine has the Azure Monitor Agent installed for security monitoring, including VMs deployed in the future. Which policy effect should the architect recommend?

Report an error

Q9.A security team wants group memberships for sensitive applications to be re-confirmed by managers every 90 days, with access removed automatically if the manager does not respond. Which feature should the architect recommend?

Report an error