To Bicep or to Terraform - That is the Question

on YouTube ↗49m

" summary

Compares Bicep and Terraform for Azure with concrete differences: Bicep compiles to ARM, is Azure-native and uses no state file, defaulting to resource-group scope and offering an “insert resource” import in VS Code; Terraform uses an AzureRM provider, keeps a centralized state file (often plain‑text secrets), supports many providers (Databricks, AWS), offers a reliable terraform plan, and requires aztfy or terraform import for existing resources. Notes preview features lag in Terraform due to the Go SDK and some ARM/Bicep deployments can be slower than Terraform for certain services.

AI-written summary · about

" chapters (12)

1. 0:00Introduction to IaC
2. 3:48IaC benefits and concepts
3. 6:59Azure behind the scenes
4. 11:51Bicep vs Terraform
5. 18:53Bicep deployment demonstration
6. 22:16Performance and limitations
7. 25:45Terraform deployment demo
8. 30:55State file management
9. 34:04Reviewing and planning changes
10. 36:16Scope and modules
11. 38:47Importing existing resources
12. 43:57Tool selection and conclusion

" related talks

• 01h 04mIaC Forged in Code: ARM/Bicep vs Terraform vs PulumiMike Benkovich · NDC London 2024
• 53mInfrastructure as Code on Azure: Bicep vs Terraform vs PulumiErwin Staal · NDC Oslo 2023
• 01h 05mIaC Forged in Code: ARM/Bicep vs Terraform vs PulumiMike Benkovich · Copenhagen Developers Festival 2023
• 01h 00mIaC Forged in Code: ARM/Bicep vs Terraform vs PulumiMike Benkovich · NDC Oslo 2025
• 01h 05mAn Infrastructure as Code Bake-off, comparing ARM, Terraform and BicepMike Benkovich · NDC London 2023
• 27mEvaluating Your ToolboxKavitha Govindarajulu · Devopsdays Boston 2022
• 48mState of Infra-as-CodeAlex Frankel, Mark Gray · PowerShell + DevOps Global Summit 2025
• 01h 02mBicep: Deploy to Azure cloud without it being a pain in the ArmPaul Glavich · NDC Melbourne 2022