 What should I put in my resource groups? This is a question I get a lot, and I like to think of resource groups as containing a logical service or application. But for a large application, maybe I want to break it up into tiers where I want to consider what region I'm deploying things into. Ultimately what I like to see for resource groups is something that I want to deploy in one unit because I can deploy my resource manager templates into into a resource group or things I want to be able to destroy and I can delete one resource group and all the resources inside are going to go away. I also like resource groups because they provide me one of the one of the scopes for billing. So if I want to see how much a particular component of my service is costing or even a whole unit, I can look at the cost from the resource group. So I like to think about resource groups as a nice logical construct for managing a particular application or a tier of an application. But for you, you're gonna have to figure that out for your service.