From the course: Azure Essential Training for Developers

What is an Azure Resource Group? - Azure Tutorial

From the course: Azure Essential Training for Developers

Start my 1-month free trial

What is an Azure Resource Group?

“

- As you start developing applications on Azure, you may quickly find yourself needing to keep track of hundreds of resources. Luckily, Azure resources groups can come to your rescue. As your resource groups are logical groupings of related resources. Related resources can mean those that belong to a single application, resources that are shared within the same team or a number of any other groupings. Say you have an eCommerce platform that sells dessert T-shirts. Now imagine wanting to manage the Azure app service it runs on, the SQL server and database storing its data, and the Azure blob storage account hosting its media files, all in a single place. By putting them all in the same resource group, you can do just that. Or what if your networking team needed a consolidated and separated way to access your organization's application gateways, firewalls and virtual networks. And because we know each team wants ownership of their own resources, let's say your database administrators also required exclusive access to your organization's SQL server instances and databases. Setting up this kind of separation is simple with resource groups. That's the beauty of resource groups. You decide what those logical groupings are and what works for your team in applications. Besides organizing resources, one of the best things about resource groups is that you can handle them as a group. When resources are no longer needed, you can get rid of them all in one fell swoop. Need to update all of your dev environment resources? As long as they're within the same resource group, you can update them all in one go. One thing to be mindful of though, is that resource groups can't share a resource. Resources can only be assigned to a single resource group at a time. And it makes sense. I can't put these objects in two boxes at the same time. It's the same with resource groups. Restricting resources in this way preserves the integrity of the resource group and truly keeps it isolated from other groups. As we touched on earlier, resource groups are also a great way to manage your users access to resources. The role-based access control for example, you can grant access to specific resource groups or specific resources themselves. My team likes to separate resources by environment and application. And we control access to production with roles. With resource groups, you can similarly configure your team's access to fit your organization's policies. Finally, Azure resource groups also takes advantage of tagging, which can be a powerful way to work with resources. By tagging resource groups with meaningful context like environment, workload, or owner, you can make it easier to identify how you use your resources, separate cost by departments that incur them, and take advantage of automation opportunities when used with continuous integration and continuous deployment processes. No matter what kind of applications you build, resources you use, or strategy you implement to manage resources within your team, resource groups give you the flexibility to maintain them that makes sense to you.

Contents