as we mentioned before. Arm templates are Jason Files that described The resource is deporting nausea.
We also said that the management Porto uses actual resource manager to manage Resource is
let's see whether there is anything that we can find in the management Porto that can help us understand our templates.
Let's reach to the actual management Porto and quickly create a simple storage account.
So click on created resource is search for storage account
I will feel in the input that they require my subscription. I'll create a new resource group when, Let's say cyber very
and I will name my storage account Cyber very test str
west us to standard storage storage fee to and now make it just locally redundant. We don't need s o much redundancy going through the wizard very fast. No changes out. Couple of tax, let's say application
business all No, that's me.
He's in a cell, not email
tenant will be cyber very
and version 10
will review. And on this page you can see that you have a link toe down. What a template for automation.
Let's click on that link and see what we'll get.
So this is the arm template that is automatically generated by the port O. When you try to create a storage account,
I will *** well doesn't this template and I'll open it in a court editor so we can look at it a little bit more in details
when you download the template. That's part of the creation wizard. You get two files. One is the parameters Jason file. And this is a J sound file that contains all the inputs that we have selected as part of the Wizard.
As you can see, here we have a location west us that what we select it we have the storage account name, cyber retest str the count time the kind and the access tear
you can modify. This party matters. Jason file to put new values like, for example, if I don't wantto name my a storage account name sub cyber retest. But let's say Buddhism test S p r. I can modify the parameters file.
The other file that you get is the actual template. The template is very simple. In this case, we have just a couple of para matters which are actually the parameters that we hit in the parameters j some file as well as the resource that is created in this case. The resource is a storage account,
and those are the This is the information that is needed to create the resource.
As you can see, all the parameters are passed to the resource creation, the occasion, the access tear, the account name and some as well us, the tax, the tax are far called it for the storage account,
and you can see that the tax that we've put are already in the template
throughout. The rest of the videos will learn how we can modify these templates and make them more flexible. But for now, let's take a look where else arm templates are used
going back to the management portal.
So getting the album template for the new storage account that we're creating is great. But what about existing resources that we have already created in Azure?
The good news is that everything that we have created a national you can let the template for, so I'll go back. I have another resource group where I created a virtual machine
and some other resource is there So you have, ah, complete environment here. I can go and I can look at the templates
and I can export the template for the whole resource group. So you can see that when you export the template,
you get in for the template for everything that is created in this resource group the disks, the network, the public I, P and the virtual machines, any storage accounts, network interfaces and some.
This is a much bigger template that the one that we actually saw for the storage account.
And these template describes every resource that is deporting this resource group.
Well, that's nice again, but I may actually modify this resource group over time.
Let's say I deport the virtual machine first, and after that I decided to other storage account of this resource group. This is exactly what I did for here, and I have two deployments.
So I have the first deployment where I created the bone to virtual machine with all the resources that belonged to it.
So if I click on this deployment and select template, I can see all the resources that are deport us part of this deployment.
This is the virtual machine
on with all the required resource is for the virtual machine like diagnostic storage account like Public I. P address, virtual network, network, security group and network interface.
This template does not include the storage account that I deport later on. Tow this resource group.
I can download these template and use it as a starting point to develop just the template that the points of virtual machines.
If I go back to the deployments and if I click on the storage account deployment
and then template,
I will get the template on Lee for the storage account, which is almost the same that what I got from the deployment wizard for the storage account
this way you can see that, actually, each deployment that you create in the resource group has its own template, and you can not only
use those templates are starting point for such resources, But you can also track the deployments and what has changed in the resource group.
Let's say I would liketo delete the storage account. I will just go select the storage account and say delete.
Let's confirm that
and give it a minute to get deleted. Itwas pretty fast
now if I go back to the deployments,
I can use the storage account deployment to just really boy the storage account again with the same part of matters
as you can see. Arm templates are used extensively in azure, and they can help you make your work with actual much simpler. You can describe anything that you need deporting natural, and you can use it for different purposes.
Now let's go and look deeper into the arm template structure and develop our own template.