Hey folks! I recently featured as a guest on the Ctrl+Alt+Azure podcast for episode 109 to talk Azure Policy as Code with hosts Tobias Zimmergren and Jussi Roine.
Tobias had reached out to me over twitter to check my availability and interest in contributing to an upcoming episode dedicated to Azure Policy as Code.
Admittedly I was surprised by Tobias’s message, and other community events were already on my calendar, but the fact of the matter is that having actively advocated on this exact subject matter over the past 12+ months I would not be passing up such a wonderful opportunity!
You can tune into the episode at https://ctrlaltazure.com/episodes/109-azure-policy-as-code. There you’ll also find helpful links to various tools and resources mentioned during our talk.
Starting from ground zero with Azure Policy? Check out episode 25 of the Ctrl+Alt+Azure podcast Azure Policies - the how, the what, and the why?
Azure Policy as Code - Episode 109 - Session Abstract
Don’t have 40 mins to listen to the entire episode but want to know what’s discussed? I’ve got you covered!
Here’s 13 points of Azure Policy as Code goodness covered during episode 109!
- Brief introduction to Azure Policy and Policy as Code using Bicep language - Microsoft’s Domain Specific Language for transpiling into ARM Templates.
- At what point might you decide to move from managing your Azure Policies via the Azure Portal (click-ops) to a Policy as Code workflow based on Infrastructure as Code and DevOps methodologies?
- Using Bicep’s loadtextcontext function to quickly onboard new policies to your Bicep modules.
- Is there a difference in capability for developers when managing your Azure Policies from the Azure Portal versus managing them as code via say Bicep/ARM templates?
- What are some key concepts to know about when working with Azure Policy as Code workflows?
- Designing your Service Principal RBAC roles adhering to the principle of least privilege.
- How to approach testing methdologies for new custom Azure Policies before deploying them to prod.
- Programmatically triggering an Azure Policy on-demand compliance scan at your desired scope.
- Recommended tools for getting started with Azure Policy as Code workflows using Bicep language.
- Available options for migrating your Azure Policies from the Azure Portal to a code-driven workflow.
- Free community tools which can assist with your Azure Policy as Code journey.
- Infrastructure as Code tooling comparison.
- A surprise question to Jesse.
Now that I’ve piqued your curiousity tune into the episode at https://ctrlaltazure.com/episodes/109-azure-policy-as-code.
The Ctrl+Alt+Azure podcast journey
My own research of the Ctrl+Alt+Azure podcast’s early beginnings and it’s journey from episode 1 to episode 52 (late last year) has yielded many insightful blog posts from both Tobias and Jussi.
I highly recommend checking them out! For example I found a couple beautiful gems in their documented journey some of which include:
- Choosing a podcast name. (one of my favourites!)
- Finding time to record an episode.
- Staying flexible with scheduling.
- Leveraging peer pressure to collaborate.
- Finding their audience via distribution.
- Technology and tooling choices.
- Announcing a new podcast Ctrl Alt Azure - Tobias Zimmergren
- Announcing our new podcast Ctrl Alt Azure the first episode is out now - Jussi Roine
Getting started blog posts
- How we planned and launched a podcast the technical story - Tobias Zimmergren
- Getting started with a podcast the equipment setup and logistics - Jussi Roine
- The first anniversary of the Ctrl Alt Azure podcast - Jussi Roine
It was an amazing opportunity to talk Azure Policy as Code with Tobias Zimmergren and Jussi Roine. I personally learned much from the discussions. Also very grateful for the wide scope of questions from Tobias and Jussi related to the topic and hope we were inclusive towards various perspectives, scenarios, and skillsets!
As to my own experience with contributing to a podcast episode let’s just say I now have a great appreciation for the amount of effort required to plan, setup, and record just one of these episodes!
Thanks for tuning in folks. I hope you found the episode interesting, informative, and helpful; as always I welcome your feedback and comments.