<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Azure DevOps on Incredible Technology, Incredibly Simple</title><link>https://damianflynn.com/tags/azure-devops/</link><description>Recent content in Azure DevOps 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/azure-devops/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>Azure DevOps Wiki to a Corporate PDF</title><link>https://damianflynn.com/posts/from-azure-devops-wiki-to-a-corporate-pdf/</link><pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/from-azure-devops-wiki-to-a-corporate-pdf/</guid><description>&lt;p&gt;The project documentation is in good shape. The team has been maintaining an Azure DevOps wiki, the architecture pages link to the detailed design, and the deployment instructions sit alongside the decisions that explain them.&lt;/p&gt;
&lt;p&gt;Then comes the handover request: “Can you send us the design document as a PDF? Please use the company template.”&lt;/p&gt;
&lt;p&gt;That is a reasonable request. The recipient might not have access to Azure DevOps. An architecture board may need a fixed version to review, or the customer may need to file the document in a records system. A wiki is useful for the people doing the work; a controlled document is useful for the people accepting it.&lt;/p&gt;</description></item><item><title>Building a Jekyll Site with Azure DevOps: Docker and Native Pipelines</title><link>https://damianflynn.com/posts/constructing-a-new-home-with-jekyll-and-azure-devops/</link><pubDate>Wed, 10 Oct 2018 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/constructing-a-new-home-with-jekyll-and-azure-devops/</guid><description>&lt;h1 class="relative text-5xl font-semibold leading-tense text-secondary-500 mb-4 -ml-px" id="migrating-like-a-jekyll-using-azure-devops"&gt;&lt;a href="#migrating-like-a-jekyll-using-azure-devops" class="header-mark" aria-label="Header mark for 'Migrating like a Jekyll using Azure DevOps'"&gt;&lt;/a&gt;
 &lt;div id="migrating-like-a-jekyll-using-azure-devops" class="absolute -top-28"&gt;&lt;/div&gt;
 Migrating like a Jekyll using Azure DevOps
&lt;/h1&gt;
&lt;p&gt;One of the unspoken truths behind the lack of posts on ths blog in recent history was due to a few bugs, which in the end resulted in an experience where from home it appeared that any new content was published and working; but outside this fortress in the real world, there was a large silence echoing.&lt;/p&gt;</description></item></channel></rss>