Forum Discussion
Helper ITwo capacities in the same resource group
Hi everyone,
I would like your view on the following.
We have a resource group in azure where we have created an F16 fabric capacity. The respective workspace is used as a development environment.
Now we want to request a second infra/workspace running on F64 so that it can serve as production.
The question is, should a new resource group be created (under the same tenant) and the new f64 fabric capacity to be created there? Or the new one can be added in the existing rg? (for instance I was informed that if we were using databricks, creating a new rg for the new environment would be a oneway solution)
Are there specific best practices regarding that or relevant documentation?
Thank you in advance,
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.
6 Replies
- tayloramy
Super User
Hi 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.- 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.
- svenchio
Hei, Rafaela07 just cathing up on the latest issues on the community and your question caugth my attention, to being with I fully agree with apturlov amazing answer (kudos mate 😉), having prod vs non-prod environment isolated from each other, back in the day, due to limited resources it was thought to be Ok to have both on sharing, but nowadays, is just a BEST PRACTICE in every single moderm technology stack 😁
However, in your question, you mentioned this 👉 "(for instance I was informed that if we were using databricks, creating a new rg for the new environment would be a oneway solution)" i wonder 🤔what you mean by this? are you planning to have a shared azure databricks and you worry that workspace in different capacities won't be able to read? Just curious and perhaps we can give you some pointers ... looking forward and best of lucks.
KevinChantHey Rafaela07 , this really depends on how you want to manage the capacities in Azure (or how your company asks you to).
You can manage them both in the same Resource Group. However, if you need to follow any standards it may be the case that you need to split capacities into separate resource groups to represent the different environments.
Separate Resurce Groups for different environments can be better if you need to manage them collectively as far as permissions and automated tasks are concerned. In addition, it is an easier focus area if you need to purchase reserve capacity in the future.
I hope this helps.
v-aatheequeCommunity Support
Hi Rafaela07
Have you had a chance to look through the responses shared earlier? If anything is still unclear, we’ll be happy to provide additional support.
