Azure Resources and Resource Groups
Slide deck explaining Azure resources and resource groups, their definitions, Azure Resource Manager (ARM) scopes, management controls, location concepts, and best practices for organization and deletion.
Azure Resources and Resource Groups
Introduction to Azure Resources and Resource Groups, covering manageable items in Azure and their logical containers.
Azure Resources and Resource Groups
Introduction to Azure Resources and Resource Groups, covering manageable items in Azure and their logical containers.
Resources vs Resource Groups
Resources are the things you run; resource groups are how you manage them together. Resource equals manageable item in Azure. Resource group equals logical container for related resources. You manage, secure, and clean up at the group level.
Azure Resource (definition)
If you can create and manage it in Azure, it's a resource. Manageable item in Azure. Examples: Virtual Machine (VM), storage account, database. Resources have their own settings and lifecycle.
Resource Group (definition)
A resource group is a logical container to manage related resources as a unit. Contains related resources within a subscription. Common uses: deploy, monitor, control access, clean up. Good boundary for a solution or environment (dev/prod).
Azure Resource Manager (ARM) and scopes
ARM uses scopes so you can apply settings at the right level. Azure Resource Manager (ARM) equals management layer for Azure. Scope hierarchy: Management group → Subscription → Resource group → Resource. Resource group scope is often 'just right' for a solution.
Common controls at Resource Group scope
Resource groups are a practical place to apply access and governance. Role-Based Access Control (RBAC): permissions for people/teams. Azure Policy: guardrails for what can be created/configured. Resource locks: prevent accidental change/deletion.
Rule: A resource belongs to one group
A resource can be in only one resource group at a time. One resource → one resource group (at a time). Moving may be possible, but depends on resource type. Use naming/tags for organization across groups.
Resource Group location ≠ Resource location
The resource group's location is for metadata; resources choose their own regions. Resource group location stores metadata. Resources can be in different Azure regions. Each resource has its own location setting.
Quick diagnostic: Thing vs Container
If it runs or has settings, it's a resource; if it groups them, it's a resource group. VM, storage, database equals resources. Resource group equals place to manage related resources together. Not a 'service'; it's a management container.
Dev vs Prod: resource group strategy
Separate resource groups when lifecycle or access needs differ. Different environments often need different RBAC and policies. Separate groups reduce accidental changes. Avoid a pile of per-resource exceptions.
Deletion impact + common pitfalls
Deleting a resource group is usually a full cleanup action—verify before you do it. Deleting a resource group typically deletes contained resources. Resource locks can block deletion. Tags are not automatically inherited by resources. Scope reminder: Subscription → Resource group → Resource.