AZ-104: Microsoft Azure Administrator certification video training course by prepaway along with practice test questions and answers, study guide and exam dumps provides the ultimate training package to help you pass.

Azure Virtual Machines

5. *NEW* VM Custom Script Extension

Now, when we were creating our virtual machine, one of the options that we had was to have a script run after deployment. So if we go under creation under the advanced tab, there are two options here: one is a virtual machine extension, and the other is called Cloudinary, which is used for Linux. Why would you want a script to run after deployment?

Well, when you run a Windows image from the marketplace, all you're getting is an empty Windows server. Remember, when we created the machine and were in it, there were no programmes installed, only the default Windows ones, which was pretty useless to us as an organization. We need to have iOS installed. We need to copy our files, pull them from GitHub, put them in the right spot, configure iOS and reports, and all these wonderful things. So there is a deployment that needs to happen, and this is done using basically a virtual machine extension, and in Linux, it's done using the in it.

I'm going to answer a lot of this and go back to the VM that we created. So we'll go under settings, extensive, and we can see that we've already had a couple of extensions installed, the monitoring one eye diagnostics, and so on, and this is all around things that we did in the previous video, but with these are not instruments that we need. We need the PowerShell extension. So we say "add," and we scroll down here and see the custom script extension. Now this is a tool that will allow you to remotely execute PowerShell scripts onto an Azure VM, so we're going to say "create." Now we have to deploy the PowerShell file.

It will be downloaded into the VM and executed on the VM, and we can pass in optional arguments, so this would be when we're deploying it and how to do a setup. But this could also be some sort of regular maintenance. This can be set up as an automation job. Once this extension has been installed, it will basically run Power scripts, and so we're going to do this using a custom script extension.

We can set this as a more user-friendly way of doing a number of things remotely, including run PowerShell script, and we can even write a PowerShell script in the box and have it run on the virtual machine if we go down into operations and go under run command. So I can say PS version table PS version, and that would be like a type of script that we can then run. This isn't going to help us right now, but if we had the ability to download files from GitHub and copy files and stuff like that, this is one way we could basically instantiate a ready-to-use virtual machine.

6. *NEW* Azure Bastion Service

We've already seen that we can connect to this machine using RDP for Windows, SS for Linux, and a third option called Bastion. So let's go and set up a Bastion server. We're going to go under operation. And as you can see, Bastion is an operation. But in order to use a bin server, the server itself has to exist on its own subnet. And we let Azure create the subnet when we created this VM. So we're going to have to go into managed subnet conviction. And we can see that there's a single subnet.

Unfortunately, it consumes the entire address space. So the first thing I'm going to do is extend the virtual network by an additional 255 addresses. And then, when that's done, I'm going to create a subnet just for the Bastian server. So I'm going to go under subnet, and we're going to add a subnet. and it's suggesting Azure Bastion. Subnet. We can, I guess, name it whatever we want, but I'll accept that, and I don't know if we need to. It says it needs a minimum of a 27, so we'll reserve a 27 for it. We'll leave everything as is and press OK. As a result, it adds a second subnet to our virtual network. We can go back to the VM. Now we have a new name for the Bastion server. That's the subnet.

It's going to create a brand new public IP address. It's going to put it in an existing resource group. Now, I haven't really explained what Bastion actually is actually. Bastian is pretty cool. Basically, instead of RDPing directly into the box, hit the creative ones. Remotely connecting into an environment in an Asian environment is a more secure method. So you can set up pretty strict security settings to avoid having an open Rd port. You can basically turn off your RDP port, and people would then have to connect to the basic server in order to get into this virtual machine. So it is a much stronger and more secure way of allowing administrators and authorised administrators into your virtual machine.

And we can obviously create this as a Marketplace image, or we can go into this virtual machine and put it under Bastion, and now it's creating a brand new Bastian server for us. And so this is basically a better way of connecting to Azure. And so after that, we can see here that it's asking for the administrator, user ID, and password of the machine. and I'll do that. It does not require RDP or SSH, and it does not require a public IP address on the other virtual machine.

So basically, it's also money in terms of having a public IP address. So, if I click Connect, I should be able to see pop-ups and there shouldn't be a pop-up blocker. That is a Chrome thing, I guess. And now, basically, I'm connecting to the machine using a browser window. So how cool is that? This is a better way of making convertible machines. does not require RDP, SSH, or even a public IP address on that virtual.

7. *UPDATED* Virtual Machine Scale Sets (VMSS)

Now one of the great advantages to cloud computing, and Microsoft Azure specifically, is the ability to grow and shrink your resource usage depending on your actual needs. So if you have a website and you need to add a server during a peak period and then reduce it during a slow period, that is sort of the benefit of cloud computing over having your own web servers that you own in a hosted environment. But when you look at creating a virtual machine, and even if you could automate it, then you have to then create alerts and then have automation scripts that create new ones and add them to a load balancer. That's sort of a lot of work, and it's a pretty common task. So what Microsoft provides for the scaling of virtual machines is called a "virtual machine scale set." Go into the resource, create a resource, and we're going to start searching for scale set, and we can search for machine skill set, which is provided as a service.

Now, what this is is basically two or more virtual machines running behind a load bouncer, and that's provided to you in a single package. So if we hit create here, we can see the creation screen is a little bit more complicated than a single VM. We have health tabs, management tabs, and scaling tabs that we don't have in a regular VM. However, we must form a resource group. So I'll create a resource group. We give the entire scale set a name. So choose the region and put this back into the central US region, as I did before. We have the same options now. We don't have availability sets with scale sets. We'll talk about that in a second. But you do have the option of putting your VMs in specific data centres for availability zones. Again, this enhances your availability for a virtual machine scale set. Of course, you can choose any of the traditional default images, or, as we should say, you could create your own image.

If you have a machine that you can back up and use as an image, prepare it, flow it into Azure, and that becomes the image that you use to deploy a machine. We do have this low-priority option for Azure Spot instances. So if we want these machines to be running only on the low priority version, then we can do that; otherwise, we get the default VM size. We'll also leave that as the default. Just one; we talked about that in the VM section. We have to give those machines Now all machines will have the same user ID and password.

Remember using a Windows machine? So we get Windows set up here. We can also use our licences from hybrid benefits as the VM in terms of choosing the premium solid state disc as your operating system disc and maybe having a network disc added. It's going to create a brand new virtual network. We can create a load balancer. So if we want this virtual machine scale set to be part of an existing load balancing solution, We just add that to a load balancer, but it does have its own load balancer.

So we go next into the Scalision, and this is basically a load balancer that we can create with the VM SS. And look, we get the initial instance count of two in this case of two. So we're going to create two virtual machines, and we can have the manual policy, which means we can just go in and manually add a machine. Or we can have a built-in seat that will have one to ten machines. Or in this case, I'm going to do one to five machines based on a CPU hold, and it's going to be above 75% CPU utilization. It's going to add one virtual machine, and if the CP utilisation is low or lower, it's going to reduce one virtual machine.

We want to collect diagnostic logs. We talked about diagnostics, and if we were to put this into availability zones, how do we want to handle the availability zones? And so we can have a specific deal again, dealing with availability. Now again, this is similar to the wegot Security Center, we've got operating system things. I can turn off the diagnostics. The other thing about load balancers in particular is that you can actually monitor their health aspect. As a result, you can ping an HTTP end point. So this is the root domain of port 80 on each of the servers, and that will then tell you whether the server is working or not. Because you don't want your health probe to be like pinging the database and all, we could have a specific health HTML page that will tax the resources of your server.

Maybe you do, but sometimes people just have a simple HTML page being served up by the website. This is a recent addition; this automatic repair One of the more recent additions to Azure is the ability for machines to delete and reinstate virtual machines that are no longer operational. So the ability to delete those unhealthy instances means that in the past, it would simply kick it off the load balancer and leave it, but it would not serve traffic well. You can now have misbehaving instances automatically reinstated. We can skip through the advanced tab, which has some specific VM things. So by default, there's a limit of 150 in a single virtual machine scale set. So you could not have a 101-instance scale set. You can enable this, and what it uses is called a placement group.

So, essentially, it will divide 100 instance scale sets into different groups, allowing you to reach 1000 MSS. There's also how your VMs are going to be spread out among different centres if you're using availability zones. Remember, in the creation of the VMs, both an extension and a cloud are included. Now, as mentioned in the VMs, the placement group actually brings resources closer together. It's almost the opposite of availability. And you might want that if these VMs need to talk to each other and you're not concerned with uptime. So we're going to skip over this and the tags we talked about. So with this Create button, I'm now creating a load bouncer with two running VMs that will automatically scale between one and five VMs depending on CPU utilization. And again, I have enabled a VM extension. We could have deployed certain code.

We could use images that already have everything that we need. And so this is sort of the case if you've got the need for multiple virtual machines running on a load balancer to scale up and down. One option you have is to have Azure take care of that for you using a virtual machine scale set. Now, it's not mandatory because you could create your own VMs, your own bouncer, and your own automation scripting to grow and shrink the size of your load-balanced VMs yourself. But this is also provided for you at no additional cost, unlike the charges that the virtual machine makes for the VMs that you use. And there's no additional cost for using this routine; just use it on your own.

8. Create a VM in PowerShell

So now that we have PowerShell installed, the AZ module installed, and we've connected to Azure, let's go ahead and create a virtual machine. In the past, with the old Azure RM module, it was a bit more difficult. You have to do a lot of different commands to create a virtual machine. Microsoft has remedied this, and the new AZ module makes it a lot simpler. Now the first thing we need to do is create ourselves a resource group. Now, I find resource groups helpful because they allow you to delete resources.

So if a bunch of things get created in a resource group, once you're done with them, you can just delete the resource group, and it deletes all of the associated resources. You'll find as you go into PowerShell that the commands are kind of predictable. I mean, there's always a verb followed by a hyphen, followed by the z, followed by the service name or the resource name. As a result, the New AZ Resource Group was formed. If I wanted to delete it, it would be deleted as a resource group. I would type "get resource group" to get a list of all resources. So let's go ahead and create a new AZ resource group. Now it's time to name it, dashname, and I'm going to call this Azschd's new RG Tap. It has to be unique on my account for this region, and I will hopefully have that done before I have to choose a location. The location is the region.

So I'm going to put this in the East US region, hit Enter, and this will go and create the resource group. We can see that it says "successful" here. If we did go into the Azure Portal, we would see an empty resource group with this name in it. Now we want to create the virtual machine. The command for creating a virtual machine is AZ VM. very easy to remember in this instance. Now the good thing about this is that it used to take many different commands to create a virtual machine, and now we can just give it the settings just like we do in the portal, and Azure will go off and create those resources. So, what is the resource group's name? We just created the new AZ SGD RG Test Resource. So let's go ahead and use that one. Now we must give the VM a name, Dashname, and this is known as Azed SJD new VM location.

Let's put the virtual machine and all of its resources in one location. As the resource group, we have to provide the virtual network. Now, if we had an existing one, we could specify it. In this case, we don't. So we're going to give it a new name, and it'll create a new virtual network for me. Now, under the subnet, I'm happy with the default subnet name and the network security group. So if I hit the tab key, it automatically fills it. So a security group name And this is the new NSG and the public IP address.

So if we want this to have a public IP address and that IP address, a name, my IP address, and finally, which we want to get into this now, by default, you want none of them, but maybe you want 80 for the web server and 3389, which is the RDP port. Okay, we want four, four, three as well for the other web server. So 3389. So with this new AVM command, we're giving it all of the parameters just like we're going through the wizard. And when we hit Enter, it should go off and create this virtual machine.

Now, these are going to be the administrator credentials. Remember, when we create a virtual machine, we have to give it a user ID and password. And so I'm going to give it the user ID. Thankfully, it still hides the path for me. And so I'm going to hit enter. So this is how we're going to use RDP to get access to the virtual machine using these credentials. Here, we are showing us 8%. We're going to let that run. We'll come back to it. So that was it. Basically, when I created a new virtual machine within Azure, it came back with this status to say that it worked. So let's head over to the Azure Portal and just see that it's there.

So this is cool. The new AZ SJD VM is indeed running in that resource group and has an IP address. We can see that it ran successfully ran. Okay, from now on, we could RDP into the machine. We ensure that the port number is open, download the RDP file, and connect right into it. But I just wanted to demonstrate to you that using PowerShell, it's relatively easy nowadays to create a virtual machine in one single command with a resource group. In one single command, we've got a virtual machine. Now, you'll notice that we didn't enter the instance type.

We didn't add any additional discs or tags. There are a lot of things we left out here, but Azure just went ahead and took the default size. So if we go back to the portal, we can see that it is a DS One machine, a very small machine. And if we wanted something, we could have specified a different instance type. We also didn't specify the operating system. It shows this as Windows Server 2016. But if you need to use PowerShell to create a VM, look how simple it is. It could be fairly simple.

Prepaway's AZ-104: Microsoft Azure Administrator video training course for passing certification exams is the only solution which you need.