M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Azure resource group

Concept

A resource group is a logical container in Azure Resource Manager that holds related resources sharing the same lifecycle, permissions and policies; every Azure resource belongs to exactly one resource group.

✦ CONCEPTAzure resource groupM365.FM
Title graphic: Azure resource group (Concept)

Relationships

Azure resource group falls under the broader topic Microsoft Azure.

Description

An Azure resource group is a logical container in Azure Resource Manager that holds related resources of an Azure solution. Resources placed in the same group are meant to share the same lifecycle, permissions and policies. Every Azure resource belongs to exactly one resource group, which makes the group the basic unit for organizing and managing resources within Microsoft Azure.

The central design idea is the shared lifecycle. According to the Microsoft Learn documentation on Azure Resource Manager, resources in one group should be deployed, updated and deleted together. A resource with a different lifecycle belongs in a different group. This matters in practice because deleting a resource group deletes everything inside it, so the grouping decision directly determines what can be removed or redeployed as a single unit. Resources can be added to or removed from a group at any time, and they can be moved to another resource group or to another subscription.

Resource groups also act as a scope for governance. Access to a group can be restricted with Azure Policy, role-based access control or resource locks, which lets administrators apply permissions and rules once at the group level instead of resource by resource. Tags set on a resource group are not inherited by the resources it contains, so tagging has to be handled separately if resources need the same metadata. Resources in one group may also connect to resources that live in other groups, so a group is a management boundary rather than a network or isolation boundary.

A location must be chosen when a resource group is created. The group stores metadata about its resources, and control-plane requests are routed through that location, while data-plane access to the resources themselves is unaffected. If the group's region is unavailable, Azure Resource Manager redirects control-plane requests to a backup region. A resource group can hold only a limited number of instances per resource type, with some exceptions, which is a consideration when planning how many resources of the same kind go into one group.

Resource groups appear in deployment tooling as the typical target scope. The M365.FM episode "Bicep vs ARM Templates vs Terraform for Azure" discusses infrastructure-as-code options and notes that many users find Bicep modules simpler than linked templates for composing deployments within an Azure resource group or across subscriptions. In that context the resource group is the container into which a template or module deploys its resources.

The concept also shows up as a setup prerequisite for services connected to Microsoft 365. The episode "Automate Document Processing with Microsoft Syntex" lists the requirements for pay-as-you-go billing: an Azure subscription in the same tenant as the SharePoint environment, an Azure resource group set up within that subscription, SharePoint Administrator or Global Administrator permissions, and owner or contributor rights on the Azure subscription. Here the resource group serves as the container that ties the billed resources to the subscription before the service is activated from the SharePoint admin center.

In short, a resource group sits between the Azure subscription and the individual resources. Decisions about which resources share a group, which location it uses, and which policies, role assignments and locks apply at that level shape how a solution is deployed, secured and eventually retired.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept

Episodes about Azure resource group

Episodes in which Azure resource group is discussed:

Timeline of episodes about Azure resource group

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

Can an Azure resource belong to more than one resource group? (AI)

No. Each Azure resource lives in exactly one resource group. It can, however, be moved to another resource group or subscription, and it can connect to resources that sit in different groups.

What happens when an Azure resource group is deleted? (AI)

Deleting a resource group deletes all resources inside it. For this reason resources that share a lifecycle, meaning they are deployed, updated and deleted together, are grouped together.

Why does a resource group need a location? (AI)

The resource group stores metadata about its resources, and control-plane requests are routed through the chosen location. Data-plane access to the resources is not affected, and if the region is unavailable, Azure Resource Manager redirects control-plane requests to a backup region.

Related topics in brief

Topics linked to Azure resource group, each briefly explained:

All relationships of Azure resource group, grouped by type of relationship:

Broader topic

Broader topics of Azure resource group:

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Experts on related topics

Experts on topics related to Azure resource group, each with the topic that connects them:

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: