Forum Discussion
Resource groups
Lets say if have different use cases lets say X resource group under subscription to support new group of users using VDI, then lets saw get new requirement to add user base maybe with different VDI requirments/budget . Is it best to just create a new resource group under same subscription and just tag the new resource group?
2 Replies
rigouts you have multiple option either you can create a new resources groups that way you can draw some logical boundary between the two VDI pools and also apply security policies or exception if needed as an example , Regular employees accessing set of VDI under one resources groups and maybe a contractors accessing AVD hosted in another resources groups that way you can define the security polcieis accordingly and say if the contractors project is over you can delete it whole resources groups but this will have a cost implication .
Tagging is always mandatory weather you use one or many resource groups now at which level you will apply you need to decide is it on VDI level or resource group level
Please "Accept as Answer" if it helped so it can help others in community looking for help on similar topics.
Resource groups are "folders" to store resources, same way you store all files for a project in a folder. Then with resource groups you can apply policies and some other features to all resources within the resource group.
When it comes to budget/cost management/cost followup I recommend you to use tags on your resources. You can then do cross-resource group cost analyze and management.
