Exercise - Use Azure Resource Manager tags and parameter files

In this exercise, you add tags to help organize and track your Microsoft Azure resources. You also use an Azure Resource Manager (ARM) template parameter file to allow for different parameter configurations for each deployment.

Create a tag to track the resource deployment environment and project

First, you create a parameter to use as a resource tag in your template.

1. In Visual Studio Code, in the azuredeploy.json file, Add an attribute called defaultValue: and set the value to {"Environment": "Dev", "Project": "Tutorial"}.

   The parameter block should look like this code:

   "parameters": {
     "storagePrefix": {
       "type": "string",
       "minLength": 3,
       "maxLength": 11
     },
     "storageSKU": {
       "type": "string",
       "defaultValue": "Standard_LRS",
       "allowedValues": [
         "Standard_LRS",
         "Standard_GRS",
         "Standard_RAGRS",
         "Standard_ZRS",
         "Premium_LRS",
         "Premium_ZRS",
         "Standard_GZRS",
         "Standard_RAGZRS"
       ]
     },
     "resourceTags": {
       "type": "object",
       "defaultValue": {
         "Environment": "Dev",
         "Project": "Tutorial"
       }
     }
   },
   

2. Use this parameter to tag your storage account resource. Change the tags: attribute in the resource definition:

   "tags": "[parameters('resourceTags')]",
   

3. Your file should look like this file:

   {
     "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
     "contentVersion": "1.0.0.0",
     "parameters": {
       "storagePrefix": {
         "type": "string",
         "minLength": 3,
         "maxLength": 11
       },
       "storageSKU": {
         "type": "string",
         "defaultValue": "Standard_LRS",
         "allowedValues": [
           "Standard_LRS",
           "Standard_GRS",
           "Standard_RAGRS",
           "Standard_ZRS",
           "Premium_LRS",
           "Premium_ZRS",
           "Standard_GZRS",
           "Standard_RAGZRS"
         ]
       },
       "resourceTags": {
         "type": "object",
         "defaultValue": {
           "Environment": "Dev",
           "Project": "Tutorial"
         }
       }
     },
     "functions": [],
     "variables": {
       "uniqueStorageName": "[toLower(concat(parameters('storagePrefix'),uniqueString(resourceGroup().id)))]"
     },
     "resources": [
       {
         "name": "[variables('uniqueStorageName')]",
         "type": "Microsoft.Storage/storageAccounts",
         "apiVersion": "2025-01-01",
         "tags": "[parameters('resourceTags')]",
         "location": "[resourceGroup().location]",
         "kind": "StorageV2",
         "sku": {
           "name": "[parameters('storageSKU')]"
         }
       }
     ],
     "outputs": {}
   }
   

4. Save the file.

Deploy the ARM template with updated tags

Verify that the new tags are in the deployment

1. In Azure, select your resource group name, then select the storage account you deployed.

2. Notice the Environment : Dev and Project : Tutorial tags:

   

Use a parameter file

There are currently three parameters to fill in each time you deploy this template. Each user of the template can create a file to hold their parameter values. Here, you create a parameter file to use with your template.

1. In Visual Studio Code, create another file. Call it azuredeploy.parameters.dev.json.

2. In this file, you add the values for the template parameters that you want to have input into the template for the development environment. Change a tag value to see that the deployment makes a change. For example, you could change projectName to Learn:

   {
     "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
     "contentVersion": "1.0.0.0",
     "parameters": {
       "storagePrefix": {
         "value": "{unique-prefix}"
       },
       "storageSKU": {
         "value": "Standard_LRS"
       },
       "resourceTags": {
         "value": {
           "Environment": "Dev",
           "Project": "Learn"
         }
       }
     }
   }
   

3. Be sure to replace {unique-prefix} with your unique prefix.

4. Save the file.

Deploy the template with the parameter file

In this section, you deploy the ARM template, specifying which parameter file to use.