4 Deploying ARM templates

 

This chapter covers

  • Understanding what happens when a template is deployed
  • Choosing a deployment tool
  • Picking the correct template deployment scope and mode
  • Understanding how authorizations, policies, and resource locks influence deployments
  • Debugging template deployments

After discussing how to write ARM templates in the previous chapters, it is time for a more in-depth discussion of what happens when you deploy a template. Every deployment goes through the same series of steps after you have submitted it to Azure Resource Manager. The first part of this chapter goes through those steps one by one.

After we discuss the deployment process, we’ll look at two more deployment topics: how you can use ARM to validate templates without actually deploying them, and how you can perform a dry run using a template. Such a dry run lists all the changes that would be made when deploying the template for real. Finally, we’ll touch on troubleshooting templates and explain what you can do when the deployment of a template fails. Before we dive into the details of the deployment process, let’s start with a quick overview.

4.1 An overview of the deployment process

All ARM deployments go through the same process for deployment. Figure 4.1 visualizes that process.

Figure 4.1 Template deployment process

4.2 Submitting a deployment

4.2.1 Choosing a deployment scope

4.2.2 Submitting a template using different tools

4.3 The execution phase

4.3.1 Role-based access control

4.3.2 Azure Policy

4.3.3 Resource locks

4.3.4 Resource provisioning

4.4 The clean-up phase

4.4.1 Incremental deployment mode

sitemap