<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Building Azure With Code on Incredible Technology, Incredibly Simple</title><link>https://damianflynn.com/series/building-azure-with-code/</link><description>Recent content in Building Azure With Code on Incredible Technology, Incredibly Simple</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 16 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://damianflynn.com/series/building-azure-with-code/index.xml" rel="self" type="application/rss+xml"/><item><title>bicep-deploy vs bicep-action: A Tool or a Workflow?</title><link>https://damianflynn.com/posts/bicep-deploy-vs-bicep-action-a-tool-or-a-workflow/</link><pubDate>Mon, 16 Nov 2026 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/bicep-deploy-vs-bicep-action-a-tool-or-a-workflow/</guid><description>&lt;h1 class="relative text-5xl font-semibold leading-tense text-secondary-500 mb-4 -ml-px" id="azurebicep-deploy-vs-bicep-action-a-tool-or-a-workflow"&gt;&lt;a href="#azurebicep-deploy-vs-bicep-action-a-tool-or-a-workflow" class="header-mark" aria-label="Header mark for 'Azure/bicep-deploy vs bicep-action: A Tool or a Workflow?'"&gt;&lt;/a&gt;
 &lt;div id="azurebicep-deploy-vs-bicep-action-a-tool-or-a-workflow" class="absolute -top-28"&gt;&lt;/div&gt;
 Azure/bicep-deploy vs bicep-action: A Tool or a Workflow?
&lt;/h1&gt;
&lt;p&gt;





 
 
 
 


&lt;figure class="my-8"&gt;
 &lt;img src="https://damianflynn.com/posts/bicep-deploy-vs-bicep-action-a-tool-or-a-workflow/bicep-deploy-vs-bicep-action/hero.png" alt="A tool versus a workflow" class="w-full rounded-lg" /&gt;
 
&lt;/figure&gt;
&lt;/p&gt;
&lt;p&gt;I maintain &lt;a href="https://github.com/innofactororg/bicep-action" target="_blank" rel="noopener noreferrer"&gt;innofactororg/bicep-action&lt;/a&gt;, so I should say up front that I am not a neutral party. I am also the person who most needs this comparison to be honest, because every time someone evaluates bicep-action for a new estate, the first question is the obvious one: why not just use Microsoft&amp;rsquo;s?&lt;/p&gt;</description></item><item><title>bicep-action: Plan, Review and Deploy Bicep from Pull Requests</title><link>https://damianflynn.com/posts/bicep-action-plan-review-and-deploy-bicep-from-pull-requests/</link><pubDate>Mon, 09 Nov 2026 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/bicep-action-plan-review-and-deploy-bicep-from-pull-requests/</guid><description>&lt;p&gt;






&lt;figure class="my-8"&gt;
 &lt;img src="https://raw.githubusercontent.com/innofactororg/bicep-action/v1/docs/images/hero.png" alt="Plan, review, deploy" class="w-full rounded-lg" /&gt;
 
&lt;/figure&gt;
&lt;/p&gt;
&lt;p&gt;Terraform teams stopped deploying blind years ago. They open a pull request, a bot runs &lt;code&gt;terraform plan&lt;/code&gt; and posts the result as a comment, a colleague reads exactly what will be created, changed and destroyed, and only then does anyone type &lt;code&gt;atlantis apply&lt;/code&gt;. Most Bicep teams still merge and find out. The pipeline runs, the deployment succeeds or fails, and the first time anyone sees what Azure actually did is in the activity log afterwards.&lt;/p&gt;</description></item><item><title>Terraform or Bicep for Azure: Strengths Compared</title><link>https://damianflynn.com/posts/considering-terraform-and-bicep/</link><pubDate>Wed, 15 Feb 2023 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/considering-terraform-and-bicep/</guid><description>&lt;h1 class="relative text-5xl font-semibold leading-tense text-secondary-500 mb-4 -ml-px" id="considering-terraform-and-bicep"&gt;&lt;a href="#considering-terraform-and-bicep" class="header-mark" aria-label="Header mark for 'Considering Terraform and Bicep'"&gt;&lt;/a&gt;
 &lt;div id="considering-terraform-and-bicep" class="absolute -top-28"&gt;&lt;/div&gt;
 Considering Terraform and Bicep
&lt;/h1&gt;
&lt;p&gt;As more organizations adopt cloud infrastructure, the demand for infrastructure as code (IAC) solutions has grown. Infrastructure as code allows developers to manage and automate infrastructure deployments using code, making it easier to track changes and maintain consistency.&lt;/p&gt;
&lt;p&gt;Terraform and Bicep are two popular IAC solutions that enable developers to manage and automate infrastructure deployments using code.&lt;/p&gt;</description></item><item><title>Azure Tags as Bicep Parameters</title><link>https://damianflynn.com/posts/bicep-tags-as-parameters/</link><pubDate>Fri, 23 Jul 2021 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/bicep-tags-as-parameters/</guid><description>&lt;p&gt;A deployment often needs to find infrastructure that already exists. A virtual machine might belong to a subscription with a shared Recovery Services vault, while its backup policy depends on the workload. Passing the vault name, its resource group and the policy name into every deployment works, but repeats configuration that may already be recorded in Azure.&lt;/p&gt;
&lt;p&gt;In the earlier post, &lt;a href="https://damianflynn.com/posts/azure-iac-tags-as-parameters/" rel=""&gt;Azure Tags as ARM Template Parameters&lt;/a&gt;, I used tags to look up those values from an ARM JSON template. This is the same lab scenario expressed in Bicep. The lookup behaves the same way, but the string interpolation makes the resource paths easier to follow.&lt;/p&gt;</description></item><item><title>Azure Tags as ARM Template Parameters</title><link>https://damianflynn.com/posts/azure-iac-tags-as-parameters/</link><pubDate>Sun, 17 Jan 2021 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/azure-iac-tags-as-parameters/</guid><description>&lt;h1 class="relative text-5xl font-semibold leading-tense text-secondary-500 mb-4 -ml-px" id="azure-as-a-state-machine-dogfooding-tags"&gt;&lt;a href="#azure-as-a-state-machine-dogfooding-tags" class="header-mark" aria-label="Header mark for 'Azure as a State Machine, dogfooding Tags'"&gt;&lt;/a&gt;
 &lt;div id="azure-as-a-state-machine-dogfooding-tags" class="absolute -top-28"&gt;&lt;/div&gt;
 Azure as a State Machine, dogfooding Tags
&lt;/h1&gt;
&lt;p&gt;In the post, I am going to introduce a concept which will allow you to greatly up your Infrastructure as Code game, by using Azure as a State Machine!&lt;/p&gt;
&lt;p&gt;One of the typical challenges when deploying ARM templates, is the sheer number of parameters which we find as a requirement to complete a deployment; which as you will appreciate gets considerably harder as we target many environments.&lt;/p&gt;</description></item><item><title>Appending Tags to Azure Resources with ARM Templates</title><link>https://damianflynn.com/posts/azure-iac-appending-tags/</link><pubDate>Wed, 01 Apr 2020 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/azure-iac-appending-tags/</guid><description>&lt;p&gt;Todays conundrum: As I am leveraging templates, there will always be some standard tags I require to implement within the template, but I also require to provide additional tags as a parameter to be appended with the deployment.&lt;/p&gt;
&lt;p&gt;My objective is to set up tags within an ARM template in accordance with good governance and the Cloud adoption framework.&lt;/p&gt;
&lt;h2 class="relative text-3xl font-bold leading-tight text-secondary-500 mb-2 mt-12 -ml-px"&gt;
 &lt;div id="solution" class="absolute -top-28"&gt;&lt;/div&gt;
 Solution
&lt;/h2&gt;
&lt;p&gt;ARM Template functions to the rescue. Todays salvation is called &lt;code&gt;union&lt;/code&gt;, which you can learn more about on the actual [reference site][https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-template-functions-array#union]&lt;/p&gt;</description></item><item><title>Configure the Azure Application Gateway WAF with PowerShell</title><link>https://damianflynn.com/posts/configuring-the-web-application-firewall-with-powershell/</link><pubDate>Thu, 03 Oct 2019 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/configuring-the-web-application-firewall-with-powershell/</guid><description>&lt;p&gt;Microsoft Azure Application Gateway is a Layer 7 application delivery controller (ADC) offered as a service in Azure. It provides load balancing, SSL termination, end-to-end SSL, URL path-based routing, and basic web application firewall (WAF) functionality.&lt;/p&gt;
&lt;p&gt;Working with the WAF, I usually build a basic configuration in the Portal before exporting the ARM JSON, which, then becomes my primary method to working on this service.&lt;/p&gt;
&lt;h2 class="relative text-3xl font-bold leading-tight text-secondary-500 mb-2 mt-12 -ml-px"&gt;
 &lt;div id="why-json-you-may-ask" class="absolute -top-28"&gt;&lt;/div&gt;
 Why JSON you may ask&amp;hellip;
&lt;/h2&gt;
&lt;p&gt;One of my biggest gripes with the Azure Firewall solutions currently is based on thier CRUD &lt;em&gt;(Create, Read, Update and Delete)&lt;/em&gt; interface. It always results in a workflow from hell, training along the lines of &amp;lsquo;&lt;em&gt;Edit, Save,&lt;/em&gt; &lt;em&gt;&lt;strong&gt;WAIT,&lt;/strong&gt;&lt;/em&gt;, &lt;em&gt;Edit, Save,&lt;/em&gt; &lt;em&gt;&lt;strong&gt;WAIT&lt;/strong&gt;&lt;/em&gt;&amp;rsquo; in a painful loop. What should be a fast and straightforward configuration update, typically is a process that must be executed over many hours, preferably on a second screen.&lt;/p&gt;</description></item></channel></rss>