Despite all the different options, when it's time to adopt an Infrastructure as Code approach on Azure, my first choice is always Bicep.

Why? I can enumerate several reasons for this, starting with its simplified syntax, the incredible instruments we can use to code it, as well as some really interesting native features we can leverage.

In this session, I'll go through all the key points that make Bicep so cool to me. Additionally, I'll show you how easy is to implement it in a structured way in comparison to ARM templates, thanks to the simplified reusability of the code and its integration with CI/CD pipelines.