Infrastructure as code delivers many benefits to developers, infrastructure engineers, and their organizations. Azure resource manager made it possible to define your Azure resources and infrastructure using Azure resource manager (ARM) templates, which was a great step forward. But these JSON-based ARM templates can be challenging to work with. The Bicep domain specific language was created to simplify the development and management of your Azure infrastructure as code, eliminating the need for wrangling JSON.

Join me for this session to learn how I’ve been using Bicep to automate complex Azure infrastructure deployments while simplifying the code to do so. I’ll provide an overview of the Bicep language, a lap around the tools you need to be productive with Bicep, and I’ll show you where to go to get started and learn more.

In addition to getting started with Bicep, I’ll also show you how my team and I reuse Bicep code, orchestrate infrastructure deployments with DevOps tooling and release management pipelines, and how we reverse engineer existing Azure resources into Bicep templates and migrate existing ARM templates into Bicep.