Frequently asked questions about ARM templates

ARM templates are JSON files where you define what you want to deploy to Azure. Templates help you implement an infrastructure-as-code solution for Azure. Your organization can repeatedly and reliably deploy the required infrastructure to different environments.

To learn more about how ARM templates help you manage your Azure infrastructure, see What are ARM templates?

To simplify authoring ARM templates, you need the right tools. We recommend installing Visual Studio Code and the Azure Resource Manager tools extension. For a quick introduction to these tools, see Quickstart: Create ARM templates with Visual Studio Code.

When you're ready to learn about creating ARM templates, start the beginner tutorial series on ARM templates. These tutorials take you step by step through the process of constructing an ARM template. You learn about the different sections of the template and how to they work together.

Use the option that you like the best. Both services assist you with automating deployments to Azure.

We believe there are benefits to using ARM templates over other infrastructure-as-code services. To learn about those benefits, see Why choose ARM templates?

Yes, watch it anytime.

For general information about features we're working, join our Azure Advisors Deployments Yammer group.

To learn about the new template language, sign up for notifications.

To learn about template specs, see Azure Resource Manager template specs.

For recommendations about how you implement your templates, see ARM template best practices. After creating a template, run the ARM test toolkit. It checks whether your template matches recommended practices.

Yes, you can export the template from a resource group. The exported template is a good starting point for learning about templates, but you'll probably want to revise it before using it in a production environment.

When exporting the template, you can select which resources you want to include in the template.

Yes, you can create a resource group in a template when you deploy the template at the level of your Azure subscription. For an example of creating a resource group and deploying resources, see Resource group and resources.

We recommend running the ARM test toolkit and the what-if operation on your templates before deploying them. The test toolkit checks whether your template uses best practices. It provides warnings when it identifies changes that could improve how you've implemented your template.

The what-if operation shows the changes your template makes to your environment. You can see unintended changes before they're deployed. What-if also returns any errors it can detect during preflight validation. For example, if your template contains a syntactical error, it returns that error. It also returns any errors it can determine about the final state of the deployed resources. For example, if your template deploys a storage account with a name that is already in use, what-if returns that error.

VS Code provides intellisense for working with the resource properties.

Use the copy element to specify more than one instance. You can use copy on resources, properties, variables, and outputs.

To learn about the new language, see What is Bicep (Preview)?.

Currently, there's no plan to support YAML. We believe the new template language offers a solution that is easier to use than YAML or JSON.

Yes, you can continue using JSON templates.

Yes. See Converting ARM templates between JSON and Bicep.

Azure Blueprints will use template specs in its implementation by replacing the blueprint definition resource with a template spec resource. We provide a migration path to convert the blueprint definition into a template spec, but the blueprint definition APIs will still be supported. There are no changes to the blueprint assignment resource. Blueprints remain a user-experience to compose a governed environment in Azure.

No, but template specs are designed to work well with linked templates. You don't have to move the linked template to a publicly accessible endpoint before deploying the parent template. Instead, you package the parent template and its artifacts together when creating the template spec.

Yes, they can be used across subscriptions as long as the user has read access to the template spec. Template specs can't be used across tenants.

Yes, use deployment scripts. You can include Azure PowerShell or Azure CLI scripts in your templates.

Those options are still available and haven't changed. Deployment scripts are designed to perform actions that aren't related to the VM guest. If you need to run a script on a host operating system in a VM, then the custom script extension and/or DSC would be a better choice. However, deployment scripts have advantages, such as setting the timeout duration.

Yes, you can use deployment scripts in China East 2 region on Azure China 21vianet currently.

Yes, use the what-if feature. It evaluates the current state of your environment and compares it to the state that will exist after deployment. You can examine the summarized changes to make sure the template doesn't have any unexpected results.

Yes, both deployment modes are supported. For an example of using incremental mode, see Run what-if operation. For an example of using complete mode, see Confirm deletion.

Yes, what-if evaluates the state of the parent template and its linked templates.

Yes, you can use what-if to verify that the Pipeline should continue.

We're working on reducing the noise. You help us improve by submitting issues in our GitHub repo here: https://aka.ms/WhatIfIssues

We have a community-contributed VS Code extension that does a great job of visualizing your ARM template. It shows the resources you're deploying and the relationships between them.

The template visualizer is being previewed in the portal. For more information, watch this short session from Build.

In the past, this limit was five resource groups. It has recently been increased to 800 resource groups. For more information, see Create resource groups and resources at the subscription level.

We're changing how the deployment history for a resource group is maintained. In the past, you had to manually delete deployments from this history to avoid this error. Starting in June 2020, we'll automatically delete deployments from the history as you get near the limit. For more information, see Automatic deletions from deployment history.

Deleting a deployment from the history doesn't affect the deployed resources.

Yes. For an explanation of how to use template and pipelines, see Tutorial: Continuous integration of ARM templates with Azure Pipelines and Integrate ARM templates with Azure Pipelines.

Yes, see Deploy ARM templates by using GitHub Actions.

Next steps

For an introduction to ARM templates, see What are ARM templates?.