<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bicep on Incredible Technology, Incredibly Simple</title><link>https://damianflynn.com/tags/bicep/</link><description>Recent content in Bicep 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/tags/bicep/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></channel></rss>