Azure Resource Groups

Question

I’m in the process of building a new network within Azure and using the Microsoft Azure migration tools to migrate on-prem servers and VMs on a legacy VMware server. I have created a single resource group that is currently only used by my Azure subscription. Is it ok to create all of my other Azure features like networking, firewall and VMs and continue to use the single resource group I have created for the Azure subscription? In watching many YouTube Azure example videos some create a new resource group for every Azure category thus ending up with many resource groups while others use a single for their setup. Is there a significant or necessary reason to not just use a single resource group?

Thanks for any input or suggestions.

Answer 1

This is fine (there is actually no limit on resources per resource group) but might not be the optimal approach. In general, you'd structure your resource groups to reflect your delegation model and resource lifecycle. In other words, if you want to delegate permissions to some of the resources (not all of them) to someone else, then it might make sense to create a resource group for it. Similarly, if some of the resources will be deleted earlier than others, you might want to create a resource group for them as well. Another potential reason is to organize resources in the manner that reflects their intended use. However, there are no hard rules regarding this - so ultimately it's your decision.

More at https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/overview#resource-groups

---

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin