Study guide

3.1 Subscription Design and Management Groups

AZ-104 Microsoft Azure Administrator Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Orientation and Microsoft Learn Source Control

1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log

2 Chapter 2: Identity, RBAC, and Governance Foundations

2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab

3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization

3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab

4 Chapter 4: Storage Accounts, Access, and Data Protection

4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab

5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep

5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab

6 Chapter 6: Containers, App Service, and Platform Compute

6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab

7 Chapter 7: Virtual Networking, Routing, and Secure Access

7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab

8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting

8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab

9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery

9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab

10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs

10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab

11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path

11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths

3.1 Subscription Design and Management Groups

Key Takeaways Explain This Topic AI

Subscriptions are billing, quota, RBAC, Policy, and deployment boundaries, not just folders for resources.

Management groups provide governance inheritance above subscriptions and should mirror stable control needs rather than every department change.

Azure role assignments, policy assignments, budgets, and resource providers must be evaluated at the correct scope.

A subscription strategy should separate production risk, ownership, compliance, and quota pressure before resources are deployed.

Last updated: May 2026

Subscription scope as an administrator boundary

In Azure, a subscription is the practical container where most administrator work becomes enforceable. It links resources to an Azure offer and billing relationship, but it also creates boundaries for quotas, role assignments, policy assignments, resource provider registration, cost analysis, activity logs, and support operations. On AZ-104, treat a subscription as more than a payment unit. It is often the smallest governance boundary that can cleanly separate production from nonproduction, regulated from unregulated, and centrally managed from application-owned workloads.

A subscription contains resource groups, and resource groups contain resources. Management groups sit above subscriptions and can contain other management groups or subscriptions. A tenant can have a hierarchy of management groups under the tenant root group. Governance assigned at a management group can flow down to child management groups, subscriptions, resource groups, and resources unless exclusions or scope choices change the result. Tenant root group

  • |-- Platform management group
  • | |-- Connectivity subscription
  • | |-- Identity subscription
  • | `-- Management subscription
  • |-- Landing zones management group
  • | |-- Prod subscription A
  • | |-- Prod subscription B
  • | `-- Nonprod subscription A
  • `-- Sandbox management group
  • `-- Developer sandbox subscription

A common exam trap is confusing the hierarchy with deployment placement. You do not deploy a virtual machine into a management group. You deploy the VM into a resource group in a subscription. The management group can govern the VM indirectly through inherited Azure Policy or RBAC assignments, but it is not a resource container for the VM.

Choosing subscription boundaries

Use separate subscriptions when you need a hard administrative or operational boundary. Strong reasons include separate billing ownership, different production controls, different regulatory requirements, subscription quota isolation, workload isolation for risky experiments, or separation between platform services and application teams. Weak reasons include every project name, every cost center change, or every short-lived environment. Those are often better handled with resource groups, tags, budgets, and policy.

Design driver Subscription boundary is useful when Resource group or tag may be enough when

Billing Charges must be invoiced or charged back separately Costs only need reporting by app, team, or environment

Security Different administrators must not control each other's resources Same operators manage the workload with different labels

Compliance A policy baseline must apply to all resources in the scope Only a subset of resources needs a tag or naming rule

Quotas Compute, networking, or regional limits may block deployments Quotas are not under pressure

Lifecycle Workload has an independent create, operate, and retire path Resources are part of one application lifecycle

For an enterprise landing zone, subscriptions commonly map to workload or platform boundaries. A connectivity subscription may host hub virtual networks, Azure Firewall, VPN gateways, or ExpressRoute gateways. A management subscription may host Log Analytics workspaces, automation, and monitoring assets. Application subscriptions host the business workloads. This pattern reduces accidental coupling between shared services and application deployments.

Management groups and inherited governance

Management groups are best used for broad, stable governance. Assign policies such as allowed regions, required tags, diagnostic settings, or allowed resource types at a management group when the rule should affect many subscriptions. Assign RBAC at a management group when a central team truly needs access across all child subscriptions. Do not use broad Owner or User Access Administrator assignments casually. They are powerful and are inherited by child scopes.

A practical hierarchy usually starts simple. Create top-level groups for platform, landing zones, sandbox, and decommissioned subscriptions. Put production and nonproduction under separate child groups only when they need different rules. If the company later reorganizes, do not immediately mirror every new department. Management groups should represent durable governance needs, not a volatile org chart. Decision workflow

1. Does the rule apply across many subscriptions? Use management group scope.

2. Does the rule apply to one billing or workload boundary? Use subscription scope.

3. Does the rule apply to one application lifecycle? Use resource group scope.

4. Does the rule apply to one resource exception? Use resource scope only when necessary.

Subscription operations you must recognize

Administrators often need to register resource providers before deploying a service. For example, a subscription may need Microsoft.ContainerService , Microsoft.Insights , or Microsoft.RecoveryServices registered before related resources work. Many portal deployments register providers automatically, but template, CLI, or locked-down environments may expose provider registration as a blocker.

  • Useful commands include: az account list --output table
  • az account set --subscription "Prod-Shared-01"

az provider list --query "[?registrationState!='Registered'].{Namespace:namespace, State:registrationState}" --output table

  • az provider register --namespace Microsoft.RecoveryServices
  • az account management-group list --output table

For PowerShell, expect Get-AzSubscription , Set-AzContext , Get-AzResourceProvider , and Register-AzResourceProvider . The exam may show either tool. The decision logic matters more than memorizing every switch.

Exam traps and troubleshooting cues

If a user can see a subscription but cannot create a resource, check RBAC at the target scope, policy denials, provider registration, quota, and region restrictions. If a policy assigned to a management group blocks a deployment in a child subscription, changing the resource group setting alone will not fix it. You must modify the inherited assignment, add an exemption when justified, or deploy in a compliant way.

If cost analysis does not show a resource where expected, confirm the selected scope. Cost Management can view costs at billing, subscription, resource group, or management group scopes depending on account type and permissions. A tag report also depends on tag presence and whether tags were applied before usage occurred.

Remember the AZ-104 pattern: when the question asks for one control applied consistently to many subscriptions, management group is usually the right governance scope. When it asks for isolating billing, quotas, or production risk, a separate subscription is usually the stronger answer. When it asks for a single application lifecycle, start with a resource group unless another boundary requirement is explicit.