What two components could you use to implement a “infrastructure as code” deployment? Bicep and ARM TemplatesAzure Policy and Azure ArcAzure Monitor and Azure Arc

The two components that you could use to implement an "infrastructure as code" deployment are Bicep and ARM Templates.

Here's a step-by-step guide on how you could use these two components:

1. Bicep: Bicep is a Domain Specific Language (DSL) for deploying Azure resources declaratively. It aims to drastically simplify the authoring experience with a cleaner syntax and better support for modularity and code re-use.

   • Step 1: Install the Bicep CLI by following the instructions in the Bicep GitHub repository.
   • Step 2: Write your infrastructure code in a .bicep file. This file will contain the description of what you want to deploy in Azure.
   • Step 3: Use the Bicep CLI to compile your .bicep file into an ARM template. The command for this is bicep build <filename>.bicep.
   • Step 4: Deploy the generated ARM template using the Azure CLI or PowerShell with the command az deployment group create or New-AzResourceGroupDeployment respectively.

2. ARM Templates: Azure Resource Manager (ARM) templates are JSON files that define the resources you need to deploy for your solution.

   • Step 1: Write your infrastructure code in a .json file. This file will contain the description of what you want to deploy in Azure.
   • Step 2: Use the Azure CLI or PowerShell to deploy your ARM template with the command az deployment group create or New-AzResourceGroupDeployment respectively.

Both Bicep and ARM Templates allow you to define and deploy your entire Azure infrastructure declaratively, and they support all the resources available in Azure.