You could have come across multiple best practices articles related with Azure Resource Group. The recommendation could be “Keep separate resource group ” for different applications . At the same time there is a pop-up question could arise….How all the resource can be part of 2 resource group . For example Network Vnet how can be part of 2 resource group
The answer and concept is very simple . At any condition “same resource can not be part in multiple resource group” . But you can use the resource in other resource group without any restriction ex like Vnet .
While building your application resource group VM,storage accounts and other resources you can keep your new dedicated resource group.But network and security can be part of actual own group .
The following factors you need to know about Azure resource group:
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
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).