Transcribed
ARM Templates - Simply Explained
Jul 15, 2026 ·
15m 4s
Download and listen anywhere
Download your favorite episodes and enjoy them, wherever you are! Sign up or log in now to access offline listening.
ARM Templates - Simply Explained
Description
Still clicking through the Azure portal to build the same environment again and again? This episode explains ARM templates and infrastructure as code in plain English for Azure admins and...
show more
Still clicking through the Azure portal to build the same environment again and again? This episode explains ARM templates and infrastructure as code in plain English for Azure admins and developers, and shows how to deploy repeatable environments, make templates reusable and when to move to Bicep.
In this episode
Key takeaways
Worth quoting
“The second approach is declarative, and that's what Arm templates use. Instead of telling Azure how to build something, you just describe what you want the end result to look like.” – Mirko Peters (03:20)
“Arm templates are idempotent. That's a fancy word meaning you can deploy the same template 100 times and get the same result.” – Mirko Peters (04:12)
Explore more on M365.FM
Follow and rate M365.FM in your podcast app, and join the free M365 community at m365con.net.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support.
show less
In this episode
- 00:00 – Intro: stop clicking through the portal
- 00:42 – What Azure Resource Manager is
- 02:20 – Infrastructure as code: the big idea
- 04:30 – Anatomy of an ARM template
- 06:50 – Making templates reusable
- 08:51 – How deployment works
- 10:55 – The Bicep evolution
- 13:03 – Common mistakes and how to avoid them
Key takeaways
- Azure Resource Manager is the control layer behind every Azure request, and ARM templates are its declarative, idempotent JSON blueprints.
- Parameters, variables, conditions, copy loops and linked templates let one template serve development, test and production environments.
- Bicep is recommended for new deployments and compiles to ARM JSON, so understanding ARM still helps when troubleshooting deployments.
Worth quoting
“The second approach is declarative, and that's what Arm templates use. Instead of telling Azure how to build something, you just describe what you want the end result to look like.” – Mirko Peters (03:20)
“Arm templates are idempotent. That's a fancy word meaning you can deploy the same template 100 times and get the same result.” – Mirko Peters (04:12)
Explore more on M365.FM
- Episode page: the full episode with chapters, quotes and a short FAQ on ARM templates
- Bicep – presented as the cleaner language that compiles to ARM JSON and is recommended for new deployments
- Infrastructure as code – the core idea behind ARM templates, explained through declarative versus imperative deployment
- Visual Studio Code – recommended with the ARM Tools extension to catch JSON syntax errors and name mismatches
- Mirko Peters – hosts this Knowledge Nugget and walks through ARM templates from structure to deployment
- Related episode: Azure Resource Manager - Simply Explained
Follow and rate M365.FM in your podcast app, and join the free M365 community at m365con.net.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support.
Information
| Author | Mirko Peters M365, Azure & AI |
| Organization | m365 FM |
| Website | - |
| Tags |
Copyright 2026 - Spreaker Inc. an iHeartMedia Company
Comments