To Bicep or to Terraform - That is the Question

If you're getting started with an implementation using Infrastructure as Code, one of the first things to figure out is which tool to use. In this session will dive into the details of the differences of Bicep and Terraform to help you choose the best option for your scenario.
We will begin the session by going through the similarities of Bicep and Terraform, but will then jump straight into the differences of these two tools. We will cover how state is handled, how configuration is scoped and how making changes is evaluated. Then we will go through how existing resources are handled and using preview features. At the end of this session you will be able to choose which tool is the best option for your implementation!
Speaker: Heini Ilmarinen SQLbits.com/speakers/Heini_Il...
SQLbits.com/Sessions/To_Bicep_...
Tags: Azure,Azure SQL Database,Data Lake,deployment,Managing,Architecture & Infrastructure,DataOps & Automation

[@vinayayinapurapu]

Very clear and concise..❤

[@SQLBits]

Thank you! 🙂

[@usmanrahat2913]

Nice talk.
In Bicep can we import beyond a single resouce? Like the whole resource group? or beyond that a subscription?
Probably not right?
Thanks

[@MrRolloTamasi]

Larger scopes can be exported as arm template and turned to bicep with az bicep decompile. The single resource import is for vscode.