Transcribed
The PowerShell Ceiling: Why You Need Bicep
Jul 7, 2026 ·
1h 9m 13s
Download and listen anywhere
Download your favorite episodes and enjoy them, wherever you are! Sign up or log in now to access offline listening.
The PowerShell Ceiling: Why You Need Bicep
Description
You have dozens of PowerShell scripts that work, but nobody could rebuild the platform behind them in three hours. This episode is for Microsoft 365 and Azure automation engineers who...
show more
You have dozens of PowerShell scripts that work, but nobody could rebuild the platform behind them in three hours. This episode is for Microsoft 365 and Azure automation engineers who have hit the scripting ceiling. Learn how Bicep turns infrastructure and identity into versioned, auditable code and how to start the transition next Monday.
In this episode
Key takeaways
Worth quoting
“It does not fail because the scripts are bad. It fails because automation that scales becomes infrastructure that nobody can govern.” – Mirko Peters (00:30)
“PowerShell is a tool for doing things. It is not a tool for defining what things should be.” – Mirko Peters (05:58)
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 – 50 Scripts Nobody Can Govern
- 01:08 – The Automation Journey
- 03:17 – What PowerShell Is and Isn't
- 09:21 – The Declarative Shift with Bicep
- 15:38 – Identity as Infrastructure with Graph Bicep
- 24:56 – Governance as Code, Modules and Git
- 35:40 – CI/CD Pipelines and Career Impact
- 58:56 – Limitations, Terraform and First Steps
Key takeaways
- Script sprawl fails not because PowerShell is bad but because imperative scripts never declare the infrastructure, identities and permissions they depend on.
- Bicep, now including Microsoft Graph resources, lets you declare Azure infrastructure and Entra ID identity in Git, with modules, what-if previews and pipelines enforcing governance by default.
- Use Bicep for infrastructure, PowerShell for operations and Graph for data, and choose Terraform only when you genuinely operate across multiple clouds.
Worth quoting
“It does not fail because the scripts are bad. It fails because automation that scales becomes infrastructure that nobody can govern.” – Mirko Peters (00:30)
“PowerShell is a tool for doing things. It is not a tool for defining what things should be.” – Mirko Peters (05:58)
Explore more on M365.FM
- Episode page: the full episode with chapters, quotes and an FAQ on Bicep
- Bicep – the Azure-native declarative language the episode recommends for defining infrastructure and identity as code
- Infrastructure as code – the shift from imperative scripts to declared, versioned infrastructure kept in Git
- Governance – the hidden cost of script sprawl, solved by modules that enforce naming, tags and logging
- Terraform – the multi-cloud alternative, recommended only when you actually run workloads beyond Azure
- Related episode: ARM Templates Were a Mistake: Lessons from the Bicep Shift
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 | www.m365.fm |
| Tags |
Copyright 2026 - Spreaker Inc. an iHeartMedia Company
Comments