WEBVTT 00:00.800 --> 00:03.520 Let's move down the Azure resource hierarchy. 00:04.000 --> 00:07.280 Now we'll look at resource groups. As you already know, 00:07.780 --> 00:11.800 an Azure resource group is like a folder. It can contain one or more Azure 00:12.300 --> 00:16.199 resources, like an Azure SQL database, Kubernetes cluster, and so 00:16.699 --> 00:20.960 on. It is a boundary, like a management group or Azure subscription. 00:21.280 --> 00:25.200 You can use this to organize your resources and control access 00:25.700 --> 00:29.040 to them. Azure resource groups also contain deployments. 00:29.440 --> 00:32.880 So whenever you deploy anything into one, the deployment will stay 00:33.380 --> 00:36.760 there for a while and you can repeat the deployment and investigate 00:37.260 --> 00:41.160 it. A resource group has a geographical location, like West 00:41.660 --> 00:45.480 Us. It uses this to store things like deployments and metadata about 00:45.980 --> 00:50.000 the services that it contains. Interestingly, resources in the resource 00:50.500 --> 00:54.230 group can have a completely different location. They are not tied together. 00:54.870 --> 00:58.550 And like any other Azure resources, resource groups can 00:59.050 --> 01:02.390 have tags. These are key value pairs that you can use for things 01:02.890 --> 01:06.550 like cost management, for instance, a tag environment with the value 01:07.050 --> 01:10.230 dev. This is useful for organizing resources and 01:10.730 --> 01:14.350 keep them apart in reports. As a side note, you can move 01:14.850 --> 01:18.470 resources between resource groups. Also, resource groups 01:18.970 --> 01:22.550 are free. You don't pay for them. So let's see that in action. 01:23.110 --> 01:26.790 Here are my resource groups. They all belong to the same subscription. 01:27.270 --> 01:31.350 Let's create a new one. Okay, first, I'll give it a name 01:31.430 --> 01:34.550 like this. And it has a region location. 01:35.030 --> 01:38.390 So East US in this case. Okay, Next, 01:38.790 --> 01:42.390 tags. Like I said earlier, these are simple 01:42.890 --> 01:46.870 key value pairs. So for instance, environment and value 01:47.110 --> 01:50.550 production. Okay, cool. Let's move on and create 01:51.050 --> 01:54.430 the resource group. Okay, that's it. Here it is in 01:54.930 --> 01:58.150 the list. Let's take a look. All right, move this away. 01:58.630 --> 02:02.030 And okay, so this is the tag that we 02:02.530 --> 02:06.470 added. Environment production. This will help with reporting for 02:06.970 --> 02:10.390 cost management, for instance, and the location is East Us. 02:11.270 --> 02:14.710 Now let's create a service in the resource group. All right, 02:15.210 --> 02:18.670 here we go. And I'll search for a storage account. This one 02:19.170 --> 02:22.470 here. Let's go. All right, first pick the 02:22.970 --> 02:25.870 resource group, which is this new one. Okay. 02:26.350 --> 02:29.630 And now give this thing a name like this. 02:30.190 --> 02:33.630 And instead of east us, I'll pick something else here. 02:34.030 --> 02:37.190 All right, I'll leave the rest as it is, and then I'll 02:37.690 --> 02:40.110 create the storage account. I'll skip to when it is done. 02:40.880 --> 02:43.960 And here it is, the Azure storage account. As you 02:44.460 --> 02:47.880 can see, it is located in West Europe. And as this is a 02:48.380 --> 02:51.200 redundant one, it has a secondary region in North Europe. 02:51.680 --> 02:54.880 Okay, and here is its resource group. 02:55.280 --> 02:59.120 This is located in east us. So a different location. 02:59.440 --> 03:02.800 All right, here is another resource group. 03:02.880 --> 03:06.880 And let me show you something. Resource groups have deployments. 03:07.490 --> 03:10.650 These I only have one in here but usually there 03:11.150 --> 03:14.810 will be many in here. I can take a look at it. This one 03:15.310 --> 03:19.290 succeeded to deploy my service and I can drill down to see more details 03:19.790 --> 03:23.529 about the deployment. Okay. Also I can redeploy 03:24.029 --> 03:27.330 this service so repeat the deployment. Let's take a look. 03:27.810 --> 03:31.890 This is it. It has all these parameters that I can change like the 03:32.390 --> 03:35.800 name and location. This is actually an Azure Resource 03:36.300 --> 03:39.240 Manager template which defines a deployment in JSON. 03:39.400 --> 03:41.880 Like this. We'll talk about this more later. 03:42.680 --> 03:46.240 I want to show you one more thing about resource groups and that's 03:46.740 --> 03:49.880 locks. Here we are again. And here are locks. 03:50.360 --> 03:54.280 Every resource can have a lock on it including resource groups. 03:54.600 --> 03:58.280 Let's add one. A lock can be a read only lock 03:58.780 --> 04:02.190 or a delete lock. A read only lock makes the resource 04:02.690 --> 04:06.270 read only and a delete lock prevents it from being deleted. 04:06.750 --> 04:08.430 That can be very useful.