 The whole point of this is talk about Azure Image Builder in the Azure portal. But why are we in Visual Studio Code with some PowerShell open? There are some prereqs we need to run before deploying through the Azure portal. So we're going to go ahead and do that with some PowerShell. So you can see I have Visual Studio Code with the PowerShell extension enabled. You can also run this in Azure Cloud Shell. I'll link to the Learn document with all the commands below the video, which will show you how to do that as well. So in this video, I'll assume you have a working Azure subscription. PowerShell enabled locally and the easy command let's enable them. And first we need to connect to the subscription we want to work in. So I'm going to use the set easy context command and run that hitting F8. And now I'm in the proper subscription before you start registering the providers needed. Here are the necessary providers that we need for Azure Image Builder. And the reason these aren't enabled by default is really for security reasons. Why have something enabled if you're not using it? So this command is registering the providers we need. And then we'll define some variables so we aren't repeatedly typing in the same information. Here we're defining the image resource group, the location, the image template name, and so forth. So I'm going to go ahead and run these individually so you can see them. So image resource group name will be MyWinImageBuilderRG. We'll see that in the portal. Our region will be West US 2, but again, this could be a region you prefer. You can be more creative with your template name as well. And then the distribution properties of the managed image. And here this command is just again setting our subscription ID into a variable so we can use it. And the right output command showing that it's properly saved into that subscription ID variable and it's the correct one. So yeah, it's correct. Looks good to me. Now let's actually create a resource group now that we've saved our variables. So we're going to do new az resource group with our name and location. And there we go. Now it's time to create variables for the actual role definition and identity names. These values must be unique. So Microsoft put in this nice little timestamp and date. So it'll be a unique name no matter what. And this is to give it the proper permissions as well so the image build can finish without it. This just won't work. So here we'll highlight it and run it. And now create a user identity. And you can see it's being stored in the resource group. Now we're going to store the identity resource and principal IDs into variables. And here you can see we're downloading a JSON config file to assign permissions to the identity that we just created. So there's a URL from GitHub downloading the JSON file and there's our local path. But we're going to update it with our variables here. So we're going to replace subscription ID, the RG name and the image creation role. So I'm going to run all of it and everything completed. And now we're going to create the role definition with our JSON file here. Again, if you know JSON, you can go in and edit it more. But I'm sticking with the basics here. And finally, we grant the role definition to that actual VM image builder service principle. And this is the final step for everything to come into place. So we get a little warning there, but this will go ahead and run. Now you're done messing with PowerShell. You can go into the Azure portal and start creating images and creating an image gallery or you can continue on with PowerShell and create that gallery and the images that you'd like to set.