Subscriptions & Resource Groups
The billing, scale and access boundary for resources, and the resource group lifecycle that organises them.
Readiness
0%
1h 30m baseline
Exam memorization points
- A subscription is simultaneously a billing boundary, an access control boundary and a scale/quota boundary.
- A subscription trusts exactly one Entra ID tenant; a tenant can have many subscriptions.
- Every resource lives in exactly one resource group and one subscription. Resource groups cannot be nested.
- A resource group name and location are fixed at creation - the name cannot be changed. The location stores metadata only.
- Deleting a resource group deletes every resource inside it. There is no recycle bin at resource-group scope.
- Tags are not inherited by child resources and are not enforced unless Azure Policy enforces them.
Traps & distractors
- Assuming every resource type can be moved between subscriptions or resource groups. Support for move is per resource type and some cannot move at all.
- Moving a resource changes its resource ID, which breaks hard-coded references in scripts, DNS records and role assignments.
- Confusing the resource group location with the location of the resources inside it - they are independent.
- Expecting subscription quotas to be shared. vCPU and other quotas are per subscription per region.
Suggested lab
Resource group hygiene and tags
Experience resource group lifecycle behaviour and tag inheritance rules first hand.
- 1Create two resource groups with a naming convention such as rg-az104-dev-eastus and rg-az104-prod-eastus.
- 2Deploy a storage account into each and apply tags at the resource group level only.
- 3Inspect the storage account tags to confirm tags were not inherited.
- 4Move the storage account from the dev group into the prod group and capture the old and new resource IDs.
- 5Create a throwaway resource group, deploy a resource and delete the group to observe cascade deletion.
Microsoft Learn
- Azure Resource Manager overviewdoc
- Search Microsoft Learn: move resources between resource groups and subscriptionssearch
Live Microsoft Learn ingestion is a Sprint 2 item; until then links are curated and the search fallback always resolves.
Status
No time invested yet. Baseline assumptions only.
Self-assessed mastery
0%
Critical priority
High-yield and still weak. Study this next.
- Exam importance80% × 30% = 24.0
Learner-agnostic frequency on the real exam (4/5).
- Blueprint weight100% × 25% = 25.0
This topic's domain carries 22.5% of the exam objectives.
- Dependency leverage99% × 20% = 19.8
28 later topics depend on it.
- Current gap100% × 25% = 25.0
Readiness is 0%, so 100% of the topic is still uncovered.
Exam Priority Score = 30% importance + 25% blueprint + 20% dependency + 25% gap. Importance is exam frequency, blueprint is the domain's official exam weight, dependency is how many later topics this one unlocks, and gap is how far you currently are from ready.
Unlocks next
28 topics downstream in total.
Baseline study time
1h 30m
Complexity
2 / 5
Remaining to target
1h 17m
Status weight
0%
Topics: resource group, billing, quotas, tags, move, resource id
Weak neighbours in Identities