Forum Discussion
Helper ITwo capacities in the same resource group
Rafaela07 Resource groups on Azure should follow your organizational policies on resource separation and naming conventions. Resource groups provide region affiliation, security context and a deployment scope. In many cases resource groups are used to separate production vs non production resources.
In enterprise-grade scenarios responsibilities of managing Azure and Fabric can be assigned to different groups, for example IT and Data Engineering. Fabric Capacity, while an Azure resource, still logically belong to Data Engineering domain but resource management should follow the Azure conventions.
The best practice of resource groups is to use different resource gorups for production and non-production resources, different regions, and different workloads. For example, a resource group that is reserved for non-production Fabric resources (capacities) is usually separate from a resource group for production Fabric resources.
An example of suggested approach for structuring resource groups can be found here Organize your Azure resources effectively - Cloud Adoption Framework | Microsoft Learn
If you find this answer useful or solving your problem please consider giving kudos and/or marking as a solution.
Super UserHi Rafaela07,
It can be created in the same resource group. The resource groups are a way for your org to organize azure resources, and control access. Given that the only access for fabric that is controlled from azure is the ability to pause/resume capacities, for fabric they are mainly for organization.
Rafaela07Hi tayloramy!
Thanks for your reply. Is there any reason why you should want separate rgs nevertheless? And is there a proposed approach by Microsoft?- apturlov
Rafaela07 Resource groups on Azure should follow your organizational policies on resource separation and naming conventions. Resource groups provide region affiliation, security context and a deployment scope. In many cases resource groups are used to separate production vs non production resources.
In enterprise-grade scenarios responsibilities of managing Azure and Fabric can be assigned to different groups, for example IT and Data Engineering. Fabric Capacity, while an Azure resource, still logically belong to Data Engineering domain but resource management should follow the Azure conventions.
The best practice of resource groups is to use different resource gorups for production and non-production resources, different regions, and different workloads. For example, a resource group that is reserved for non-production Fabric resources (capacities) is usually separate from a resource group for production Fabric resources.
An example of suggested approach for structuring resource groups can be found here Organize your Azure resources effectively - Cloud Adoption Framework | Microsoft Learn
If you find this answer useful or solving your problem please consider giving kudos and/or marking as a solution.