This chapter expands on the brief resource-group coverage from the Azure Resource Manager chapter, focusing specifically on resource groups' role in day-to-day resource management. AZ-900 tests this under objective 2.1.
Jump to a section
A simple way to picture Azure Resource Groups
A filing cabinet doesn't just store documents randomly — they're organized into folders by category, making it easy to find related documents together and manage them as a group. Azure Resource Groups work similarly — they're logical containers for organizing related Azure resources, letting you manage, monitor, and control access to them as a group rather than one resource at a time.
What a resource group is
A resource group is a logical container that groups together related Azure resources — virtual machines, storage accounts, databases, and so on — for the purpose of managing, monitoring, and controlling access to them collectively, rather than configuring each resource individually.
Lifecycle management as a group
Because resources share a resource group, common operations can be performed at the group level: monitoring all resources in a group together, applying access control to the entire group, or deleting the group (which also deletes all resources within it).
Resource group location and actual resource locations
A resource group has a location (region) that determines where the group's metadata is stored, but the individual resources within it can be deployed to different regions. The group's location doesn't restrict where resources within it can exist.
Planning resource groups effectively
Common strategies for organizing resources into groups include: by environment (one group for development, one for production), by project (one group per customer or business unit), or by application (resources for one application together). There's no single "right" way — the right organization depends on an organization's specific structure and management needs.
Create a resource group
A resource group is created first, serving as the container for related resources.
Create resources within the group
Individual Azure resources are then created and deployed into the resource group.
Manage resources as a group
Common operations — applying access control, monitoring, or deleting all resources together — can be done at the group level rather than resource by resource.
Plan grouping strategy based on organizational needs
Decide how to organize groups (by environment, project, application, or other criteria) based on what makes sense for your organization's structure and management approach.
A company creates separate resource groups for development and production environments, so access controls and policies can be managed separately for each, and the environments can be monitored independently rather than mixed together.
Objective 2.1 expects candidates to understand resource groups' role as a logical container for organizing and managing related resources.
A common wrong answer is confusing a resource group's location with the locations of resources within it — the group's location only determines where metadata is stored; resources inside it can be in different regions.
Stable terms: resource group. Memory trick: resource groups organize related resources together so they can be managed collectively — not a strict hierarchy, but a flexible grouping for operational convenience.
A resource group is a logical container for organizing related Azure resources for management purposes.
Common operations (applying access control, monitoring, deleting all resources) can be performed at the group level.
A resource group's location only determines where the group's metadata is stored, not where resources within it must be deployed.
Resource group organization strategies vary based on organizational needs — by environment, project, application, or other criteria.
Mistake
A resource group's location determines where all resources within it must be deployed.
Correct
The resource group's location only determines where the group's metadata is stored — resources inside it can be deployed to different regions.
Mistake
There's only one correct way to organize resources into groups.
Correct
The right organization strategy depends on your organization's structure and management needs — common approaches include grouping by environment, project, or application.
It's a logical container that groups related Azure resources together for management purposes, allowing common operations like access control, monitoring, and deletion to be performed at the group level rather than one resource at a time.
No — the resource group's location only determines where the group's own metadata is stored. Resources within the group can be deployed to different regions than the group itself.
There's no single correct strategy — common approaches include grouping by environment (development/production), by project or business unit, or by application, depending on what makes sense for your organization's structure and management approach.
You've just covered Azure Resource Groups — now see how well it sticks with free AZ-900 practice questions. Full explanations included, no account needed.
Done with this chapter?