Resource group characteristics – Core Azure Architectural Components

Resource group characteristics

You should understand the following characteristics of resource groups:

  • Resources must belong in a resource group and can only exist in one resource group but can be moved between resource groups.
  • Resources can interact with other resources in the same resource group, other resource groups, and other subscriptions. Resources work at the data plane level, while resource groups and subscriptions work at the management plane level.
  • Resource groups don’t have to use the same region; they can contain resources from other regions.
  • Resource groups don’t contain subscriptions, but subscriptions contain resource groups.
  • Resource groups are not physical; they are a logical entity and not a billable item.
  • Resource groups contain metadata about the resources they include.
  • Resources inherit all permissions set at the resource group level they belong to by default.
  • When adding new resources to a resource group, they inherit those permissions and any access assignments.
  • When moving resources, they lose the permissions of the resource group they belonged to and inherit those of the new resource group they are moved to.
  • If access and permissions are assigned at the resource group level, all resources in that resource group can be managed.
  • Deleting a resource group will remove all resources within that resource group and not delete the subscription or tenant.
  • Because all resources are contained in the same resource group, it is easy to take action on all resources with a single activity; all resources within the resource group inherit the access assignments and policies set at the resource group.
  • When assigning tags to a resource group, the resources in that resource group do not inherit those tags; you would have to apply the tags individually to each resource in that group.

This section looked at the characteristics of resource groups. The following section looks at resource group logical organization.

About the author

Leave a Reply

Your email address will not be published. Required fields are marked *