{"id":97444,"date":"2024-09-19T15:44:43","date_gmt":"2024-09-19T10:14:43","guid":{"rendered":"https:\/\/www.whizlabs.com\/blog\/?p=97444"},"modified":"2024-09-20T16:03:24","modified_gmt":"2024-09-20T10:33:24","slug":"optimizing-azure-deployments-arm-templates","status":"publish","type":"post","link":"https:\/\/www.whizlabs.com\/blog\/optimizing-azure-deployments-arm-templates\/","title":{"rendered":"Optimizing Azure Deployments Using ARM Templates"},"content":{"rendered":"

In this blog post, we will look into <\/span>Optimizing Azure Deployments Using ARM Templates<\/b> and understand how to deploy an ARM template using Azure CLI. We will explore a live scenario to give you hands-on experience in deploying resources in Azure, helping you grasp the practical aspects of optimizing and automating your deployments efficiently.<\/span><\/p>\n

ARM templates are design documents created in JSON file format and are used in the Azure Resource Manager to outline how the resources in Azure will be structured and used. Therefore, these templates allow resources to be deployed and maintained in a repeatable manner with assurance of exactly what state will be deployed based on the infrastructure designed.<\/span><\/p>\n

For those preparing for the <\/span>Microsoft Azure Administrator AZ-104 Course<\/b><\/a>, becoming proficient in ARM templates is essential. This certification course covers a wide range of Azure administrative tasks, including deploying and managing Azure resources.\u00a0<\/span><\/p>\n

Advantages of the ARM Templates<\/span><\/h3>\n

Infrastructure as Code (IaC):<\/strong><\/p>\n

ARM Templates allow the users to create a blueprint of their structure and manage it on the Azure Cloud environment in the form of code. This way, features such as versioning ability, testing, or even collaboration can be facilitated making sure that the structure is more reliable and consistent.<\/span><\/p>\n

Repeatability and Consistency:<\/strong><\/p>\n

However, with the use of ARM Templates, the same environment with the same configuration if required can be deployed any number of times thus decreasing the chances of human error and other flawless chances in the deployments.<\/span><\/p>\n

Easier Administration:<\/strong><\/p>\n

The deployment of resources is synchronized through ARM Templates making it possible for the infrastructure to be monitored, updated, or managed as a whole. This majorly cuts down the complications associated with large-scale deployments.<\/span><\/p>\n

Managing Dependencies:<\/strong><\/p>\n

In particular, ARM Templates are capable of installing resources in a focused order as defined by the dependencies for the resources. This guarantees that all the resources are rolled out in the correct order without any manual planning.<\/span><\/p>\n

Collaboration with CI\/CD Pipelines<\/strong>:\u00a0<\/span><\/p>\n

It is possible to include ARM templates in the course of building <\/span>Continuous Integration\/Continuous Deployment (CI\/CD)<\/span><\/a> lifecycle processes. This means that whenever there are changes to the necessary infrastructure in the cloud platform, automating those changes can be done.<\/span><\/p>\n

Scalability<\/strong>:\u00a0<\/span><\/p>\n

At the same time, it is relatively easy to deploy an ARM Template for a complex architecture with many resources; over time, one can easily run more ARM Templates around that baseline.<\/span><\/p>\n

Structure of an ARM Template\u00a0<\/b><\/p>\n

The file of the ARM Templates contains several pairings of richly detailed key-value sets in the form of JSON. For instance, below, you can see a format of ARM Templates\u00a0<\/span><\/p>\n

{ \u201c$schema\u201d: \u201c<\/span>https:\/\/schema.management.azure.com\/schemas\/2024-09-03\/deploymentTemplate.json#\u201d<\/span>, \u201ccontent version\u201d: \u201c1.0.0\u201d, \u201cparameters\u201d:{}, \u201cvariables\u201d: {}, \u201cfunctions\u201d:[], \u201cresources\u201d: [], \u201coutputs\u201d:{} } <\/span><\/pre>\n
1. Schema:<\/strong>\u00a0<\/span><\/p>\n
The schema defines from where the schema information of the template is taken and this is used in template validation.\u00a0<\/span><\/p>\n
 2. <\/span>Content Version:<\/span><\/strong><\/p>\n
The content version specifies the version of the template. Tracking changes and ensuring consistency across various versions of the template becomes much easier with this approach.<\/span><\/p>\n
3. Parameters:<\/strong><\/span><\/p>\n
This section allows you to define the inputs that can be provided at deployment time. This makes the template more flexible and reusable across different environments. Below is an example of parameters that allow users to specify the type of storage account they want to deploy in Azure.<\/span><\/p>\n
{<\/span>\r\n\"parameters\": {<\/span>\r\n\"storageAccountType\": {<\/span>\r\n\"type\": \"string\",<\/span>\r\n\"defaultValue\": \"Standard_LRS\",<\/span>\r\n\"allowed values\": [<\/span>\r\n\"Standard_LRS\",<\/span>\r\n\"Standard_GRS\",<\/span>\r\n\"Standard_RAGRS\",<\/span>\r\n\"Premium_LRS\"<\/span>\r\n],<\/span>\r\n\"metadata\": {<\/span>\r\n\"description\": \"Storage Account type\"<\/span>\r\n}<\/span>\r\n}<\/span>\r\n}<\/span>\r\n}<\/span><\/pre>\n
4. Variables:<\/strong><\/span>
\nThe variables section defines values that can be reused throughout the template. Unlike parameters, these are calculated within the template and cannot be provided during deployment.<\/span><\/p>\n
{<\/span>\r\n\"variables\": {<\/span>\r\n\"storageAccountName\": \"[concat('storage', uniqueString(resourceGroup().id))]\"<\/span>\r\n}<\/span>\r\n}<\/span><\/pre>\n
5. Functions:<\/strong><\/span><\/p>\n
In a template, the function contains the steps and procedures to be followed. It is just like a variable that defines the steps performed when called in templates. The below example of the function defines the unique name for the resources.<\/span><\/p>\n
6. Resources:<\/strong><\/span><\/p>\n
The resources section is the most critical part of the ARM Template. It defines the Azure resources to be deployed, including their properties, configurations, and dependencies.<\/span><\/p>\n
{<\/span>\r\n\u00a0\"resources\": [<\/span>\r\n{<\/span>\r\n\"type\": \"Microsoft.Storage\/storageAccounts\",<\/span>\r\n\"apiVersion\": \"2024-09-03\",<\/span>\r\n\u00a0\"name\": \"[variables('storageAccountName')]\",<\/span>\r\n\u00a0\"location\": \"[resourceGroup().location]\",<\/span>\r\n\u00a0\"sku\": {<\/span>\r\n\u00a0\"name\": \"[parameters('storageAccountType')]\"<\/span>\r\n\u00a0},<\/span>\r\n\"kind\": \"StorageV2\",<\/span>\r\n\"properties\": {}<\/span>\r\n}<\/span>\r\n]<\/span>\r\n}<\/span><\/pre>\n
1. Outputs:<\/strong><\/span><\/p>\n
The outputs section is used for value returns once the deployment is complete. This may feature the resource IDs, Connection strings or useful information as post-deployment operations.<\/span><\/p>\n
{<\/span>\r\n\u201coutputs\u201d: {<\/span>\r\n\u201cstorageAccountConnectionString\u201d: {<\/span>\r\n\u00a0\u201ctype\u201d: \u201cstring,\u201d<\/span>\r\n\u00a0\u201cvalue\u201d: \u201c[listKeys(resourceId(Microsoft.Storage\/storageAccounts\u2019, variables(\u2018storageAccountName\u2019), \u20182024-09-03\u2019) \u2018.keys[0].value]\u201d<\/span>\r\n\u00a0}<\/span>\r\nCopy<\/span>\r\n}<\/span>\r\n}<\/span><\/pre>\n
Azure Quickstart templates<\/b><\/p>\n
It is a repository of pre-created Azure resource manager arm templates available from Microsoft. The purpose of these templates is to ease the deployment of the said infrastructure of any applications on azure.<\/span><\/p>\n
Deployment of ARM Templates using Azure CLI<\/b><\/p>\n
\"whizlabs-webiste-login\"<\/p>\n
Click on the Training Library panel, select Cloud Computing, Microsoft Azure, and Microsoft Azure Exam AZ-104 Course.<\/span><\/p>\n
\"whizlabs-training-library-platform\"<\/span><\/p>\n
You will be redirected into AZ-104 Azure Administrator Associate Course. Select the Hands-on lab button to be taken into Hands-on Lab Page.<\/span>
\n<\/span><\/p>\n
\"<\/p>\n
Once the Hands on lab page opens, scroll down further to select \u2018Automate deployment of resources by using templates\u2019. Click on the \u2018Create a Windows VM using an ARM Template Start button to begin the lab.<\/span>
\n<\/span><\/p>\n
\"windows-vm-arm-template\"<\/p>\n
Once you click the Start button, you will be redirected to the lab page. Click on \u2018Start Guided Lab\u2019 to begin the lab.<\/span>
\n<\/span><\/p>\n
\"create-vm-windows-arm-template\"<\/p>\n
To start the lab, we must\u00a0 enable the button by participating in Whizlabs Training. Agree to the Whizlabs Term of User and click \u2018Start lab\u2019.<\/span><\/p>\n
\"windows-vm-arm-template-lab-confirmation\"<\/p>\n
The lab will begin with Whizlabs User\u2019s Credentials, including Username and password. We provide lab steps along the screenshots to be followed in the Azure Portal. Click on the \u2018Open Console\u2019 Button which will redirect you to the Azure Portal.<\/span><\/p>\n

\n<\/span>\"create-windows-vm-arm-template-lab\"<\/p>\n
Please give the Username and Password provided by Whizlabs on the Sign-in In Page.<\/span>
\n<\/span><\/p>\n
\"<\/p>\n
\"<\/p>\n
 <\/p>\n
\"Azure-services\"<\/h3>\n
Creation of an ARM Template\u00a0<\/span><\/h3>\n
To create a Windows Virtual Machine, you will need an ARM Template with A Windows Virtual Machine (VM). There follows an ARM Template, which uses a Windows Virtual Machine, public IPv4 address, virtual network, and subnet along with a network interface. A network security group (NSG) to enable Remote Desktop Protocol (RDP) connections.Diagnostics storage requirements. Template. The text file has to be saved as template.json.<\/span><\/p>\n
{<\/span>\r\n\u00a0\u00a0\"$schema\": \"https:\/\/schema.management.azure.com\/schemas\/2019-04-01\/deploymentTemplate.json#\",<\/span>\r\n\"contentVersion\":\"1.0.0.0\",<\/span>\r\n\u00a0\"metadata\": {<\/span>\r\n\"_generator\": {<\/span>\r\n\"name\": \"bicep\",<\/span>\r\n\"version\": \"0.8.9.13224\",<\/span>\r\n\"templateHash\":\"15495738823141086515\"<\/span>\r\n}<\/span>\r\n},<\/span>\r\n\"parameters\": {<\/span>\r\n\"adminUsername\": {<\/span>\r\n\"type\": \"string\",<\/span>\r\n\"metadata\": {<\/span>\r\n\"description\": \"Username for the Virtual Machine.\"<\/span>\r\n}<\/span>\r\n},<\/span>\r\n\"adminPassword\":{<\/span>\r\n\"type\":\"secureString\",<\/span>\r\n\"minLength\": 12,<\/span>\r\n\"metadata\": {<\/span>\r\n\"description\":\"Password for the Virtual Machine.\"<\/span>\r\n}<\/span>\r\n},<\/span>\r\n\"dnsLabelPrefix\": {<\/span>\r\n\u00a0\"type\": \"string\",<\/span>\r\n\"defaultValue\": \"[toLower(format('{0}-{1}', parameters('vmName'), uniqueString(resourceGroup().id, parameters('vmName'))))]\",<\/span>\r\n\"metadata\": {<\/span>\r\n\"description\": \"Unique DNS Name for the Public IP used to access the Virtual Machine.\"<\/span>\r\n}<\/span>\r\n},<\/span>\r\n\"publicIpName\": {<\/span>\r\n\"type\": \"string\",<\/span>\r\n\"defaultValue\": \"myPublicIP\",<\/span>\r\n\"metadata\": {<\/span>\r\n\"description\": \"Name for the Public IP used to access the Virtual Machine.\"<\/span>\r\n}<\/span>\r\n},<\/span>\r\n\"publicIPAllocationMethod\": {<\/span>\r\n\"type\": \"string\",<\/span>\r\n\"defaultValue\": \"Dynamic\",<\/span>\r\n\"allowedValues\": [<\/span>\r\n\"Dynamic\",<\/span>\r\n\"Static\"<\/span>\r\n],<\/span>\r\n\"metadata\": {<\/span>\r\n\"description\": \"Allocation method for the Public IP used to access the Virtual Machine.\"<\/span>\r\n}<\/span>\r\n},<\/span>\r\n\"publicIpSku\": {<\/span>\r\n\"type\": \"string\",<\/span>\r\n\"defaultValue\": \"Basic\",<\/span>\r\n\"allowedValues\": [<\/span>\r\n\"Basic\",<\/span>\r\n\"Standard\"<\/span>\r\n],<\/span>\r\n\"metadata\": {<\/span>\r\n\"description\": \"SKU for the Public IP used to access the Virtual Machine.\"<\/span>\r\n}<\/span>\r\n},<\/span>\r\n\"OSVersion\": {<\/span>\r\n\u00a0\"type\": \"string\",<\/span>\r\n\"defaultValue\": \"2022-datacenter-azure-edition-core\",<\/span>\r\n\"allowedValues\": [<\/span>\r\n\"2008-R2-SP1\",<\/span>\r\n\"2008-R2-SP1-smalldisk\",<\/span>\r\n\"2012-Datacenter\",<\/span>\r\n\"2012-datacenter-gensecond\",<\/span>\r\n\"2012-Datacenter-smalldisk\",<\/span>\r\n\"2012-datacenter-smalldisk-g2\",<\/span>\r\n\"2012-Datacenter-zhcn\",<\/span>\r\n\"2012-datacenter-zhcn-g2\",<\/span>\r\n\"2012-R2-Datacenter\",<\/span>\r\n\"2012-r2-datacenter-gensecond\",<\/span>\r\n\"2012-R2-Datacenter-smalldisk\",<\/span>\r\n\"2012-r2-datacenter-smalldisk-g2\",<\/span>\r\n\"2012-R2-Datacenter-zhcn\",<\/span>\r\n\"2012-r2-datacenter-zhcn-g2\",<\/span>\r\n\"2016-Datacenter\",<\/span>\r\n\"2016-datacenter-gensecond\",<\/span>\r\n\"2016-datacenter-gs\",<\/span>\r\n\"2016-Datacenter-Server-Core\",<\/span>\r\n\"2016-datacenter-server-core-g2\",<\/span>\r\n\"2016-Datacenter-Server-Core-smalldisk\",<\/span>\r\n\"2016-datacenter-server-core-smalldisk-g2\",<\/span>\r\n\"2016-Datacenter-smalldisk\",<\/span>\r\n\"2016-datacenter-smalldisk-g2\",<\/span>\r\n\"2016-Datacenter-with-Containers\",<\/span>\r\n\"2016-datacenter-with-containers-g2\",<\/span>\r\n\"2016-datacenter-with-containers-gs\",<\/span>\r\n\"2016-Datacenter-zhcn\",<\/span>\r\n=\"2016-datacenter-zhcn-g2\",<\/span>\r\n\"2019-Datacenter\",<\/span>\r\n\"2019-Datacenter-Core\",<\/span>\r\n\"2019-datacenter-core-g2\",<\/span>\r\n\"2019-Datacenter-Core-smalldisk\",<\/span>\r\n\"2019-datacenter-core-smalldisk-g2\",<\/span>\r\n\"2019-Datacenter-Core-with-Containers\",<\/span>\r\n\"2019-datacenter-core-with-containers-g2\",<\/span>\r\n\"2019-Datacenter-Core-with-Containers-smalldisk\",<\/span>\r\n\"2019-datacenter-core-with-containers-smalldisk-g2\",<\/span>\r\n\"2019-datacenter-gs\",<\/span>\r\n\"2019-Datacenter-smalldisk\",<\/span>\r\n\"2019-datacenter-smalldisk-g2\",<\/span>\r\n\"2019-Datacenter-with-Containers\",<\/span>\r\n\"2019-datacenter-with-containers-g2\",<\/span>\r\n\"2019-datacenter-with-containers-gs\",<\/span>\r\n\"2019-Datacenter-with-Containers-smalldisk\",<\/span>\r\n\"2019-datacenter-with-containers-smalldisk-g2\",<\/span>\r\n\"2019-Datacenter-zhcn\",<\/span>\r\n\u00a0\"2019-datacenter-zhcn-g2\",<\/span>\r\n\"2022-datacenter\",<\/span>\r\n\"2022-datacenter-azure-edition\",<\/span>\r\n\"2022-datacenter-azure-edition-core\",<\/span>\r\n\"2022-datacenter-azure-edition-core-smalldisk\",<\/span>\r\n\"2022-datacenter-azure-edition-smalldisk\",<\/span>\r\n\"2022-datacenter-core\",<\/span>\r\n\"2022-datacenter-core-g2\",<\/span>\r\n\"2022-datacenter-core-smalldisk\",<\/span>\r\n\"2022-datacenter-core-smalldisk-g2\",<\/span>\r\n\"2022-datacenter-g2\",<\/span>\r\n\"2022-datacenter-smalldisk\",<\/span>\r\n\"2022-datacenter-smalldisk-g2\"<\/span>\r\n],<\/span>\r\n\"metadata\": {<\/span>\r\n\"description\": \"The Windows version for the VM. This will pick a fully patched image of this given Windows version.\"<\/span>\r\n}<\/span>\r\n,<\/span>\r\n\"vmSize\":{<\/span>\r\n\"type\":\"string\",<\/span>\r\n\"defaultValue\": \"standard_b2s\",<\/span>\r\n\"metadata\":{<\/span>\r\n\"description\":\"Size of the virtual machine.\"<\/span>\r\n}<\/span>\r\n},<\/span>\r\n\"location\": {<\/span>\r\n\"type\": \"string\",<\/span>\r\n\"defaultValue\": \"[resourceGroup().location]\",<\/span>\r\n\"metadata\": {<\/span>\r\n\"description\": \"Location for all resources.\"<\/span>\r\n}<\/span>\r\n},<\/span>\r\n\"vmName\": {<\/span>\r\n\"type\": \"string\",<\/span>\r\n\"defaultValue\": \"simple-vm\",<\/span>\r\n\"metadata\": {<\/span>\r\n\"description\": \"Name of the virtual machine.\"<\/span>\r\n}<\/span>\r\n}<\/span>\r\n},<\/span>\r\n\"variables\": {<\/span>\r\n\"storageAccountName\": \"[format('bootdiags{0}', uniqueString(resourceGroup().id))]\",<\/span>\r\n\"nicName\": \"myVMNic\",<\/span>\r\n\"addressPrefix\": \"10.0.0.0\/16\",<\/span>\r\n\"subnetName\": \"Subnet\",<\/span>\r\n\"subnetPrefix\": \"10.0.0.0\/24\",<\/span>\r\n\"virtualNetworkName\": \"MyVNET\",<\/span>\r\n\"networkSecurityGroupName\": \"default-NSG\"<\/span>\r\n},<\/span>\r\n\"resources\": [<\/span>\r\n{<\/span>\r\n\"type\": \"Microsoft.Storage\/storageAccounts\",<\/span>\r\n\"apiVersion\": \"2021-04-01\",<\/span>\r\n\"name\": \"[variables('storageAccountName')]\",<\/span>\r\n\"location\": \"[parameters('location')]\",<\/span>\r\n\"sku\": {<\/span>\r\n\"name\": \"Standard_LRS\"<\/span>\r\n},<\/span>\r\n\"kind\": \"Storage\"<\/span>\r\n},<\/span>\r\n{<\/span>\r\n\"type\": \"Microsoft.Network\/publicIPAddresses\",<\/span>\r\n\"apiVersion\": \"2021-02-01\",<\/span>\r\n\"name\": \"[parameters('publicIpName')]\",<\/span\r\n\u00a0\"location\": \"[parameters('location')]\",<\/span>\r\n\"sku\": {<\/span>\r\n\"name\": \"[parameters('publicIpSku')]\"<\/span>\r\n},<\/span>\r\n\"properties\": {<\/span>\r\n\"publicIPAllocationMethod\": \"[parameters('publicIPAllocationMethod')]\",<\/span>\r\n\"dnsSettings\": {<\/span>\r\n\"domainNameLabel\": \"[parameters('dnsLabelPrefix')]\"<\/span>\r\n}<\/span>\r\n}<\/span>\r\n},<\/span>\r\n{<\/span>\r\n\"type\": \"Microsoft.Network\/networkSecurityGroups\",<\/span>\r\n\"apiVersion\": \"2021-02-01\",<\/span>\r\n\"name\": \"[variables('networkSecurityGroupName')]\",<\/span>\r\n\"location\": \"[parameters('location')]\",<\/span>\r\n\"properties\": {<\/span>\r\n\"securityRules\": [<\/span>\r\n{<\/span>\r\n\"name\": \"default-allow-3389\",<\/span>\r\n\"properties\": {<\/span>\r\n\"priority\": 1000,<\/span>\r\n\"access\": \"Allow\",<\/span>\r\n\"direction\": \"Inbound\",<\/span>\r\n\"destinationPortRange\": \"3389\",<\/span>\r\n\"protocol\": \"Tcp\",<\/span>\r\n\"sourcePortRange\": \"*\",<\/span>\r\n\"sourceAddressPrefix\": \"*\",<\/span>\r\n\"destinationAddressPrefix\": \"*\"<\/span>\r\n}<\/span>\r\n}<\/span>\r\n]<\/span>\r\n\r\n},<\/span>\r\n{<\/span>\r\n\"type\": \"Microsoft.Network\/virtualNetworks\",<\/span>\r\n\"apiVersion\": \"2021-02-01\",<\/span>\r\n\"name\": \"[variables('virtualNetworkName')]\",<\/span>\r\n\"location\": \"[parameters('location')]\",<\/span>\r\n\"properties\": {<\/span>\r\n\"addressSpace\": {<\/span>\r\n\"addressPrefixes\": [<\/span>\r\n\"[variables('addressPrefix')]\"<\/span>\r\n]<\/span>\r\n},<\/span>\r\n\"subnets\": [<\/span>\r\n{<\/span>\r\n\"name\": \"[variables('subnetName')]\",<\/span>\r\n\"properties\": {<\/span>\r\n\"addressPrefix\": \"[variables('subnetPrefix')]\",<\/span>\r\n\"networkSecurityGroup\": {<\/span>\r\n\"id\": \"[resourceId('Microsoft.Network\/networkSecurityGroups', variables('networkSecurityGroupName'))]\"<\/span>\r\n}<\/span>\r\n}<\/span>\r\n}<\/span>\r\n]<\/span>\r\n},<\/span>\r\n\"dependsOn\": [<\/span>\r\n\u00a0\"[resourceId('Microsoft.Network\/networkSecurityGroups', variables('networkSecurityGroupName'))]\"<\/span>\r\n]<\/span>\r\n},<\/span>\r\n{<\/span>\r\n\"type\": \"Microsoft.Network\/networkInterfaces\",<\/span>\r\n\"apiVersion\": \"2021-02-01\",<\/span>\r\n\"name\": \"[variables('nicName')]\",<\/span>\r\n\"location\": \"[parameters('location')]\",<\/span>\r\n\"properties\": {<\/span>\r\n\"ipConfigurations\": [<\/span>\r\n{<\/span>\r\n\u00a0\"name\": \"ipconfig1\",<\/span>\r\n\"properties\": {<\/span>\r\n\"privateIPAllocationMethod\": \"Dynamic\",<\/span>\r\n\"publicIPAddress\": {<\/span>\r\n\"id\": \"[resourceId('Microsoft.Network\/publicIPAddresses', parameters('publicIpName'))]\"<\/span>\r\n},<\/span>\r\n\"subnet\": {<\/span>\r\n\"id\": \"[resourceId('Microsoft.Network\/virtualNetworks\/subnets', variables('virtualNetworkName'), variables('subnetName'))]\"<\/span>\r\n}<\/span>\r\n}<\/span>\r\n}<\/span>\r\n]<\/span>\r\n},<\/span>\r\n\"dependsOn\": [<\/span>\r\n\u00a0\"[resourceId('Microsoft.Network\/publicIPAddresses', parameters('publicIpName'))]\",<\/span>\r\n\u00a0\"[resourceId('Microsoft.Network\/virtualNetworks', variables('virtualNetworkName'))]\"<\/span>\r\n\u00a0]<\/span>\r\n},<\/span>\r\n{<\/span>\r\n\"type\": \"Microsoft.Compute\/virtualMachines\",<\/span>\r\n\"apiVersion\": \"2021-03-01\",<\/span>\r\n\"name\": \"[parameters('vmName')]\",<\/span>\r\n\"location\": \"[parameters('location')]\",<\/span>\r\n\"properties\": {<\/span>\r\n\"hardwareProfile\": {<\/span>\r\n\"vmSize\": \"[parameters('vmSize')]\"<\/span>\r\n},<\/span>\r\n\"osProfile\": {<\/span>\r\n\"computerName\": \"[parameters('vmName')]\",<\/span>\r\n\"adminUsername\": \"[parameters('adminUsername')]\",<\/span>\r\n\"adminPassword\": \"[parameters('adminPassword')]\"<\/span>\r\n},<\/span>\r\n\"storageProfile\": {<\/span>\r\n\"imageReference\": {<\/span>\r\n\"publisher\": \"MicrosoftWindowsServer\",<\/span>\r\n\"offer\": \"WindowsServer\",<\/span>\r\n\"sku\": \"[parameters('OSVersion')]\",<\/span>\r\n\"version\": \"latest\"<\/span>\r\n\u00a0},<\/span>\r\n\"osDisk\": {<\/span>\r\n\"createOption\": \"FromImage\",<\/span>\r\n\"managedDisk\": {<\/span>\r\n\"storageAccountType\": \"StandardSSD_LRS\"<\/span>\r\n}<\/span>\r\n},<\/span>\r\n\"dataDisks\": [<\/span>\r\n{<\/span>\r\n\u00a0\"diskSizeGB\": 1023,<\/span>\r\n\u00a0\"lun\": 0,<\/span>\r\n\"createOption\": \"Empty\"<\/span>\r\n}<\/span>\r\n]<\/span>\r\n},<\/span>\r\n\"networkProfile\": {<\/span>\r\n\"networkInterfaces\": [<\/span>\r\n{<\/span>\r\n\"id\": \"[resourceId('Microsoft.Network\/networkInterfaces', variables('nicName'))]\"<\/span>\r\n}<\/span>\r\n]<\/span>\r\n},<\/span>\r\n\"diagnosticsProfile\": {<\/span>\r\n\"bootDiagnostics\": {<\/span>\r\n\"enabled\": true,<\/span>\r\n\u00a0\u00a0\"storageUri\": \"[reference(resourceId('Microsoft.Storage\/storageAccounts', variables('storageAccountName'))).primaryEndpoints.blob]\"<\/span>\r\n}<\/span>\r\n\u00a0}<\/span>\r\n},<\/span>\r\n\"dependsOn\": [<\/span>\r\n\"[resourceId('Microsoft.Network\/networkInterfaces', variables('nicName'))]\",<\/span>\r\n\u00a0\"[resourceId('Microsoft.Storage\/storageAccounts', variables('storageAccountName'))]\"<\/span>\r\n]<\/span>\r\n}<\/span>\r\n\u00a0\u00a0],<\/span>\r\n\"outputs\": {<\/span>\r\n\"hostname\": {<\/span>\r\n\"type\": \"string\",<\/span>\r\n\"value\": \"[reference(resourceId('Microsoft.Network\/publicIPAddresses', parameters('publicIpName'))).dnsSettings.fqdn]\"<\/span>\r\n}<\/span>\r\n\u00a0\u00a0}<\/span>\r\n}<\/span><\/span><\/pre>\n
Deploy the ARM Template<\/strong><\/p>\n
In the Azure Portal, open the Azure CLI within the Cloud Shell pane.<\/span>
\n<\/span><\/p>\n
\"Azure-login-page.\"<\/p>\n
In the pop-up box, Click on Bash.<\/span>
\n<\/span><\/p>\n
\"azure-cloud-shell-log-in\"<\/p>\n
In the getting started box, we have to enter the following details and click on apply.<\/span>
\n<\/span>Select \u201cNo storage account required\u201d.<\/span>
\n<\/span>Subscription<\/strong>: Select your own subscription<\/span><\/p>\n
\"azure-cloud-shell-subscription\"<\/span>
\n<\/span>In the toolbar of the Cloud Shell pane, select the <\/span>Manage file <\/b>option and then click on <\/span>Upload <\/b>to upload the <\/span>template.json<\/b> file into the Cloud Shell home directory.<\/span><\/p>\n

\n<\/span>\"cloud-shell-home-directory\"<\/span>
\n<\/span>Now we will deploy the resources using the given command. This step may take a few minutes for the resources to be deployed successfully.<\/span>
\n<\/span>az deployment group create –name <deployment-name> –template-file <path-to-template-file> –parameters ‘{“adminUsername”: {“value”: “<admin-username>”}, “adminPassword”: {“value”: “<admin-password>”}}’ –resource-group <resource-group-name><\/span>
\n<\/span>
\n<\/span>NOTE: <\/b>Copy this command to a text editor and replace:<\/span><\/p>\n
For the hands-on part of this tutorial, you will need to login to our Whizlabs Website<\/a> using your credentials (Email ID and Password).<\/span><\/span><\/p>\n