Study guide

3.2 Resource Groups, Lifecycle, and Move Operations

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.2 Resource Groups, Lifecycle, and Move Operations

Key Takeaways Explain This Topic AI

A resource group is a lifecycle and management boundary for related resources, but resources inside it can exist in different Azure regions.

Moving resources requires provider support, dependency planning, validation, and awareness that some resource IDs can change.

Deleting a resource group deletes contained resources, so locks, backups, dependencies, and shared services must be checked first.

Resource group location stores metadata and does not force all child resources to run in that region.

Last updated: May 2026

What a resource group really controls

A resource group is a container for Azure resources that share a lifecycle, administrative boundary, or deployment purpose. It is not a network boundary and it is not a region boundary. The resource group itself has a location, but that location stores resource group metadata. A resource group located in East US can contain a virtual machine in West US, a storage account in Central US, and a Log Analytics workspace in East US. The resource locations control where the services run.

For AZ-104, the strongest resource group design signal is lifecycle. Put resources together when they are deployed, managed, monitored, and retired together. Put them apart when they are shared by several workloads, owned by different teams, controlled by different policies, or deleted on different schedules. A hub virtual network, a shared Log Analytics workspace, or a Recovery Services vault may not belong in the same resource group as one disposable application environment. Subscription

  • |-- rg-app-payments-prod
  • | |-- vm-payments-01
  • | |-- nic-payments-01
  • | |-- pip-payments-01
  • | `-- disk-payments-01
  • |-- rg-network-hub-prod
  • | |-- vnet-hub-prod
  • | `-- azure-firewall-prod
  • `-- rg-monitoring-prod
  • |-- log-analytics-prod
  • `-- action-group-ops

This layout shows an important exam pattern. The VM and its direct dependencies may be application lifecycle resources. The hub network and monitoring workspace are shared platform resources. Deleting the application resource group should not delete the hub or central monitoring assets.

Lifecycle operations

Resource groups are commonly created by portal, CLI, PowerShell, ARM templates, or Bicep. The portal path is Resource groups > Create , then select subscription, name, region, tags, and review. CLI creation is direct: az group create --name rg-app-payments-prod --location eastus --tags Environment=Prod CostCenter=FIN App=Payments

az group show --name rg-app-payments-prod --query "{name:name, location:location, tags:tags}"

Deleting a resource group is a high-impact operation because Azure attempts to delete all contained resources. Before deletion, check whether the group contains shared resources, protected resources, backup vault dependencies, private endpoints, disks, public IPs, managed identities, role assignments, or diagnostic settings. A delete lock can prevent deletion. A dependent resource in another group can also create cleanup surprises.

Move operations and provider support

Azure supports moving many resources between resource groups or subscriptions, but not all resources can move, and not all move together cleanly. The safe workflow is inventory, dependency mapping, validation, maintenance window, move, and post-check. The portal includes a move experience from the resource group or resource blade. CLI uses commands such as az resource move , but you still need resource IDs and provider support. az resource list --resource-group rg-old --query "[].{name:name,type:type,id:id}" --output table

az resource move --destination-group rg-new --ids /subscriptions/<subId>/resourceGroups/rg-old/providers/Microsoft.Network/publicIPAddresses/pip1

Move validation matters. Azure Resource Manager validates whether the selected resources can move and whether dependencies are included. For example, moving a VM usually requires planning for its NICs, disks, public IP addresses, availability set, load balancer references, backup configuration, and extensions. Some resources can move across resource groups in the same subscription but not across subscriptions. Some resources cannot move at all. Some moves temporarily lock resources for management operations while the move completes.

  • Move concern Administrator check
  • Provider support Confirm the resource type supports the desired move path
  • Dependencies Move required related resources together or redesign references
  • Region Moving resource groups or subscriptions does not change resource region
  • RBAC Confirm permission at source and destination scopes
  • Policy Destination scope policies may block the move
  • Resource IDs Downstream automation may rely on old resource IDs

A classic exam trap is assuming a move changes region. Moving a resource to another resource group or subscription does not relocate the underlying service to another Azure region. To change a VM region, you typically redeploy, replicate, restore, or use a service-specific migration approach. To change a storage account region, you use replication, failover, copy, or create a new account depending on the goal and redundancy configuration.

Scenario workflow

Suppose a team created all development resources in rg-temp , but the network team now wants shared network resources moved to rg-network-dev . Start by listing resource types and dependencies. Move only resources whose lifecycle is truly network-owned. A subnet cannot exist outside its virtual network, and many child resources are bound to parents. If a network interface belongs to a VM lifecycle, moving only the virtual network may be valid, but moving the NIC without the VM may not meet the ownership goal.

Then check locks and policies. A CanNotDelete lock may not block a move, but locks and policy can still affect related operations. A policy at the destination requiring a tag may deny the moved resource if tags are missing. If remediation is needed, tag before moving or use an approved exemption.

Finally, update runbooks, dashboards, budgets, and access reviews. If operations scripts point to a resource group name, they may fail after the move. If RBAC was assigned at the old resource group scope, users may lose access after resources move to the new scope. That is a tested AZ-104 behavior: scope-based access follows the scope, not the user's intention.

Exam traps

Do not put every resource for a subscription into one large resource group. It makes deletion risky and access messy. Do not create one resource group per resource by default. It makes policy, RBAC, and cost operations noisy. Use lifecycle as the main rule and then adjust for ownership, compliance, and shared services.

Do not rely on tags alone for deletion safety. Tags classify resources, but they do not prevent deletion. Use locks for delete protection, RBAC to restrict who can delete, Azure Policy to enforce creation standards, and backups or replication for recovery. Resource group design is one layer of governance, not the whole system.