<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Pipeline on AJTech</title>
    <link>https://ajtech.nl/tags/pipeline/</link>
    <description>Recent content in Pipeline on AJTech</description>
    <generator>Hugo -- 0.152.2</generator>
    <language>en</language>
    <copyright>Copyright © 2023–2026, Arash Jalalat; all rights reserved</copyright>
    <lastBuildDate>Mon, 13 Jan 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ajtech.nl/tags/pipeline/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Boost your Azure Pipeline with Bicep&#39;s deployer() function</title>
      <link>https://ajtech.nl/blog/boost-your-azure-pipeline-with-biceps-deployer-function/</link>
      <pubDate>Mon, 13 Jan 2025 00:00:00 +0000</pubDate>
      <guid>https://ajtech.nl/blog/boost-your-azure-pipeline-with-biceps-deployer-function/</guid>
      <description>&lt;h1 id=&#34;context&#34;&gt;Context&lt;/h1&gt;
&lt;p&gt;Last month Microsoft released its newest Bicep version &lt;code&gt;v0.32.4&lt;/code&gt; which includes an interesting function called &lt;code&gt;deployer()&lt;/code&gt;. This function can retrieve the ObjectId and TenantId of the deploying Service principal. This can be very helpful in certain cases such as assigning tags to Azure resources or to assign a role to the deploying Service principal.&lt;/p&gt;
&lt;p&gt;In my experience you have strong Infrastructure as Code (IaC) setup when you combine both Bicep with Azure Pipelines for deploying resources to Azure. Let&amp;rsquo;s have a look what we can do with the new &lt;code&gt;deployer()&lt;/code&gt; function.&lt;/p&gt;</description>
      <enclosure url="https://ajtech.nl/images/2025/01/bicep-deployer.jpg" type="image/jpeg" />
    </item>
  </channel>
</rss>
