The new Azure portal called Azure Resource Manager groups resources together. All services must be assigned to a resource group. Resource groups are used to manage the lifecycle of the services as a whole. Resource groups can also be used for isolation. Security, auditing, and tagging are used with resource groups to help manage the deployment.
- [Narrator] The best way to get started building your Azure deployment is to start with Azure resource groups. These groups are essentially containers that hold all the resources for a specific deployment. These resources could be virtual machines, networking, and storage. Every Azure resource must be assigned to an Azure resource group. For this reason I suggest creating your resource groups and then adding the virtual machines and networking and the storage to them. Azure resource groups are only available in the Azure resource manager portal.
In this demonstration I will show you how to create a resource group and some of the functionality available within the resource group itself. I'm now in the Azure portal. This is the new Azure resource manager portal, or ARM. You'll notice that I have a list here of resource groups that I've already created. I'm gonna show you how to create one. Very simply, click on Add. Go ahead and enter a name for it. Select the subscription that you're going to associate with this resource group and then the location.
Where would you like this resource group to essentially sit? I'm working on the West Coast today, so I will go ahead and pick the West US. I'm gonna go ahead and create it and you'll notice that it is now created. I'll go ahead and refresh this screen. And there is our resource group. As you can see, it is completely empty at this point. If I wanted to add a resource, I would go ahead and click Add. And let's say I wanna add in Server 2012. Go ahead and create. And I would fill out all the appropriate information for our Server 2012 deployment.
I have already mentioned that every resource must be associated to a resource group. When I create the resource from within the resource group, it is populated with the name of the resource group itself. Again, another reason why I like to create my resource groups first. It's just one less step later on. Looking at a empty resource group is a little bit boring, and it'll take some time to populate it with resources. I'm gonna go ahead and open a resource group that already has several resources already in it. I'm gonna go ahead and open the Office 365 demo resource group.
You will notice that this resource group has a variety of resources already in it. We have a couple of virtual machines, actually there's three of them here, we have some network interface cards, the network security settings, public IPs, there is our network and of course our storage. If I want to drill down into any of these any further I could easily do so by just clicking on it, and it would give me all the information about that specific resource. This one happens to virtual networks, we're gonna actually talk about that in another video.
Let's take a look at some of the settings associated with this resource group. Resource cost will help us estimate what the cost will be of a specific resource from within that resource group. In the case of my virtual machine, I can see that I'm spending about six dollars and 75 cents a month on it. And we can scroll down, you'll see a variety of costs associated with it. For a new deployment I would recommend that you actually monitor this to understand what those costs will be. Sometimes you have a deployment and you don't know what was in that deployment.
Here, within the deployments setting, you can actually see in this case, the templates, and when they were actually deployed to that resource group. Clicking into one will again provide some further detail about that particular, in this case, virtual machine and the deployment itself. See some information about the virtual machine, the storage account. I can see who created it. Within Azure, you can assign tags to specific resources. You would do this in order to track what a specific resource is doing.
In this case, if I wanted to track all of the components of my LyndaDemo, I could go ahead and do so. I've already created the key here for it. If I wanted to go ahead and create a new key, and then assign that key I can do so. To create a new key, go ahead and provide a name and then the value associated with it. Tags are what you create. Now that we have a few tags created I may want to associate one of those tags to let's say, my virtual machine and go into the settings of the virtual machine and into the tags and now I can go ahead and assign that tag to that virtual machine.
At a later date I can use that tag to pull all the associated resources with that tag. Sometimes we don't want anybody just into our resource group, be able to, let's say delete the resource group. In that case we can actually apply a lock to it. And then go ahead, click Add. And then what kind of lock do I want to associate with it? In this case I want a read-only. I do not want them to be able to delete anything so I can go ahead and add a lock. Now this resource group has a lock on it. And it cannot be deleted.
Before I can go ahead and add users to this resource group, the first thing I need to do is that remove that lock that I've already put in place. This lock will prevent me from adding new users because I put a lock type of read-only. I'm simply going to go ahead and delete that. Now I'll be able to add users as required. From within the users pane, go ahead and click Add. What role do you want this user to have? In my case, I'm going to select reader. And then I'm just going to add in the user.
And click OK. You will notice that Geoff now has the reader role assigned to him. Now that we've added some resources to our resource group, we can go through and look at the activity logs. I've gone ahead, clicked on activity logs and this brings up our Audit logs window. From here we can go ahead and apply specific filters. In this case all I've done is gone with the filters that were already provided for me and this will show me some of the activities within the last hour. If I wanted to drill a little bit deeper into here, I'd go ahead, click on it and it would show me the information, the time stamp, when this was created, what the resource group was that was assigned to.
Again, audit logs are fantastic for tracking what has happened. And finally, I wanna touch on automation scripts. I've already mentioned, this was a new feature that was added just recently. Within our resource group, we can go ahead and take all of the resources within that resource group and export them all to a template. If we wanted to go ahead and save that whole resource group we would go into automation scripts and all the parameters would be available to us for every resource within that resource group.
From here we can go ahead and save that template. Provide a description, and we can go ahead and save it. If we wanted to, after it was saved, we can go ahead and modify it to meet our new deployment needs. If I wanted to go ahead and deploy this again, I would just go ahead and click deploy. I can now edit the template and edit some of the parameters. I can also put it into a new resource group. Again choose the location and of course the never ending legal terms.
Once I hit changed the parameters as required I would click OK and now that entire template, all those resources that were in that single resource group are going to be recreated. Again, with the click of a button. As you can see, resource groups provide that first layer for our foundation, everything builds into our resource group from here.
- Understanding cloud technologies
- Why Azure?
- Creating virtual networks and storage
- Using Azure Active Directory for identity management and protection
- Disaster recovery with Azure Backup and Azure Site Recovery
- Working with virtual machines