WEBVTT

0:00:02.840000 --> 0:00:08.120000
 Hi, in this video, I want to take a
 look at deploying virtual machines.

0:00:08.120000 --> 0:00:11.280000
 And the topics that we're going to cover
 will look, of course, first at

0:00:11.280000 --> 0:00:13.160000
 provisioning virtual machines.

0:00:13.160000 --> 0:00:15.360000
 What are the ways that we can
 provision virtual machines?

0:00:15.360000 --> 0:00:17.180000
 What are the things we
 need to think about?

0:00:17.180000 --> 0:00:20.740000
 Then, I want to take a look at
 updating virtual machines.

0:00:20.740000 --> 0:00:25.140000
 And specifically, as you update virtual
 machines, what updates are going

0:00:25.140000 --> 0:00:28.880000
 to allow you to do those live or hot,
 and which updates are going to require

0:00:28.880000 --> 0:00:35.240000
 either a reboot or a reallocation
 of your virtual machine.

0:00:35.240000 --> 0:00:38.640000
 And then, I want to just demonstrate
 a very simple deployment of a virtual

0:00:38.640000 --> 0:00:42.380000
 machine using the portal so you can
 kind of see the different elements

0:00:42.380000 --> 0:00:44.120000
 that are available.

0:00:44.120000 --> 0:00:49.360000
 Now, when provisioning a virtual machine,
 there's a number of platforms

0:00:49.360000 --> 0:00:52.600000
 that you can use to provision
 your virtual machine.

0:00:52.600000 --> 0:00:56.020000
 First of all, as in this demonstration
 I'm going to do, you can, of course,

0:00:56.020000 --> 0:01:00.840000
 use the portal. It's going to be the
 easiest for a one-off deployment.

0:01:00.840000 --> 0:01:04.240000
 Now, I will tell you for demonstration
 purposes, when I'm kind of looking

0:01:04.240000 --> 0:01:07.600000
 at the different elements of a virtual
 machine, I'll use the portal.

0:01:07.600000 --> 0:01:10.960000
 But anything that I'm doing that I
 would call real, I'm not using the

0:01:10.960000 --> 0:01:13.260000
 portal because I want
 it to be repeatable.

0:01:13.260000 --> 0:01:17.060000
 And particularly, as I get into more
 complex deployments, such as we cover

0:01:17.060000 --> 0:01:20.460000
 in other videos, then it's going to
 be a little bit challenging to try

0:01:20.460000 --> 0:01:22.940000
 and get that done or not possible to
 get that done through the portal.

0:01:22.940000 --> 0:01:26.560000
 It's great for very quick, dirty,
 one-off things, great.

0:01:26.560000 --> 0:01:30.100000
 If you're going to automate the process,
 you can, of course, do it through

0:01:30.100000 --> 0:01:34.760000
 the command line using either
 PowerShell or the Azure CLI.

0:01:34.760000 --> 0:01:38.940000
 And one thing to keep in mind, and
 I have this up here, really is just

0:01:38.940000 --> 0:01:40.280000
 kind of that generic reminder.

0:01:40.280000 --> 0:01:44.760000
 Everything you ever do in Azure, you're
 actually doing through a REST

0:01:44.760000 --> 0:01:48.240000
 API, right? Whether you're using the
 portal or PowerShell or the CLI,

0:01:48.240000 --> 0:01:53.420000
 and if you're using those, for the
 template, it's always going through

0:01:53.420000 --> 0:01:56.940000
 the API so you could write your own
 code or have your developers write

0:01:56.940000 --> 0:02:01.960000
 their own code to give you some kind
 of automated, customized provisioning

0:02:01.960000 --> 0:02:03.480000
 of virtual machines.

0:02:03.480000 --> 0:02:07.620000
 Now when you provision a virtual machine,
 there are certain resource dependencies,

0:02:07.620000 --> 0:02:11.660000
 right? First of all, you're going to
 have to have a virtual machine and

0:02:11.660000 --> 0:02:14.540000
 a subnet. And the reason you have to
 have the virtual machine and the

0:02:14.540000 --> 0:02:17.720000
 subnet is because those are
 requirements for the NIC.

0:02:17.720000 --> 0:02:24.040000
 Really the requirements for your virtual
 machine are a NIC and an OS disk.

0:02:24.040000 --> 0:02:28.380000
 And by the way, the OS disk is often
 created, often provisioned during

0:02:28.380000 --> 0:02:33.040000
 the provisioning process, but they are
 things that are separate from the

0:02:33.040000 --> 0:02:35.320000
 actual virtual machine
 resource itself.

0:02:35.320000 --> 0:02:38.560000
 Therefore we want to go ahead
 and call those out.

0:02:38.560000 --> 0:02:43.000000
 Now there are additional resources, additional,
 and anytime I say additional

0:02:43.000000 --> 0:02:46.540000
 resources, these are going to be things,
 for example, that show up in

0:02:46.540000 --> 0:02:48.260000
 a resource group.

0:02:48.260000 --> 0:02:51.600000
 Kind of, well the extensions do
 too, they're just hidden, right?

0:02:51.600000 --> 0:02:53.100000
 You have public IP addresses.

0:02:53.100000 --> 0:02:56.840000
 Now the public IP address is actually
 associated with the NIC, so it's

0:02:56.840000 --> 0:03:01.580000
 kind of indirect as a feature
 of a virtual machine.

0:03:01.580000 --> 0:03:06.000000
 You also can associate data disks
 with your virtual machine.

0:03:06.000000 --> 0:03:13.060000
 And finally, you can inject custom configuration
 into your virtual machine

0:03:13.060000 --> 0:03:19.400000
 live using extensions, such as a custom
 script or a desired state configuration

0:03:19.400000 --> 0:03:23.100000
 file, I hate saying that.

0:03:23.100000 --> 0:03:26.020000
 But any of those can be added
 through extensions.

0:03:26.020000 --> 0:03:29.400000
 And there are other videos that are
 covering those topics, so I'm not

0:03:29.400000 --> 0:03:33.300000
 going to drill too deep
 into those right now.

0:03:33.300000 --> 0:03:34.920000
 But then it's not
 too bad of a list.

0:03:34.920000 --> 0:03:38.980000
 Those are the things that you need
 when you're working with a virtual

0:03:38.980000 --> 0:03:43.340000
 machine. Now once you have your virtual
 machine, ideally when you provisioned

0:03:43.340000 --> 0:03:46.480000
 it, you were absolutely perfect, you
 did everything right, no changes

0:03:46.480000 --> 0:03:48.600000
 necessary, congratulations.

0:03:48.600000 --> 0:03:52.880000
 Realistically, over time and really
 even not necessarily because of any

0:03:52.880000 --> 0:03:56.380000
 mistake, you're storing more data,
 you need to change things.

0:03:56.380000 --> 0:03:58.860000
 You need to update your
 virtual machine.

0:03:58.860000 --> 0:04:01.420000
 Well, there's various updates you can
 make and what you want to think

0:04:01.420000 --> 0:04:04.740000
 about is, is that update going
 to be a live update?

0:04:04.740000 --> 0:04:07.340000
 So can I do this while the virtual
 machine stays online?

0:04:07.340000 --> 0:04:13.640000
 Or is this update going to require me
 to either reboot or to reallocate

0:04:13.640000 --> 0:04:14.420000
 the virtual machine?

0:04:14.420000 --> 0:04:17.140000
 I'll talk about that distinction
 in just a moment.

0:04:17.140000 --> 0:04:20.460000
 So what are our online updates?

0:04:20.460000 --> 0:04:25.340000
 There are some disk updates
 that can occur online.

0:04:25.340000 --> 0:04:29.520000
 I can add a disk to an existing
 virtual machine.

0:04:29.520000 --> 0:04:30.840000
 I can do that online, no problem.

0:04:30.840000 --> 0:04:35.680000
 I can also change the
 disk caching settings.

0:04:35.680000 --> 0:04:39.860000
 These are the disk caching settings
 within the Azure environment.

0:04:39.860000 --> 0:04:44.600000
 There's three settings, there's none,
 there's read and there's read right.

0:04:44.600000 --> 0:04:48.960000
 Depending on your workload, you
 may want to choose one of those.

0:04:48.960000 --> 0:04:56.620000
 You can also change the public or private
 IP settings of your NIC online.

0:04:56.620000 --> 0:05:01.220000
 Notice, that's got the little asterisk
 there with the absolute worst note

0:05:01.220000 --> 0:05:04.040000
 you can ever see sometimes.

0:05:04.040000 --> 0:05:07.320000
 Technically, the reason I have it that
 way is because technically, if

0:05:07.320000 --> 0:05:12.640000
 you look at the documentation, changing
 the public IP address may or may

0:05:12.640000 --> 0:05:15.460000
 not cause the virtual
 machine to reboot.

0:05:15.460000 --> 0:05:20.320000
 I have changed the public IP address
 settings multiple times and I have

0:05:20.320000 --> 0:05:22.140000
 yet to have that actually
 generate a reboot.

0:05:22.140000 --> 0:05:26.480000
 So I'll put the asterisks in there,
 personal anecdotal experiences, it's

0:05:26.480000 --> 0:05:29.680000
 not going to cause it, but it's also
 something, honestly, I would prepare

0:05:29.680000 --> 0:05:34.760000
 for and say, make the assumption that
 if you are making those changes,

0:05:34.760000 --> 0:05:38.580000
 that's something that you may consider as
 an offline, even though predominantly

0:05:38.580000 --> 0:05:39.960000
 I found it to be online.

0:05:39.960000 --> 0:05:42.600000
 Now what about the
 offline changes?

0:05:42.600000 --> 0:05:48.320000
 The first of our offline changes
 is resizing a virtual machine.

0:05:48.320000 --> 0:05:50.920000
 And here's the deal with that.

0:05:50.920000 --> 0:05:56.120000
 Resizing a virtual machine may require
 a simple reboot of the OS.

0:05:56.120000 --> 0:06:02.660000
 That's going to be a very
 low resource operation.

0:06:02.660000 --> 0:06:07.520000
 You're not giving up things like dynamic
 IP addresses, public or private.

0:06:07.520000 --> 0:06:11.960000
 You're not giving up your temp
 disk that has been allocated.

0:06:11.960000 --> 0:06:15.300000
 It's really just an OS reboot.

0:06:15.300000 --> 0:06:20.120000
 If it needs to be reallocated, what that
 means is it's going to be completely

0:06:20.120000 --> 0:06:25.600000
 deallocated and stopped from the standpoint
 of Azure and then completely

0:06:25.600000 --> 0:06:30.820000
 reallocated. So you could potentially
 lose your IP addresses, your temporary

0:06:30.820000 --> 0:06:33.320000
 disk will go away
 and be recreated.

0:06:33.320000 --> 0:06:34.700000
 And that's the allocation.

0:06:34.700000 --> 0:06:36.720000
 Now when would you need
 one or the other?

0:06:36.720000 --> 0:06:39.200000
 And the answer is, it's
 kind of hard to tell.

0:06:39.200000 --> 0:06:42.760000
 And it's kind of hard to tell because
 it depends on whether or not when

0:06:42.760000 --> 0:06:47.540000
 you repurvision to another size, that
 size is available in the current

0:06:47.540000 --> 0:06:52.040000
 Hyper-V cluster that is actually
 hosting your virtual machine.

0:06:52.040000 --> 0:06:55.580000
 Every Hyper-V cluster in the data center
 has a certain set of virtual

0:06:55.580000 --> 0:06:57.700000
 machines that it will support.

0:06:57.700000 --> 0:07:02.160000
 And if you're moving to a size that's
 supported on the same Hyper-V cluster,

0:07:02.160000 --> 0:07:04.180000
 it's just going to be a reboot.

0:07:04.180000 --> 0:07:08.260000
 If you're moving to a size that's not
 on the same cluster, then it's going

0:07:08.260000 --> 0:07:09.380000
 to be a reallocation.

0:07:09.380000 --> 0:07:15.660000
 Simple as that. Other things that are
 going to require an offline update,

0:07:15.660000 --> 0:07:21.620000
 disk changes that involve either resizing
 the disk or removing a disk.

0:07:21.620000 --> 0:07:26.540000
 Also with that wonderful asterisk, although
 this one's a little more well

0:07:26.540000 --> 0:07:30.400000
 defined, adding or removing a NIC.


0:07:30.400000 --> 0:07:34.880000
 Now here's the interesting
 way that this works.

0:07:34.880000 --> 0:07:41.080000
 There's two basic network architectures
 that are related to a virtual

0:07:41.080000 --> 0:07:45.840000
 machine. I can either have a single
 NIC virtual machine or I can have

0:07:45.840000 --> 0:07:47.300000
 a multiple NIC virtual machine.

0:07:47.300000 --> 0:07:51.720000
 Now it used to be that you had to define
 that when you initially provisioned

0:07:51.720000 --> 0:07:52.580000
 a virtual machine.

0:07:52.580000 --> 0:07:56.320000
 You cannot take a virtual machine that
 was a single NIC virtual machine

0:07:56.320000 --> 0:07:58.700000
 and make it a multi-nic.

0:07:58.700000 --> 0:08:00.440000
 However, you can do that now.

0:08:00.440000 --> 0:08:05.680000
 But if you switch from a single NIC
 to a multi-nic or from a multi-nic

0:08:05.680000 --> 0:08:11.040000
 to a single NIC, that's going to be an
 offline update and require actually

0:08:11.040000 --> 0:08:14.540000
 a deallocation reallocation.

0:08:14.540000 --> 0:08:20.340000
 If you're already a multi-nic VM, and
 remember some VMs can go up to eight

0:08:20.340000 --> 0:08:25.020000
 NICs, and if you add a NIC to an existing
 multi-nic VM, you should be

0:08:25.020000 --> 0:08:30.280000
 fine. But again, for me personally,
 even though there's that sometimes

0:08:30.280000 --> 0:08:33.800000
 for both of these, and in my case,
 changing public or private usually

0:08:33.800000 --> 0:08:39.520000
 is not an online update, I would, in
 all honesty, just make it easy, treat

0:08:39.520000 --> 0:08:41.520000
 both of those as offline updates.

0:08:41.520000 --> 0:08:44.920000
 So you would have to schedule maintenance
 to do those, or if they absolutely

0:08:44.920000 --> 0:08:49.900000
 need to be done, make sure that you would
 notify anybody of the possibility

0:08:49.900000 --> 0:08:54.800000
 of bringing down that machine at
 least for a short period of time.

0:08:54.800000 --> 0:08:58.800000
 So those are the different rules
 for updating virtual machines.

0:08:58.800000 --> 0:09:03.280000
 Now, let's have a little bit of fun,
 and let's get into a demonstration

0:09:03.280000 --> 0:09:05.480000
 of deploying a virtual machine.

0:09:05.480000 --> 0:09:09.920000
 And what I'm going to do is deploy a
 virtual machine from scratch using

0:09:09.920000 --> 0:09:13.060000
 the portal. And I'm just going to go
 through, walk through the steps in

0:09:13.060000 --> 0:09:17.620000
 the portal so you can get a feel for what
 you can do with virtual machines.

0:09:17.620000 --> 0:09:20.100000
 Again, in a production environment,
 I'm probably not using the portal,

0:09:20.100000 --> 0:09:23.080000
 but it's a great demonstration
 tool.

0:09:23.080000 --> 0:09:30.040000
 All right. I'm over
 in my Azure portal.

0:09:30.040000 --> 0:09:34.520000
 And what I'm going to do
 is create a resource.

0:09:34.520000 --> 0:09:40.580000
 And I'm going to create a Windows Server
 2016 data center, different videos.

0:09:40.580000 --> 0:09:43.720000
 I kind of randomly select
 which one of those I want.

0:09:43.720000 --> 0:09:46.540000
 And I am going to go
 through the process.

0:09:46.540000 --> 0:09:50.800000
 First, I need to define the resource
 group that this is going to go into.

0:09:50.800000 --> 0:09:55.320000
 And what I'm going to do here
 is simply going to say VM.

0:09:55.320000 --> 0:10:00.580000
 Provision. Demo.

0:10:00.580000 --> 0:10:03.180000
 That is my resource group.

0:10:03.180000 --> 0:10:07.760000
 I am going to give this.

0:10:07.760000 --> 0:10:13.580000
 A name we'll call it WinProveVM.

0:10:13.580000 --> 0:10:15.440000
 I'm going to put this in a region.


0:10:15.440000 --> 0:10:17.240000
 I always put everything
 in the E.S.

0:10:17.240000 --> 0:10:23.040000
 U.S. Image. I chose
 Windows Server 2016.

0:10:23.040000 --> 0:10:28.480000
 I can actually change this and go and
 pick any existing image, which is

0:10:28.480000 --> 0:10:32.140000
 kind of nice. And that includes, by
 the way, custom images that I have

0:10:32.140000 --> 0:10:34.920000
 developed. Next after
 image is size.

0:10:34.920000 --> 0:10:37.480000
 So you can see we're kind of going down
 through the settings that I was

0:10:37.480000 --> 0:10:40.040000
 talking about. I can go
 and change the size.

0:10:40.040000 --> 0:10:45.640000
 And I'm going to go do my kind of
 standard size here, my D2S V3.

0:10:45.640000 --> 0:10:48.200000
 It's a great general purpose
 size for demonstrations.

0:10:48.200000 --> 0:10:49.740000
 Not too expensive.

0:10:49.740000 --> 0:10:52.640000
 It gives me enough performance that I
 don't typically have to wait around

0:10:52.640000 --> 0:10:55.100000
 too much when doing demos.

0:10:55.100000 --> 0:10:59.140000
 All right. Now I have to give it, of
 course, some login information, some

0:10:59.140000 --> 0:11:00.880000
 admin information.

0:11:00.880000 --> 0:11:09.920000
 And then down here, I'm going to get really
 very basic settings for inbound

0:11:09.920000 --> 0:11:15.700000
 port rules. What this is going to do
 is to define a network security group

0:11:15.700000 --> 0:11:19.960000
 or an SG that's going to be
 associated with this VM.

0:11:19.960000 --> 0:11:23.400000
 Now the way this happens by default,
 if you're not going into a virtual

0:11:23.400000 --> 0:11:27.260000
 network that already has a network
 security group is it will create a

0:11:27.260000 --> 0:11:30.640000
 network security group and
 assign it to your NIC.

0:11:30.640000 --> 0:11:34.180000
 I generally prefer to have the network
 security groups assigned at the

0:11:34.180000 --> 0:11:38.780000
 subnet level. That's a networking concept
 outside of this video, outside

0:11:38.780000 --> 0:11:40.000000
 of this demonstration.

0:11:40.000000 --> 0:11:43.400000
 So I'm going to go ahead and
 just leave that as is.

0:11:43.400000 --> 0:11:46.880000
 The next setting is
 my disk settings.

0:11:46.880000 --> 0:11:48.360000
 First, my OS disk.

0:11:48.360000 --> 0:11:50.660000
 What type of OS disk?

0:11:50.660000 --> 0:11:54.260000
 Now standard, standard
 SSD and premium SSD.

0:11:54.260000 --> 0:11:57.840000
 These are available because
 of the VM size that I chose.

0:11:57.840000 --> 0:12:01.960000
 I chose a D2S V3.

0:12:01.960000 --> 0:12:06.100000
 Remember that S designation tells
 you that it is premium capable.

0:12:06.100000 --> 0:12:09.800000
 I'm in a location and I'm using a
 size that does not support ultra.

0:12:09.800000 --> 0:12:10.840000
 So that is not available.

0:12:10.840000 --> 0:12:18.600000
 I can if I want to add additional data
 disks right here and I have the

0:12:18.600000 --> 0:12:24.660000
 option of using managed disks
 or unmanaged disks.

0:12:24.660000 --> 0:12:27.880000
 Managed disks, your disk
 is a standalone resource.

0:12:27.880000 --> 0:12:30.820000
 You can go to a resource group
 and you will see your disk.

0:12:30.820000 --> 0:12:35.360000
 That is under almost every circumstance,
 the preferred approach.

0:12:35.360000 --> 0:12:39.840000
 You can see even to the extent that
 the choice is even hidden from you

0:12:39.840000 --> 0:12:44.900000
 here. Unmanaged disks, your OS disk,
 it's the same OS disk, but rather

0:12:44.900000 --> 0:12:49.140000
 than being a what I would call primary
 resource, it's actually stored

0:12:49.140000 --> 0:12:51.100000
 within a storage account.

0:12:51.100000 --> 0:12:54.860000
 There's some limitations there and it's
 why unless you have some compelling

0:12:54.860000 --> 0:12:59.140000
 reason to do so, you always want
 to go with a managed disk.

0:12:59.140000 --> 0:13:02.280000
 So we'll leave that next are
 my networking settings.

0:13:02.280000 --> 0:13:05.920000
 I'm going to need a virtual network
 and by default it's going to go and

0:13:05.920000 --> 0:13:10.180000
 create me a new virtual network or I
 could go and see if there were other

0:13:10.180000 --> 0:13:13.040000
 virtual networks that
 I wanted to create.

0:13:13.040000 --> 0:13:14.440000
 I could do that.

0:13:14.440000 --> 0:13:19.860000
 I've got a subnet that's being generated
 there for the virtual network,

0:13:19.860000 --> 0:13:25.480000
 a public IP. And again, all of these
 notice I can connect to an existing

0:13:25.480000 --> 0:13:27.840000
 public IP or I can just
 create my own here.

0:13:27.840000 --> 0:13:31.540000
 I have more settings for the
 network security group.

0:13:31.540000 --> 0:13:33.580000
 I'm going to leave that as basic.

0:13:33.580000 --> 0:13:37.660000
 That accelerated networking, that is
 actually our DMA and I don't have

0:13:37.660000 --> 0:13:39.500000
 a size that supports that.

0:13:39.500000 --> 0:13:45.100000
 I also have the option of setting up
 a load balance solution, which I

0:13:45.100000 --> 0:13:47.020000
 don't want or need to do.

0:13:47.020000 --> 0:13:49.800000
 I have a number of management
 settings.

0:13:49.800000 --> 0:13:54.780000
 For example, monitoring boot diagnostics,
 OS guest diagnostics.

0:13:54.780000 --> 0:14:01.340000
 Do I want a managed identity and do
 I want this to integrate with Azure

0:14:01.340000 --> 0:14:05.480000
 AD? My favorite one
 here, auto shutdown.

0:14:05.480000 --> 0:14:08.980000
 I used to use that all the time until
 I came up with an automation task

0:14:08.980000 --> 0:14:11.420000
 I run every night to make sure
 everything is shut down.

0:14:11.420000 --> 0:14:14.080000
 And then I can also configure backup
 right from here, but I'm not going

0:14:14.080000 --> 0:14:18.740000
 to do that. I have
 advanced settings.

0:14:18.740000 --> 0:14:22.680000
 I have extensions that I can deploy
 with the virtual machine.

0:14:22.680000 --> 0:14:25.860000
 So if I'm using, for example, a marketplace
 image and I've got a script

0:14:25.860000 --> 0:14:28.820000
 that's going to configure it the way
 I want, I can actually attach that

0:14:28.820000 --> 0:14:33.180000
 here. Cloud init only
 applies to Linux VMs.

0:14:33.180000 --> 0:14:39.900000
 You can have Azure dedicated hosts
 and placement groups with those.

0:14:39.900000 --> 0:14:44.440000
 And I can also select now
 a Gen 1 or Gen 2 VM.

0:14:44.440000 --> 0:14:47.120000
 Be careful right now at the
 time of this recording.

0:14:47.120000 --> 0:14:51.720000
 If you choose a Gen 2, so that
 would be a Hyper-V Gen 2.

0:14:51.720000 --> 0:14:56.720000
 For example, using VHDXs
 instead of VHDs.

0:14:56.720000 --> 0:14:59.340000
 But there's a lot of
 limitations to it.

0:14:59.340000 --> 0:15:04.060000
 So unless you have a really specific
 reason to go to Gen 2 right now at

0:15:04.060000 --> 0:15:06.660000
 the time of this recording, I
 don't recommend doing that.

0:15:06.660000 --> 0:15:08.160000
 The next is just tags.

0:15:08.160000 --> 0:15:09.760000
 So we'll skip over that.

0:15:09.760000 --> 0:15:12.820000
 We'll just go to review
 and create.

0:15:12.820000 --> 0:15:14.720000
 And it's going to
 check validation.

0:15:14.720000 --> 0:15:20.040000
 Of course, I'm going to carefully
 review everything and create.

0:15:20.040000 --> 0:15:22.500000
 Now that's going to take a few minutes
 to create when that's done.

0:15:22.500000 --> 0:15:26.160000
 We're going to come back and we're
 going to take a look at what we can

0:15:26.160000 --> 0:15:30.700000
 do, how we could update
 this virtual machine.

0:15:30.700000 --> 0:15:39.940000
 All right, this has successfully
 deployed.

0:15:39.940000 --> 0:15:44.160000
 And you can see they've got some recommendations
 there, which I'm going

0:15:44.160000 --> 0:15:45.900000
 to immediately ignore.

0:15:45.900000 --> 0:15:48.080000
 And go right to the
 resource itself.

0:15:48.080000 --> 0:15:54.680000
 This is the Azure Portal Blade, as
 it were, for my virtual machine.

0:15:54.680000 --> 0:16:02.600000
 And I can make some changes, including,
 I can go and make some networking

0:16:02.600000 --> 0:16:05.000000
 changes. This is actually
 really useful.

0:16:05.000000 --> 0:16:06.440000
 This is a, I say new.

0:16:06.440000 --> 0:16:08.900000
 It's probably been around for a year
 or two now, so it's not really that

0:16:08.900000 --> 0:16:12.480000
 new. But it wasn't originally
 part of this interface.

0:16:12.480000 --> 0:16:13.640000
 And it's really useful.

0:16:13.640000 --> 0:16:18.300000
 It gives you this nice snapshot of all
 of your networking that's associated

0:16:18.300000 --> 0:16:20.540000
 with this virtual machine.

0:16:20.540000 --> 0:16:22.280000
 And it gives you the ability
 to make changes.

0:16:22.280000 --> 0:16:27.880000
 For example, right now I've got, here's
 my rules, essentially my firewall

0:16:27.880000 --> 0:16:30.660000
 rules if you're not familiar
 with network security groups.

0:16:30.660000 --> 0:16:34.680000
 And let's say this is going
 to be a web server.

0:16:34.680000 --> 0:16:37.860000
 I go in here and just say, all right,
 I want to add a rule that's going

0:16:37.860000 --> 0:16:40.480000
 to allow port 80.

0:16:40.480000 --> 0:16:41.460000
 And just add that in.

0:16:41.460000 --> 0:16:45.320000
 And now I've got a change to that
 related network security group.

0:16:45.320000 --> 0:16:47.960000
 The network security group itself
 is a separate resource.

0:16:47.960000 --> 0:16:52.180000
 This just gives me a nice little interface
 for interacting with it.

0:16:52.180000 --> 0:16:55.860000
 And hopefully it's going to let me,
 there we go, move off of that.

0:16:55.860000 --> 0:16:57.480000
 Okay, disk management.

0:16:57.480000 --> 0:16:58.980000
 I can see my OS disk.

0:16:58.980000 --> 0:17:05.160000
 And if I wanted to go into the OS
 disk, I can make a few changes.

0:17:05.160000 --> 0:17:08.400000
 I believe, yeah, those
 are grayed out.

0:17:08.400000 --> 0:17:13.820000
 And they've changed things
 around somewhere in here.

0:17:13.820000 --> 0:17:20.580000
 I've got my, and they've
 now changed it.

0:17:20.580000 --> 0:17:27.300000
 Used to be able to very easily find the
 way to change the caching settings.

0:17:27.300000 --> 0:17:31.740000
 The great thing about demonstrating
 in Azure is that any given day it's

0:17:31.740000 --> 0:17:33.160000
 going to change on you.

0:17:33.160000 --> 0:17:34.800000
 All right, so there we go.

0:17:34.800000 --> 0:17:39.620000
 Those are some of the disk
 changes I can make.

0:17:39.620000 --> 0:17:42.140000
 I'm going to go back to
 that for just a moment.

0:17:42.140000 --> 0:17:48.560000
 I can actually add a data disk
 and create a new disk.

0:17:48.560000 --> 0:17:59.180000
 Disk name. Create this
 as a really small disk.

0:17:59.180000 --> 0:18:01.120000
 And one premium.

0:18:01.120000 --> 0:18:05.480000
 Standard SSD. And two gig.

0:18:05.480000 --> 0:18:08.660000
 It's fine. And create.

0:18:08.660000 --> 0:18:11.400000
 And that's going to create
 a managed disk.

0:18:11.400000 --> 0:18:15.600000
 And then allow me to associate that managed
 disk with my virtual machine.

0:18:15.600000 --> 0:18:16.720000
 That's going to take a moment.

0:18:16.720000 --> 0:18:25.900000
 Since that's done, we'll continue
 on with demonstration.

0:18:25.900000 --> 0:18:29.360000
 All right, so I have now
 added the data disk.

0:18:29.360000 --> 0:18:34.540000
 I will admit that during that sped up
 bit I actually hit the save so that

0:18:34.540000 --> 0:18:38.320000
 it did save that update, but
 I've got my data disk.

0:18:38.320000 --> 0:18:43.120000
 Oh, and also, I forgot, the caching I
 was talking about that you can change.

0:18:43.120000 --> 0:18:48.380000
 That's actually at the OS because that's
 an OS feature, not the actual

0:18:48.380000 --> 0:18:51.480000
 disk feature. You are
 not an OS of VM.

0:18:51.480000 --> 0:18:53.440000
 It's not an OS caching,
 it's VM caching.

0:18:53.440000 --> 0:18:56.120000
 See how many times I can give
 you the wrong information.

0:18:56.120000 --> 0:18:57.680000
 But I could change that.

0:18:57.680000 --> 0:19:00.320000
 I'm not going to go
 and discard it.

0:19:00.320000 --> 0:19:04.360000
 We now actually have an option of encrypting
 these disks through the portal,

0:19:04.360000 --> 0:19:07.200000
 which is nice. I'm not going to
 go through too many things.

0:19:07.200000 --> 0:19:09.240000
 You get the idea, you can
 go through all of these.

0:19:09.240000 --> 0:19:11.540000
 I do want to show you
 the size changes.

0:19:11.540000 --> 0:19:16.160000
 So right now, I'm on a D2S V3.

0:19:16.160000 --> 0:19:20.840000
 If I decide that I need more memory
 or more processor, I literally can

0:19:20.840000 --> 0:19:22.900000
 just go and resize.

0:19:22.900000 --> 0:19:29.420000
 One thing to be aware of, again, when you
 resize, it's going to be restarted.

0:19:29.420000 --> 0:19:34.060000
 If you stop the virtual machine, you
 might actually see additional sizes

0:19:34.060000 --> 0:19:37.920000
 are available. So that's going to be
 giving you the option to deallocate

0:19:37.920000 --> 0:19:45.880000
 and reallocate. That's
 pretty much it.

0:19:45.880000 --> 0:19:48.460000
 You can see the option for
 watching that happen.

0:19:48.460000 --> 0:19:49.340000
 Hopefully, you don't either.

0:19:49.340000 --> 0:19:50.700000
 Of course, you could always
 do it yourself.

0:19:50.700000 --> 0:19:52.360000
 That's it. That's provisioning.

0:19:52.360000 --> 0:19:54.480000
 And again, lots of ways
 you can provision.

0:19:54.480000 --> 0:19:57.200000
 Other videos will show other
 ways of provisioning.

0:19:57.200000 --> 0:20:03.400000
 But the core here, the settings are
 really pretty well illuminated going

0:20:03.400000 --> 0:20:04.520000
 through the portal to do so.