Resource Group – ARM
Resource groups :
1. 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. Resource providers Template deployment
2. Each resource can only exist in one resource group.
3. You can add or remove a resource to a resource group at any time.
4. You can move a resource from one resource group to another group. For more information, see Move resources to new resource group or subscription.
5. A resource group can contain resources that reside in different regions.
6. A resource group can be used to scope access control for administrative actions.
7. 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.