Azure Fundamentals Step 3 of 6

What Is an Azure Resource Group?

July 22, 2026 · 4 min read ·Beginner
#Azure#Resource Group#Resource Manager#Governance

An Azure resource group is a logical container for resources that you want to manage together. It helps organize an Azure solution by project, environment, workload, or lifecycle.

In this article
  • What a resource group is
  • Where it fits in the Azure hierarchy
  • How to decide which resources belong together
  • What happens when a resource group is deleted

What is a resource group?

A resource group is a container that holds related Azure resources. A virtual machine, network interface, disk, virtual network, and public IP address can be placed in one resource group when they are part of the same solution.

A resource can belong to only one resource group at a time. A resource group belongs to one subscription.

Group resources by lifecycle

Microsoft recommends putting resources with the same lifecycle in the same resource group. Ask these questions:

Deploy together?Are the resources normally created as one solution?
Change together?Are they updated or maintained by the same team?
Delete together?Should they be removed at the same time?
Control together?Do they need the same access, policy, tags, or locks?

A good resource group is not simply a folder. It is a management scope.

Example structures

A small lab can use one resource group for all resources in the lab:

Simple lab
rg-azfundamentals-lab Virtual network Virtual machine Network interface Managed disk

A company may separate production and development because they have different owners, access rules, budgets, or lifecycles:

rg-app-prod

Production application, production database, monitoring, and related network components.

rg-app-dev

Development application and test resources that can be changed or deleted independently.

There is no single naming model that works for every organization. The name should be clear, consistent, and useful to the people who operate the environment.

Resource group location

When you create a resource group, Azure asks for a region. This region stores the resource group’s metadata. It does not force every resource in the group to use the same region.

For example, a resource group can have metadata in West Europe and contain a resource deployed in North Europe. Always choose resource locations based on the requirements and supported regions of each service.

Access, policy, tags, and locks

A resource group is a scope where you can apply management controls:

  • Azure RBAC: assign access to the resource group and its resources.
  • Azure Policy: evaluate and enforce rules for resources in the group.
  • Tags: add information such as environment, owner, or cost center.
  • Locks: help protect resources from accidental deletion or modification.

Settings applied at the resource group scope can affect the resources below it. This is useful, but access should still follow the principle of least privilege.

Deleting a resource group

Deleting a resource group starts the deletion of the resources inside it. This makes resource groups useful for temporary labs, but it also makes the delete action important.

Before deletion:

  1. Confirm that the group is correct.
  2. Review all resources inside it.
  3. Check for locks, backups, dependencies, and important data.
  4. Confirm that no other system still uses those resources.

Practice this topic

The concept article stays short. Use these two practical labs when you want to create the resource group yourself.

Azure Portal

Create a resource group in the portal

Follow a clear portal workflow, check the result, and remove the lab safely.

Open portal lab
Terraform

Create a resource group with Terraform

Use a small reusable configuration, run the standard Terraform workflow, and download the code.

Open Terraform lab

Summary

A resource group organizes Azure resources that are managed together. The best grouping normally follows the lifecycle of the solution, not only its technical resource type.

Resource groups also provide a useful scope for access, policy, tags, locks, deployments, monitoring, and deletion.

Official documentation