WEBVTT

0:00:02.640000 --> 0:00:07.680000
 In this video, we're going to take a look
 at basic Azure Resource Management.

0:00:07.680000 --> 0:00:10.140000
 The topics that we're going to cover,
 we're going to start out looking

0:00:10.140000 --> 0:00:15.480000
 at the overall resource hierarchy,
 how are resources organized within

0:00:15.480000 --> 0:00:17.520000
 the Azure environment.

0:00:17.520000 --> 0:00:20.560000
 Then we're going to take a look at a
 really important component of that,

0:00:20.560000 --> 0:00:22.240000
 which is resource groups.

0:00:22.240000 --> 0:00:26.860000
 Then we're going to get into looking at
 the hows and the whys of provisioning

0:00:26.860000 --> 0:00:32.140000
 resources or creating resources, and
 deprovisioning resources as well.

0:00:32.140000 --> 0:00:35.720000
 We'll round out this video with a quick
 demonstration through the Azure

0:00:35.720000 --> 0:00:42.860000
 portal of how you can really manage your
 resources at a basic level through

0:00:42.860000 --> 0:00:43.940000
 the Azure portal.

0:00:43.940000 --> 0:00:50.180000
 Let's get started by looking at the
 overall Azure Resource Hierarchy.

0:00:50.180000 --> 0:00:56.140000
 Within the Azure Resource Hierarchy,
 we start out with a box, which is

0:00:56.140000 --> 0:00:57.360000
 actually a subscription.

0:00:57.360000 --> 0:01:04.600000
 That's from a resource standpoint,
 the highest level that we have.

0:01:04.600000 --> 0:01:06.160000
 This idea of a subscription.

0:01:06.160000 --> 0:01:09.740000
 Now, external to the subscription, we're
 not going to focus on it much,

0:01:09.740000 --> 0:01:14.380000
 but I think it's important to understand
 is that we have also an Azure

0:01:14.380000 --> 0:01:22.800000
 AD tenant. Every subscription is associated
 with a tenant, and that tenant

0:01:22.800000 --> 0:01:29.360000
 has our users and
 other principles.

0:01:29.360000 --> 0:01:37.260000
 We have users, we have groups,
 we have service principles.

0:01:37.260000 --> 0:01:41.640000
 Not really key to what we're talking
 about directly, but I think it's

0:01:41.640000 --> 0:01:46.800000
 important to understand that it's there,
 that this is really how we define

0:01:46.800000 --> 0:01:52.260000
 a key component of the subscription,
 which is not only authorization,

0:01:52.260000 --> 0:01:54.620000
 are not only authentication,
 but also authorization.

0:01:54.620000 --> 0:01:58.260000
 That's all held within
 the Azure AD tenant.

0:01:58.260000 --> 0:02:01.060000
 But now let's get back to
 the subscription itself.

0:02:01.060000 --> 0:02:05.220000
 Now, within a subscription, you
 have a number of resources.

0:02:05.220000 --> 0:02:08.180000
 That's really what we
 call our services.

0:02:08.180000 --> 0:02:11.040000
 I can draw all these in.

0:02:11.040000 --> 0:02:19.980000
 Let's say I've got maybe an Azure SQL
 database, and maybe I also have

0:02:19.980000 --> 0:02:27.480000
 some storage. It almost fits.

0:02:27.480000 --> 0:02:31.760000
 Then also, let's say a virtual
 machine, just as an example.

0:02:31.760000 --> 0:02:37.760000
 Now, initially with the original version
 of Azure, which was now called

0:02:37.760000 --> 0:02:41.300000
 Azure Classic or the Azure Service
 Management Model, this was actually

0:02:41.300000 --> 0:02:46.800000
 what we had. We had a subscription,
 then we had all of our resources,

0:02:46.800000 --> 0:02:49.860000
 all of our services
 just kind of there.

0:02:49.860000 --> 0:02:53.560000
 Well, when they redesigned it a couple
 of years after Azure came out,

0:02:53.560000 --> 0:02:56.660000
 and it came up with what's called the
 Azure Resource Manager Model, which

0:02:56.660000 --> 0:02:59.980000
 is really what we have now,
 they added a layer.

0:02:59.980000 --> 0:03:03.700000
 That layer is the resource group.

0:03:03.700000 --> 0:03:17.580000
 Within your subscription, I've got these
 resource groups in which my resources

0:03:17.580000 --> 0:03:21.100000
 or services are actually
 organized.

0:03:21.100000 --> 0:03:22.740000
 That's really the hierarchy.

0:03:22.740000 --> 0:03:25.100000
 I've got the subscription
 within the subscription.

0:03:25.100000 --> 0:03:29.460000
 I've got resource groups and within the
 resource groups, I have resources.

0:03:29.460000 --> 0:03:34.040000
 It's kind of a one to many relationship
 if you're a database person, and

0:03:34.040000 --> 0:03:38.480000
 that each subscription can have multiple
 resource groups, but each resource

0:03:38.480000 --> 0:03:40.920000
 group belongs to exactly
 one subscription.

0:03:40.920000 --> 0:03:43.400000
 So I can't have a resource
 group across subscriptions.

0:03:43.400000 --> 0:03:49.020000
 Likewise, each resource group can have
 multiple resources, but each resource

0:03:49.020000 --> 0:03:52.220000
 is only within a single
 resource group.

0:03:52.220000 --> 0:03:56.000000
 So that's just kind of really architecturally
 the way it's managed.

0:03:56.000000 --> 0:03:59.100000
 Now, in other parts of courses, we'll
 talk about the interaction with

0:03:59.100000 --> 0:04:06.460000
 Azure AD, but in just the broadest sense,
 Azure AD is going to have rights.

0:04:06.460000 --> 0:04:08.460000
 Our principles in Azure AD
 are going to have rights.

0:04:08.460000 --> 0:04:12.440000
 Those can be at the subscription level,
 at the resource group level, or

0:04:12.440000 --> 0:04:14.680000
 at the individual resource level.

0:04:14.680000 --> 0:04:19.060000
 And of course, also, you have an inheritance,
 so that if I give you rights

0:04:19.060000 --> 0:04:22.360000
 at the subscription level, you have
 those rights throughout the entire

0:04:22.360000 --> 0:04:26.740000
 subscription, flowing down to all of the
 resources within that subscription.

0:04:26.740000 --> 0:04:29.260000
 So that's the basic hierarchy.

0:04:29.260000 --> 0:04:32.080000
 Now, what I want to do next is I'm
 going to shift over, and I want to

0:04:32.080000 --> 0:04:37.460000
 talk about resource groups, because
 resource groups administratively are

0:04:37.460000 --> 0:04:39.780000
 very important. Now, they're
 not the actual resource.

0:04:39.780000 --> 0:04:43.360000
 The resource group in and of itself is
 not going to give you any services,

0:04:43.360000 --> 0:04:48.340000
 but they allow you as an administrator
 to, well, administer your services.

0:04:48.340000 --> 0:04:49.440000
 So let's talk about these.

0:04:49.440000 --> 0:04:54.700000
 First of all, resource groups are the
 primary organizational unit in Azure.

0:04:54.700000 --> 0:04:59.540000
 They really are the only organizational
 unit, and you have hundreds or

0:04:59.540000 --> 0:05:04.060000
 thousands of resources, and they have
 this one layer of hierarchy, which

0:05:04.060000 --> 0:05:05.380000
 is a resource group.

0:05:05.380000 --> 0:05:07.640000
 Now, why do we have
 resource groups?

0:05:07.640000 --> 0:05:09.120000
 What purposes do they serve?

0:05:09.120000 --> 0:05:12.420000
 And probably, purpose may be a little
 bit better term than use case.

0:05:12.420000 --> 0:05:19.960000
 For me, the most important aspect of
 resource groups is authorization,

0:05:19.960000 --> 0:05:22.280000
 permissions, roles.

0:05:22.280000 --> 0:05:27.380000
 I've got a large enterprise organization,
 and I have a number of different

0:05:27.380000 --> 0:05:29.920000
 divisions that have
 resources in Azure.

0:05:29.920000 --> 0:05:33.580000
 Well, how am I going to delegate administration
 of those resources?

0:05:33.580000 --> 0:05:36.260000
 The easiest way to do that
 is through resource groups.

0:05:36.260000 --> 0:05:40.980000
 So maybe my network management group
 has administrative rights, maybe

0:05:40.980000 --> 0:05:47.120000
 ownership or another role on the networking
 resource group, whereas my

0:05:47.120000 --> 0:05:51.340000
 systems group maybe has the same administrative
 rights on the virtual

0:05:51.340000 --> 0:05:53.240000
 machine resource group.

0:05:53.240000 --> 0:05:55.660000
 Now, it doesn't mean I have to put
 all my virtual machines in the same

0:05:55.660000 --> 0:05:59.060000
 resource group. You don't have to do
 that at all, but it does give you

0:05:59.060000 --> 0:06:00.480000
 a way to break that up.

0:06:00.480000 --> 0:06:05.800000
 Other reasons for having resource groups,
 life cycle, and I will tell

0:06:05.800000 --> 0:06:08.640000
 you, as an instructor, I
 use this all of the time.

0:06:08.640000 --> 0:06:10.760000
 I'm setting up different
 scenarios.

0:06:10.760000 --> 0:06:13.080000
 I want to be able to set them up, and
 when I'm done with them, I want

0:06:13.080000 --> 0:06:15.780000
 to be able to easily make sure I delete
 everything, so I'm not getting

0:06:15.780000 --> 0:06:17.560000
 charged for things I'm not using.

0:06:17.560000 --> 0:06:22.820000
 And that's another very good
 use of resource groups.

0:06:22.820000 --> 0:06:26.700000
 Now, the third item that I have listed
 down here says resource management,

0:06:26.700000 --> 0:06:30.180000
 which seems kind of generic, but
 it's really pretty simple.

0:06:30.180000 --> 0:06:36.120000
 If you've got thousands of resources,
 let's say, very simple, let's say

0:06:36.120000 --> 0:06:39.040000
 you've got 10,000 different
 resources in Azure.

0:06:39.040000 --> 0:06:42.280000
 You don't want a flat management of
 those where you're scrolling through

0:06:42.280000 --> 0:06:44.560000
 10,000 different items.

0:06:44.560000 --> 0:06:48.280000
 If you broke that up, and let's say you
 had 100 resource groups, and each

0:06:48.280000 --> 0:06:52.240000
 one of those resource groups had 100
 resources, then it's just easier

0:06:52.240000 --> 0:06:54.880000
 to manage, and that's
 really all that is.

0:06:54.880000 --> 0:07:00.900000
 Another capability or another aspect
 of resource groups is for use in

0:07:00.900000 --> 0:07:05.680000
 billing. The billing API, the billing
 information that you see, has the

0:07:05.680000 --> 0:07:07.960000
 resource group associated with it.


0:07:07.960000 --> 0:07:13.240000
 Now, the billing itself in Azure happens
 at the subscription level, and

0:07:13.240000 --> 0:07:16.520000
 you can't break it down as far as
 the way you have to pay for it.

0:07:16.520000 --> 0:07:21.080000
 However, in terms of the way that's
 reported, you can break that out by

0:07:21.080000 --> 0:07:21.800000
 resource groups.

0:07:21.800000 --> 0:07:24.320000
 So you could, for example, have different
 resource groups associated with

0:07:24.320000 --> 0:07:25.660000
 different cost centers.

0:07:25.660000 --> 0:07:29.960000
 And so that's another key component,
 our key capability or use case of

0:07:29.960000 --> 0:07:30.940000
 resource groups.

0:07:30.940000 --> 0:07:34.800000
 Now, in addition to that, some
 big things on resources.

0:07:34.800000 --> 0:07:38.580000
 First of all, each resource belongs
 to exactly one resource groups, but

0:07:38.580000 --> 0:07:42.400000
 you can move resources between
 resource groups.

0:07:42.400000 --> 0:07:47.860000
 Generally speaking, you cannot move
 a resource between regions, but you

0:07:47.860000 --> 0:07:50.900000
 can move a resource between
 resource groups.

0:07:50.900000 --> 0:07:55.720000
 And related resources do not need
 to be in the same resource group.

0:07:55.720000 --> 0:08:01.340000
 So if I have a virtual machine, that virtual
 machine is on a virtual network,

0:08:01.340000 --> 0:08:04.320000
 the virtual network and the virtual machine
 do not need to be in the same

0:08:04.320000 --> 0:08:07.720000
 resource group. They can, for whatever
 reason, be in different resource

0:08:07.720000 --> 0:08:12.920000
 groups. And finally, as far as big picture
 resource groups, some resource

0:08:12.920000 --> 0:08:15.580000
 groups are managed by Microsoft.

0:08:15.580000 --> 0:08:19.700000
 And an example that I run into is
 the Azure Kubernetes Service.

0:08:19.700000 --> 0:08:24.240000
 When I provision an instance of the
 Azure Kubernetes Service behind the

0:08:24.240000 --> 0:08:29.360000
 scenes, but completely available to
 me, Azure generates a resource group

0:08:29.360000 --> 0:08:33.020000
 for all of the resources associated with
 that particular service, because

0:08:33.020000 --> 0:08:35.380000
 there are multiple
 resources for that.

0:08:35.380000 --> 0:08:38.500000
 And so resource groups are really just
 something they're there all the

0:08:38.500000 --> 0:08:40.020000
 time. They're not complex.

0:08:40.020000 --> 0:08:43.340000
 They serve a purpose, and I just
 want to make sure that was clear.

0:08:43.340000 --> 0:08:50.380000
 Now, let's move on to talking about
 the provisioning and deprovisioning

0:08:50.380000 --> 0:08:55.380000
 of resources. This is obviously
 the starting place.

0:08:55.380000 --> 0:08:57.660000
 When I talk about provisioning, that's
 just the word we typically use

0:08:57.660000 --> 0:09:00.120000
 for creating a resource in Azure.

0:09:00.120000 --> 0:09:06.080000
 And there are thousands of different
 resources that can be provisioned

0:09:06.080000 --> 0:09:10.960000
 within Azure. And there are different
 ways to go about provisioning.

0:09:10.960000 --> 0:09:17.260000
 The screenshot I have here is of the
 marketplace screen within the portal,

0:09:17.260000 --> 0:09:20.900000
 so that if I go to the portal, as you'll
 see in a few minutes, and click

0:09:20.900000 --> 0:09:23.460000
 new, this is what I would get.

0:09:23.460000 --> 0:09:28.960000
 Now, when you provision a resource, that
 provisioning process may be fairly

0:09:28.960000 --> 0:09:32.380000
 simple for something like, let's say,
 a route table, where there's about

0:09:32.380000 --> 0:09:35.900000
 four pieces of information, I need
 to define, or it could be something

0:09:35.900000 --> 0:09:40.360000
 much more complex, such as
 with a virtual machine.

0:09:40.360000 --> 0:09:43.340000
 And here with the virtual machine, you'll
 notice that there's actually,

0:09:43.340000 --> 0:09:49.180000
 and again, this is actually from the
 portal, there's a number of views

0:09:49.180000 --> 0:09:51.840000
 that I have to go through, a number
 of screens that I need to go through

0:09:51.840000 --> 0:09:55.360000
 to fully define my
 virtual machine.

0:09:55.360000 --> 0:09:57.780000
 And if you're going through the portal,
 it's really going to walk you

0:09:57.780000 --> 0:09:59.720000
 through that process.

0:09:59.720000 --> 0:10:03.500000
 Now, in addition to using the portal,
 there are other approaches that

0:10:03.500000 --> 0:10:06.260000
 we have for provisioning
 our resources.

0:10:06.260000 --> 0:10:12.940000
 What you see here is an example of Azure
 PowerShell, where I've got PowerShell

0:10:12.940000 --> 0:10:15.580000
 cmdlets, and these, by the
 way, are cross-platform.

0:10:15.580000 --> 0:10:19.620000
 I can install them on Windows, but
 I can also install them on Linux or

0:10:19.620000 --> 0:10:25.420000
 on Mac OS. And it allows me to define,
 in this case, a new Azure virtual

0:10:25.420000 --> 0:10:30.740000
 machine with a number of parameters, such
 as resource group name, location,

0:10:30.740000 --> 0:10:37.120000
 etc. Now, similar to that, you want
 to be able to deprovision, get rid

0:10:37.120000 --> 0:10:40.240000
 of resources. Why are you going
 to deprovision resources?

0:10:40.240000 --> 0:10:41.540000
 There are a few reasons.

0:10:41.540000 --> 0:10:45.900000
 First of all, many resources, you're
 paying for them as long as you have

0:10:45.900000 --> 0:10:50.520000
 them. So it makes sense to get rid of
 them once you no longer need them.

0:10:50.520000 --> 0:10:55.020000
 But also, in addition to that,
 it's clutter, right?

0:10:55.020000 --> 0:10:58.200000
 You're not using a virtual
 disk anymore.

0:10:58.200000 --> 0:10:59.860000
 You want to go ahead and get
 rid of that virtual disk.

0:10:59.860000 --> 0:11:04.440000
 Simple as that. Just good management
 and hygiene practices.

0:11:04.440000 --> 0:11:11.460000
 And it's relatively easy to deprovision
 or to remove these elements.

0:11:11.460000 --> 0:11:15.400000
 Now, another thing, though, that you
 want to be aware of, and this is

0:11:15.400000 --> 0:11:20.680000
 particularly important when it
 comes to virtual machines.

0:11:20.680000 --> 0:11:24.000000
 Because, first of all, most people
 end up having virtual machines that

0:11:24.000000 --> 0:11:28.720000
 they're running in Azure, and they tend
 to be a pretty big cost center.

0:11:28.720000 --> 0:11:32.680000
 I mentioned that many of the resources
 you have, you will pay as long

0:11:32.680000 --> 0:11:33.720000
 as you have them.

0:11:33.720000 --> 0:11:38.040000
 For example, if you have a virtual
 network gateway, you are paying for

0:11:38.040000 --> 0:11:40.440000
 that virtual network gateway
 as long as you have it.

0:11:40.440000 --> 0:11:42.580000
 Virtual machines are a
 little bit different.

0:11:42.580000 --> 0:11:46.400000
 If I've got a virtual machine and I'm
 not using it, but I am planning

0:11:46.400000 --> 0:11:49.940000
 on using it in the future, rather than
 deprovisioning it and completely

0:11:49.940000 --> 0:11:53.820000
 getting rid of it, I can just
 stop that virtual machine.

0:11:53.820000 --> 0:11:58.020000
 And what that will do is it will pause
 the actual runtime of the virtual

0:11:58.020000 --> 0:12:02.280000
 machine. It will deprovision any resources
 that have been provisioned,

0:12:02.280000 --> 0:12:03.740000
 but that virtual machine
 is still there.

0:12:03.740000 --> 0:12:05.420000
 It's ready to restart.

0:12:05.420000 --> 0:12:08.360000
 And that, by the way, is different
 than, say, shutting down a virtual

0:12:08.360000 --> 0:12:10.180000
 machine from within the
 operating system.

0:12:10.180000 --> 0:12:15.040000
 So if I go and I run a shutdown command
 within a Linux VM, or I go and

0:12:15.040000 --> 0:12:20.420000
 I shut down and went to a server VM,
 that's not stopping or deallocating

0:12:20.420000 --> 0:12:21.260000
 the virtual machine.

0:12:21.260000 --> 0:12:22.960000
 And those are just
 some terms there.

0:12:22.960000 --> 0:12:26.020000
 The term deallocate typically
 applies to virtual machines.

0:12:26.020000 --> 0:12:28.440000
 And that's when you're going to
 full stop that virtual machine.

0:12:28.440000 --> 0:12:32.720000
 You're not going to pay for it, but
 it still exists versus deprovision,

0:12:32.720000 --> 0:12:37.160000
 which means you're going to fully get
 rid of that particular resource.

0:12:37.160000 --> 0:12:43.260000
 Now, let's go ahead and let's take
 a quick look at the process and the

0:12:43.260000 --> 0:12:44.820000
 tools for managing resources.

0:12:44.820000 --> 0:12:49.380000
 I'm going to bring up the Azure portal
 and just go briefly through some

0:12:49.380000 --> 0:12:52.680000
 of the things I've already shown you,
 the process that you would use to

0:12:52.680000 --> 0:12:53.820000
 manage resources.

0:12:53.820000 --> 0:12:57.520000
 So let's go ahead
 and get into that.

0:12:57.520000 --> 0:13:03.880000
 Right now, I am logged
 into the Azure portal.

0:13:03.880000 --> 0:13:08.320000
 And I'm logged in with an account that's
 got all kinds of rights here,

0:13:08.320000 --> 0:13:11.980000
 more than I probably should have, but
 that's okay, more than I should

0:13:11.980000 --> 0:13:13.040000
 be trusted with.

0:13:13.040000 --> 0:13:17.100000
 In any case, what I'm going to do
 is go ahead and create a resource.

0:13:17.100000 --> 0:13:24.200000
 And what you see here is a window very similar
 to what I had in the screenshot,

0:13:24.200000 --> 0:13:25.960000
 in fact, pretty much the same.

0:13:25.960000 --> 0:13:30.860000
 And this looks fairly limited, but
 if I look down here, I can go into

0:13:30.860000 --> 0:13:31.880000
 these categories.

0:13:31.880000 --> 0:13:36.160000
 And these are just the featured
 instances of these categories.

0:13:36.160000 --> 0:13:42.300000
 And if I go see all, I get a
 much bigger set of options.

0:13:42.300000 --> 0:13:47.040000
 So just under compute, there are hundreds
 of different compute options

0:13:47.040000 --> 0:13:48.380000
 that are available.

0:13:48.380000 --> 0:13:51.040000
 So if you want to do something, there's
 a good chance you're going to

0:13:51.040000 --> 0:13:56.100000
 find it. I'm going to go ahead and just
 create an Ubuntu virtual machine.

0:13:56.100000 --> 0:13:57.520000
 Go ahead and hit create there.

0:13:57.520000 --> 0:13:59.580000
 And it's going to really walk
 me through the process.

0:13:59.580000 --> 0:14:01.900000
 Now, remember that hierarchy
 I talked about?

0:14:01.900000 --> 0:14:03.780000
 Subscription to resource
 group to resource.

0:14:03.780000 --> 0:14:07.960000
 Well, I'm creating a resource that resource
 group, that resource has to

0:14:07.960000 --> 0:14:12.300000
 be in a resource group, which is
 associated with a subscription.

0:14:12.300000 --> 0:14:17.340000
 And what I'm going to do is go ahead
 and create a new resource group.

0:14:17.340000 --> 0:14:25.900000
 It's 3509, say D1, a terrible
 naming convention.

0:14:25.900000 --> 0:14:28.420000
 All right, I have
 to give it a name.

0:14:28.420000 --> 0:14:33.000000
 I am terrible with naming things.

0:14:33.000000 --> 0:14:34.400000
 Give it a location.

0:14:34.400000 --> 0:14:39.840000
 Now, those are very standard subscription
 resource group virtual machine.

0:14:39.840000 --> 0:14:41.800000
 And for most resources,
 there's a region.

0:14:41.800000 --> 0:14:46.000000
 There's some resources, a few that
 don't have a region, but most every

0:14:46.000000 --> 0:14:50.120000
 resource that you would create would
 have or provision would have these

0:14:50.120000 --> 0:14:54.260000
 settings. For a resource or for a virtual
 machine resource, then I go

0:14:54.260000 --> 0:14:55.720000
 into things like availability
 options.

0:14:55.720000 --> 0:14:59.300000
 I'm just going to leave
 those image size.

0:14:59.300000 --> 0:15:01.640000
 In this case, keep it simple.

0:15:01.640000 --> 0:15:04.300000
 Let me use password
 based security.

0:15:04.300000 --> 0:15:07.000000
 So I don't feel like going
 and grabbing my key.

0:15:07.000000 --> 0:15:12.320000
 This word production,
 I would do key based.

0:15:12.320000 --> 0:15:16.580000
 And then I'm going to go through,
 I have options for the disks.

0:15:16.580000 --> 0:15:18.380000
 I'm going to leave those alone.

0:15:18.380000 --> 0:15:21.140000
 I'm going to have options in
 this case for the networking.

0:15:21.140000 --> 0:15:23.780000
 I'm going to actually
 leave those alone.

0:15:23.780000 --> 0:15:26.960000
 Leave management, leave advanced.

0:15:26.960000 --> 0:15:29.820000
 Don't set any tags.

0:15:29.820000 --> 0:15:32.800000
 And I get a review and create screen
 where it's going to let me define

0:15:32.800000 --> 0:15:36.100000
 this. It's going to tell me how much
 it's going to cost me, and then I

0:15:36.100000 --> 0:15:39.740000
 can create. And that's
 going to go.

0:15:39.740000 --> 0:15:42.720000
 And in a moment, it's going to start
 creating in the background, and I

0:15:42.720000 --> 0:15:45.380000
 get this deployment blade.

0:15:45.380000 --> 0:15:47.320000
 The blade, by the way,
 I'll use that term.

0:15:47.320000 --> 0:15:49.760000
 That is just a window
 within the portal.

0:15:49.760000 --> 0:15:55.720000
 I found out not too long ago that that term
 actually comes from Xbox terminology,

0:15:55.720000 --> 0:15:59.160000
 but there you go, a little bit of information
 that will do you nothing.

0:15:59.160000 --> 0:16:02.020000
 Now, I'm going to go and provision
 another resource while this one is

0:16:02.020000 --> 0:16:05.480000
 going. And this one's kind of be
 at the other end of the spectrum.

0:16:05.480000 --> 0:16:10.560000
 I'm going to create a route table,
 which I'm not going to use at all,

0:16:10.560000 --> 0:16:14.520000
 but it just is going to give you an
 example of provisioning a resource

0:16:14.520000 --> 0:16:16.800000
 that is much less complex.

0:16:16.800000 --> 0:16:20.720000
 And so here I've got a route table,
 and you can see that I have a much

0:16:20.720000 --> 0:16:27.280000
 simpler definition screen for this
 provisioning screen called demo RT.

0:16:27.280000 --> 0:16:32.520000
 Now in this case, I'm going to put
 it in an existing resource group.

0:16:32.520000 --> 0:16:37.320000
 Notice the location, and
 then I'm just created.

0:16:37.320000 --> 0:16:42.340000
 And this one will create a bit faster
 than the virtual machine.

0:16:42.340000 --> 0:16:46.660000
 Now, while I'm in the portal, a nice
 little useful thing over here.

0:16:46.660000 --> 0:16:49.900000
 I'm going to dismiss everything
 that's completed.

0:16:49.900000 --> 0:16:54.680000
 I can view the progress of my deployments,
 and I get all kinds of other

0:16:54.680000 --> 0:16:59.300000
 information. If I click over here, this
 is my deployment on my route table,

0:16:59.300000 --> 0:17:02.380000
 and I'm going to wait for that to finish,
 and then I'm going to pop in

0:17:02.380000 --> 0:17:08.260000
 and just show you what the
 result of this process is.

0:17:08.260000 --> 0:17:17.900000
 All right, my route table has fully
 deployed, so let's take a look at

0:17:17.900000 --> 0:17:24.280000
 that. Now I'm in the blade at this
 point for the route table, and I've

0:17:24.280000 --> 0:17:27.900000
 got most of the management
 capabilities.

0:17:27.900000 --> 0:17:32.860000
 I say most of the management capabilities,
 because there are some resources

0:17:32.860000 --> 0:17:37.120000
 that you are going to occasionally
 have to use a command line, because

0:17:37.120000 --> 0:17:42.140000
 for whatever reason, they haven't built
 a particular capability into the

0:17:42.140000 --> 0:17:46.040000
 portal. For most of your day to day,
 if you like working in the portal,

0:17:46.040000 --> 0:17:47.420000
 you will be able to do so.

0:17:47.420000 --> 0:17:50.400000
 But you want to be familiar with the
 command line as well, whether it's

0:17:50.400000 --> 0:17:55.840000
 PowerShell or the CLI, just to make
 sure that you can fully manage all

0:17:55.840000 --> 0:17:57.020000
 of your resources.

0:17:57.020000 --> 0:18:00.000000
 But if I wanted to go, for example,
 in this case and set up new routes,

0:18:00.000000 --> 0:18:03.340000
 I could go routes, click
 add and define a route.

0:18:03.340000 --> 0:18:07.380000
 I'm not going to do that now, because
 that's not the point of this exercise.

0:18:07.380000 --> 0:18:11.000000
 The other thing that I can
 do is I can deprovision.

0:18:11.000000 --> 0:18:17.040000
 Typically, in the portal, I have the
 individual delete here, and I can

0:18:17.040000 --> 0:18:21.820000
 simply just click delete, and that's
 going to prompt me, make sure that

0:18:21.820000 --> 0:18:26.100000
 I want to actually delete that, and then
 go about the process of deleting

0:18:26.100000 --> 0:18:34.320000
 that resource. I can also go in to my
 resource group, and I can view all

0:18:34.320000 --> 0:18:36.460000
 of the resources in
 that resource group.

0:18:36.460000 --> 0:18:41.780000
 So here is the resource group that I
 just provisioned, and I can see that

0:18:41.780000 --> 0:18:47.200000
 I've got a storage account, a virtual
 network, a virtual machine, a disk,

0:18:47.200000 --> 0:18:49.860000
 network interface, public IP,
 and network security group.

0:18:49.860000 --> 0:18:54.400000
 These are all of the resources that were
 provisioned when I said I wanted

0:18:54.400000 --> 0:18:57.300000
 to create or provision
 a virtual machine.

0:18:57.300000 --> 0:19:01.820000
 I can manage these, I can go into a
 virtual machine, and I get a more

0:19:01.820000 --> 0:19:06.200000
 complex, but similar concept for the
 blade for the virtual machine.

0:19:06.200000 --> 0:19:09.840000
 I have more things I can do with it, for
 example, stop it, restart, capture.

0:19:09.840000 --> 0:19:13.720000
 I can also delete it, and then you
 can see all of the other management

0:19:13.720000 --> 0:19:15.100000
 capabilities that I have.

0:19:15.100000 --> 0:19:18.840000
 And one thing I recommend that you do,
 while you're, particularly if you're

0:19:18.840000 --> 0:19:26.440000
 new to Azure, is go into the portal and
 just take a look at what's available

0:19:26.440000 --> 0:19:30.480000
 on these different blades, because
 it really gives you a good feel for

0:19:30.480000 --> 0:19:32.140000
 what you can do with
 different resources.

0:19:32.140000 --> 0:19:33.100000
 An easy way to find it.

0:19:33.100000 --> 0:19:36.300000
 Of course, you want to look at documentation,
 and hopefully I'll do a

0:19:36.300000 --> 0:19:39.700000
 good job of showing you the really important
 things, but always make sure

0:19:39.700000 --> 0:19:42.920000
 you get in there, you touch these blades,
 just click around and see what's

0:19:42.920000 --> 0:19:45.620000
 available. All right, just
 a couple more things here.

0:19:45.620000 --> 0:19:50.340000
 I'm going to go back to, oh, I'm in
 the resource group, and what I want

0:19:50.340000 --> 0:19:53.520000
 to do is I want to use a resource
 group to manage some resources.

0:19:53.520000 --> 0:19:56.760000
 So I'm going to just say, you know
 what, I'm going to select all these

0:19:56.760000 --> 0:20:01.640000
 resources, and then I'm going to delete
 all of these resources from within

0:20:01.640000 --> 0:20:02.660000
 the resource group.

0:20:02.660000 --> 0:20:06.600000
 Now, because I'm deleting multiple
 resources, it's going to ask me to

0:20:06.600000 --> 0:20:12.600000
 confirm, and I hit yes, and I've now
 undone all that good that I just

0:20:12.600000 --> 0:20:14.660000
 did by creating those resources.

0:20:14.660000 --> 0:20:18.720000
 And I can also, when I'm done with the
 resource group, I can delete the

0:20:18.720000 --> 0:20:21.300000
 actual resource group itself.

0:20:21.300000 --> 0:20:24.400000
 I can just go here and say, okay, I
 want to delete the resource group,

0:20:24.400000 --> 0:20:26.900000
 and when you delete the resource group,
 you actually have to type the

0:20:26.900000 --> 0:20:28.500000
 name of the resource group.

0:20:28.500000 --> 0:20:33.240000
 So I've gotten in the habit of deleting
 all the contents, and using the

0:20:33.240000 --> 0:20:36.680000
 same resource groups typically over and
 over, but this is a demonstration.

0:20:36.680000 --> 0:20:38.680000
 So I'll show you that very simple.


0:20:38.680000 --> 0:20:40.180000
 I go ahead and hit that now.

0:20:40.180000 --> 0:20:42.720000
 It's probably going to yell at me a
 little bit because I'm deleting the

0:20:42.720000 --> 0:20:45.880000
 resources within the resource group and
 deleting the resource group actually

0:20:45.880000 --> 0:20:47.960000
 should be okay. All right,
 but there you go.

0:20:47.960000 --> 0:20:52.600000
 Those are the basics of resources and
 resource management within the Azure

0:20:52.600000 --> 0:20:56.020000
 environment. Remember, you've got the
 subscription within the subscription,

0:20:56.020000 --> 0:20:58.740000
 you have resource groups, and within the
 resource groups, you have resources

0:20:58.740000 --> 0:21:01.440000
 that you in turn manage.