Resources and Resource Groups
😟 THE PROBLEM
Hundreds of resources in one place, and someone deletes a production database by mistake.
😊 THE SOLUTION
Group related resources into resource groups by app and environment.
- Hard to find what belongs to which app✓ One resource group per app and environment
- Cleaning up 15 test resources one by one✓ Delete the whole test resource group
- Testers can touch production✓ Set permissions per resource group
Quick answer
An Azure resource is anything you create in Azure, such as a virtual machine, storage account, database or virtual network. A resource group is a logical container that holds related resources so you can manage, secure and delete them together. Every resource must be in exactly one resource group, and resource groups cannot be nested.
Exam objective: 2.1.4 Describe Azure resources and resource groups. (Skills measured as of July 20, 2026)
Start with a question
How would you find the 12 things that make up your online shop among 500 things in your company’s Azure?
Without organisation you would be scrolling forever, and deleting the wrong thing would be easy. Azure gives you resource groups: folders that keep related things together.
Explain it like I’m 10
The technical explanation
A resource is a manageable item in Azure: virtual machines, storage accounts, web apps, databases, virtual networks and so on. Every resource lives in a resource group, a logical container managed through Azure Resource Manager.
| Rule | What it means |
|---|---|
| One group per resource | A resource belongs to exactly one resource group (it can be moved) |
| No nesting | You cannot put a resource group inside another |
| Mixed regions | Resources can be in different regions from the group |
| Delete together | Deleting a group deletes everything in it |
| Inheritance | RBAC permissions and Azure Policy on a group apply to its resources |
Real-world business scenario
An online shop
- The problem
- All resources for production, testing and experiments were in one big group. Someone deleted a test database that was actually production.
- What they used
- Split into rg-shop-prod, rg-shop-test and rg-experiments, with tighter permissions on production.
- Why that choice
- Grouping by lifecycle and environment makes access control and clean-up safe and simple.
- The result
- Testers can delete freely in test groups, and production is protected.
When to use it and when not to
✓ Use it when…
- Group resources that share a lifecycle, for example one app in one environment.
- Apply permissions and policies once at the group level.
✕ Think twice when…
- Putting everything in one giant resource group.
- Mixing production and test resources in the same group.
Interview preparation
Say your answer out loud first, then open the model answer. Interviewers care more about your reasoning than the exact words.
Beginner What is a resource group?
Model answer
It is a container that holds related Azure resources, like the VM, database and storage for one app. I can manage access, apply policies, view costs and delete everything in it together.
Interviewer follows up
Can a resource be in two resource groups?
You
No. A resource belongs to exactly one resource group at a time, although it can be moved to another group.
Intermediate What are the important rules about resource groups?
Model answer
A resource is in only one group; groups cannot be nested; resources in a group can be in different regions from the group itself; deleting a group deletes everything in it; and access and policies applied to a group are inherited by its resources.
Experienced developer How do you decide how to split resources into resource groups?
Model answer
Mainly by lifecycle and ownership. Things deployed and deleted together, owned by the same team, go together, for example one group per application per environment such as rg-shop-prod and rg-shop-dev. Shared networking often lives in its own group managed by a platform team. This keeps RBAC, cost reporting and clean-up simple.
Scenario A developer finished testing and wants to remove 15 test resources quickly. What is the easiest way?
Model answer
If they are all in one test resource group, delete the group. Everything inside is deleted in one operation. That is why grouping by lifecycle is so useful.
Test yourself with exercises
3 original practice questions in the AZ-900 style. Pick your answers, then check them. You will see why each option is right or wrong. Score 75% or more and this topic is marked complete.
Quick revision
Key points
- A resource is any item you create in Azure.
- A resource group is a logical container for related resources.
- Each resource is in exactly one group; groups cannot be nested.
- Deleting a group deletes all its resources.
- Access (RBAC) and policies set on a group are inherited by its resources.
Important terminology
- Resource
- A manageable item you create in Azure, such as a VM, storage account or web app.
- Resource group
- A logical container for resources that share a lifecycle, owner or purpose.
- Lifecycle
- When resources are created, updated and deleted. Resources with the same lifecycle belong in the same group.
Common mistakes
- Believing resources must be in the same region as their resource group.
- Forgetting that deleting a resource group deletes everything inside.
Exam tips
- "Delete all resources for a project at once" = put them in one resource group and delete the group.
- Resource groups cannot be nested.
Five quick revision questions
-
1.How many resource groups can one resource belong to at a time?Show
One.
-
2.Can resource groups be nested?Show
No.
-
3.What happens when you delete a resource group?Show
All the resources inside it are deleted too.
-
4.Must resources be in the same region as their resource group?Show
No.
-
5.What is the best way to group resources?Show
By shared lifecycle, owner or purpose, for example one app per environment.
Official references
Finished this lesson? Tick it off. Your progress is saved in this browser.
Next up: Azure Subscriptions