Migrate Azure resources and JSON ARM templates to use Bicep
Export and convert your Azure resources to Bicep files, and migrate your JSON Azure Resource Manager templates (ARM templates) to Bicep. Refactor your Bicep files to follow best practices. Test your Bicep files and deploy them to production.
Learning objectives
After completing this module, you'll be able to:
- Convert JSON ARM templates to Bicep.
- Create Bicep definitions for your existing Azure resources.
- Verify template conversions by using the what-if operation and documentation.
Prerequisites
You should be familiar with the following:
- Azure, including the Azure portal, subscriptions, and resource groups.
- ARM templates (both JSON and Bicep), including parameters, modules, the
existingkeyword, and child and extension resources. - The what-if operation.
- Refactoring Bicep files to align with best practices.
Before you start the exercises in the module, you'll need the following items:
- An Azure account, with the ability to create resource groups. If you can't meet these requirements with your current Azure account, you can get a free trial and create a new Azure subscription and tenant.
- Local installations of the following software:
- Visual Studio Code
- Bicep extension for Visual Studio Code
- The latest version of one of the following command-line interface applications: