Return to Azure glossary, Azure security, Azure Resource Manager (ARM)

“There are some important factors to consider when defining your resource group:

• All the resources in your group should share the same lifecycle. You deploy, update, and delete them together. If one resource, such as a database server, needs to exist on a different deployment cycle it should be in another resource group.

• Each resource can only exist in one resource group.

• You can add or remove a resource to a resource group at any time.

• You can move a resource from one resource group to another group. For more information, see Move resources to new resource group or subscription - https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-move-resources

• An Azure resource group can contain Azure resources that reside in different Azure regions.

• A resource group can be used to scope Azure access control for administrative actions.

• A resource can interact with resources in other resource groups. This interaction is common when the two resources are related but don't share the same lifecycle (for example, web apps connecting to a database).

• When creating a resource group, you need to provide a location for that resource group. You may be wondering, “Why does a resource group need a location? And, if the resources can have different locations than the resource group, why does the resource group location matter at all?” The resource group stores metadata about the resources. Therefore, when you specify a location for the resource group, you're specifying where that metadata is stored. For compliance reasons, you may need to ensure that your data is stored in a particular region.

Fair Use Source: https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-overview#resource-groups

• Azure Resource Group