Infrastructure as Code on Azure: Bicep vs Terraform vs Pulumi

on YouTube ↗53m

" summary

Compares Bicep, Terraform, and Pulumi by showing live demos: creating a storage account and app service in Azure and updating Cloudflare DNS. Bicep compiles to ARM, runs in Azure, has no state file — Azure is state and uses deployment scripts that spin containers (can’t reach private resources). Terraform uses providers, stores a JSON state (often remote) and state files contain plain-text secrets, and has ~16k+ Stack Overflow questions. Pulumi runs your language, debugs locally, supports native providers and SaaS state with encryption.

AI-written summary · about

" chapters (5)

1. 0:00Start
2. 40:13Have applications create infrastructure
3. 41:00Self-service tooling by platform teams
4. 41:58Server vs Client-side execution
5. 48:38Community - Google Search Trends

" related talks

• 01h 00mIaC Forged in Code: ARM/Bicep vs Terraform vs PulumiMike Benkovich · NDC Oslo 2025
• 01h 04mIaC Forged in Code: ARM/Bicep vs Terraform vs PulumiMike Benkovich · NDC London 2024
• 53mInfrastructure as code - is it really?Shahid Iqbal · NDC DevOps 2020
• 01h 05mAn Infrastructure as Code Bake-off, comparing ARM, Terraform and BicepMike Benkovich · NDC London 2023
• 27mEvaluating Your ToolboxKavitha Govindarajulu · Devopsdays Boston 2022
• 58mDeploying Cloud Infrastructure using PulumiShahid Iqbal · NDC Melbourne 2022
• 49mTo Bicep or to Terraform - That is the QuestionHeini Ilmarinen · SQLBits 2023
• 48mState of Infra-as-CodeAlex Frankel, Mark Gray · PowerShell + DevOps Global Summit 2025