Transcribed
Azure Resource Manager - Simply Explained
Jul 16, 2026 ·
16m 1s
Download and listen anywhere
Download your favorite episodes and enjoy them, wherever you are! Sign up or log in now to access offline listening.
Azure Resource Manager - Simply Explained
Description
Most Azure users never notice the engine behind every deployment. This episode explains Azure Resource Manager in plain English for Azure beginners and admins, covering RBAC, resource groups, policies and...
show more
Most Azure users never notice the engine behind every deployment. This episode explains Azure Resource Manager in plain English for Azure beginners and admins, covering RBAC, resource groups, policies and ARM templates so deployments become consistent, governed and repeatable.
In this episode
Key takeaways
Worth quoting
“Every request to create, update, or delete a resource goes through ARM first. It doesn't matter how you make that request, whether it's through the Azure portal, the command line, power shell, or the SDKs, they all hit the same front door.” – Mirko Peters (01:02)
“Here's the rule you need to remember. Every single resource in Azure must belong to exactly one resource group, no exceptions.” – Mirko Peters (04:15)
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 – What Azure Resource Manager actually is
- 02:15 – Authentication and authorization with RBAC
- 03:48 – Resource groups
- 05:58 – Tags, locks and policies
- 08:28 – Infrastructure as code with ARM templates
- 10:32 – Real-world scenario: deploying a web app
- 12:25 – How it all fits together
- 14:22 – Actionable takeaways
Key takeaways
- Azure Resource Manager is the control plane every portal click, CLI command and template passes through, which is why results are consistent.
- Resource groups, RBAC, tags, locks and Azure Policy form one governance system that ARM enforces on every request.
- ARM templates and Bicep make deployments declarative and repeatable; export a template from an existing resource group to get started.
Worth quoting
“Every request to create, update, or delete a resource goes through ARM first. It doesn't matter how you make that request, whether it's through the Azure portal, the command line, power shell, or the SDKs, they all hit the same front door.” – Mirko Peters (01:02)
“Here's the rule you need to remember. Every single resource in Azure must belong to exactly one resource group, no exceptions.” – Mirko Peters (04:15)
Explore more on M365.FM
- Episode page: the full episode with chapters, quotes and a plain-English FAQ on ARM
- Microsoft Entra ID – the directory ARM relies on to verify your identity and issue the token for every request
- Infrastructure as code – the approach behind ARM templates, so environments become version controlled and repeatable
- Bicep – the simpler language Microsoft created that compiles to ARM templates when JSON feels too heavy
- Microsoft Azure – the platform whose portal, CLI, PowerShell and SDK requests all pass through ARM
- Related episode: ARM Templates - 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