Welcome back! In our previous session, we delved into the strengths of YAML as a tremendous alternative for orchestrating Azure configurations via Bicep. Today, I'll guide you through deploying Azure resources using a YAML with Bicep.
🧑💻 Using YAML and Bicep Together
Revisiting the previous post, you might remember our YAML file, structured as follows:
resourceGroups:
- name: "app01"
location: "westeurope"
tags:
environment: "dev"
project: "project01"
- name: "app02"
location: "northeurope"
tags:
environment: "dev"
This file lists two resource groups, app01 and app02. Each resource group has a name, location, and tags property. It's like a to-do list for our task. Now, we will write a resource block in Bicep to create these resource groups in Azure.



