Governance, Management Groups and Compliance
AZ-305 AZ-305 · Design identity, governance, and monitoring solutions
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.
Exam traps to watch for
- Applying a Deny policy immediately without an Audit phase — you will block legitimate deployments; measure first, then enforce.
- Putting every workload in one subscription to 'keep it simple' — subscriptions are the billing, quota, and isolation boundary; separate production from non-production.
- Confusing resource locks with Azure Policy — locks prevent deletion or modification of specific resources; policy enforces rules across scopes.
- Forgetting that RBAC and policy assignments at a management group inherit to all subscriptions beneath it — a broad assignment high in the tree has a wide blast radius.
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?
Explanation: Separate subscriptions give separate billing and isolation boundaries, and a policy assigned at the management group inherits to every subscription beneath it — both requirements met. Option B is wrong because one subscription means one bill and no subscription-level isolation. Option C is wrong because management groups group subscriptions, not resources, and assigning policy per resource group is unmanageable. Option D is wrong because separate tenants would fragment identity and are far more drastic than needed.
Exam objective: AZ-305 Domain 1: Design governance
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?
Explanation: Starting with Audit measures the blast radius without breaking anything; once the compliance report shows what would be blocked, the team can remediate and then switch to Deny. Option D is wrong because an immediate Deny could block legitimate deployments and break existing automation. Option C is wrong because locks prevent modification or deletion, not deployment location. Option A is wrong because RBAC cannot express location-based rules — that is Policy's job.
Exam objective: AZ-305 Domain 1: Design governance
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?
Explanation: A Modify (or Append) policy can add the costCentre tag automatically, inheriting the value from the resource group, so tagging happens without relying on users. Option C is wrong because Deny would block deployments but would not add tags. Option A is wrong because Audit only reports missing tags without fixing them. Option D is wrong because DeployIfNotExists deploys resources, not tags.
Exam objective: AZ-305 Domain 1: Design governance
Q4.A company must demonstrate compliance with ISO 27001 across its Azure estate and remediate gaps. Which combination should the architect recommend?
Explanation: Defender for Cloud maps resources against the ISO 27001 standard and reports compliance posture with remediation guidance, while Azure Policy enforces the controls — reporting plus enforcement. Option B is wrong because Cost Management addresses spend, not compliance. Option A is wrong because locks prevent accidental changes but do not assess or enforce compliance standards. Option D is wrong because read access for auditors is not a compliance programme.
Exam objective: AZ-305 Domain 1: Design governance
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?
Explanation: Access packages bundle the five applications into one requestable unit with manager approval and built-in expiration — exactly the requirement. Option D is wrong because access reviews check existing access rather than provisioning a bundle with approval. Option A is wrong because Conditional Access controls sign-in conditions, not access provisioning. Option C is wrong because PIM manages privileged role activation, not standard application access for contractors.
Exam objective: AZ-305 Domain 1: Design governance
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?
Explanation: A CanNotDelete lock prevents deletion of the resource group and its resources while still allowing modifications — it matches the requirement precisely. Option A is wrong because a ReadOnly lock would block all updates, not just deletion. Option D is wrong because a Deny policy on deletes is not how resource protection is implemented and would be fragile. Option C is wrong because removing Contributor access would prevent administrators from doing their jobs.
Exam objective: AZ-305 Domain 1: Design governance
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?
Explanation: The Cloud Adoption Framework landing-zone model uses a platform subscription for shared services and separate subscriptions per workload or team, giving each team autonomy with clear boundaries while platform governance applies through the management group hierarchy. Option A is wrong because one subscription gives no isolation or separate billing. Option B is wrong because resource groups alone do not provide subscription-level isolation, quotas, or billing. Option C is wrong because separate tenants fragment identity and are unnecessary.
Exam objective: AZ-305 Domain 1: Design governance
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?
Explanation: DeployIfNotExists evaluates whether the agent extension exists on each VM and deploys it when missing — it both remediates existing VMs and covers future deployments. Option C is wrong because Audit only reports non-compliance without fixing it. Option B is wrong because Deny blocks deployments rather than installing the agent. Option A is wrong because Append adds properties to resources during deployment but cannot deploy an extension.
Exam objective: AZ-305 Domain 1: Design governance
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?
Explanation: Access reviews periodically ask reviewers to confirm that access is still needed, and can auto-apply results — including removing access when a reviewer does not respond. Option D is wrong because session controls manage sign-in sessions, not periodic access attestation. Option C is wrong because Azure Policy governs resource compliance, not identity access reviews. Option B is wrong because lifecycle workflows handle joiner-mover-leaver events, not recurring attestation of existing access.
Exam objective: AZ-305 Domain 1: Design governance