Deployments that use Azure Resource Manager templates (ARM templates) and Bicep files result in a series of changes to your Azure environment. In this module, you learn how to review the changes that will happen before you execute a deployment.
Suppose you help to manage the Azure environment at a toy company. One of your colleagues has asked you to help update some templates that you previously created to deploy a virtual network. Before you deploy your updated template, you want to confirm exactly what changes Azure will make. So you decide to evaluate how to preview changes in your deployments.
What will we be doing?
In this module, you gain an understanding of the what-if operation for Azure Resource Manager. You also learn about the modes that you can use for your deployments to Azure.
Bicep is a new language for defining your Azure resources. It has a simpler authoring experience than JSON, along with other features that help improve the quality of your infrastructure as code. We recommend that anyone new to infrastructure as code on Azure use Bicep instead of JSON. To learn about Bicep, see Deploy and manage resources in Azure by using Bicep.
What is the main goal?
By the end of this module, you'll be able to preview the changes that will happen before you deploy by using the what-if operation.
You should be familiar with:
- Creating and deploying basic ARM templates, using either Bicep or JSON.
- Azure, including the Azure portal, subscriptions, resource groups, and resource definitions.
To follow along with the exercises in the module, you'll need:
- Visual Studio Code installed locally.
- The Bicep extension for Visual Studio Code installed locally.
- The Azure Resource Manager Tools for Visual Studio Code extension installed locally.