Resource Group
An Azure Resource Group is a logical container that holds related resources — VMs, databases, storage accounts — for a solution, sharing a common lifecycle for deployment, access control, and billing. Deleting a resource group deletes every resource inside it, and RBAC permissions and tags applied at the resource group level cascade down to everything it contains.
Resource Group
A Resource Group is the smallest unit of lifecycle management in Azure — deleting it deletes everything inside it.
Why It Matters in Production
Swiggy isolates each microservice's infrastructure into its own resource group (swiggy-orders-prod-rg, swiggy-payments-prod-rg) so a team can tear down and rebuild their stack without touching anyone else's resources.
az group create --name swiggy-orders-prod-rg --location centralindia
RememberA resource can only belong to one resource group at a time, but the resource group and the resource itself can live in different regions.
Frequently Asked Questions
Can resources in a Resource Group span multiple Azure regions?
Yes — a Resource Group itself has a location (which mainly determines where its metadata is stored), but the resources inside it can be deployed to any Azure region. This is common for multi-region architectures where a single logical application's resource group contains VMs or databases spread across two regions for disaster recovery. The grouping is organizational, not a network or regional boundary.
What's a common mistake teams make with resource group organization?
Putting everything — dev, staging, and production — into one flat resource group 'to keep it simple.' Because deleting a resource group deletes everything inside it, and RBAC/tags cascade down, this makes it far too easy to accidentally destroy production while cleaning up a dev experiment, or grant a contractor's scoped access to more than intended. The standard practice is one resource group per environment (or per application-plus-environment combination), matching both lifecycle and blast radius.