<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title></title><link>https://petarivanov.uk/</link><description>Practical tools and public projects for Azure automation, governance and infrastructure as code, by Petar Ivanov.</description><language>en-us</language>
    <atom:link href="https://petarivanov.uk/index.xml" rel="self" type="application/rss+xml"/>
    <item><title>Infrastructure as Code on Azure: Bicep vs Terraform in 2026</title><link>https://petarivanov.uk/blogs/iac-bicep-vs-terraform/</link><pubDate>Sun, 01 Mar 2026 00:00:00 &#43;0000</pubDate><guid>https://petarivanov.uk/blogs/iac-bicep-vs-terraform/</guid><description>&lt;h2 id=&#34;the-iac-landscape-in-2026&#34;&gt;The IaC Landscape in 2026&lt;/h2&gt;
&lt;p&gt;Infrastructure as Code has become table stakes for any serious Azure deployment. The two dominant tools in the Azure space — &lt;strong&gt;Bicep&lt;/strong&gt; and &lt;strong&gt;Terraform&lt;/strong&gt; — each have compelling strengths, and the choice between them significantly shapes your team&amp;rsquo;s workflow.&lt;/p&gt;
&lt;p&gt;This post covers the practical trade-offs based on real-world experience managing large Azure estates.&lt;/p&gt;
&lt;h2 id=&#34;bicep-azure-native-tight-integration&#34;&gt;Bicep: Azure-Native, Tight Integration&lt;/h2&gt;
&lt;p&gt;Bicep is Microsoft&amp;rsquo;s domain-specific language for Azure Resource Manager. It compiles down to ARM JSON, which means it has &lt;strong&gt;day-zero support for new Azure features&lt;/strong&gt; — the moment a resource type is available in ARM, you can deploy it with Bicep.&lt;/p&gt;</description></item><item><title>Azure Update Manager: What It Actually Replaces (and What It Doesn&#39;t)</title><link>https://petarivanov.uk/blogs/azure-update-manager-replacing-wsus/</link><pubDate>Tue, 20 Jan 2026 00:00:00 &#43;0000</pubDate><guid>https://petarivanov.uk/blogs/azure-update-manager-replacing-wsus/</guid><description>&lt;h2 id=&#34;a-common-misconception&#34;&gt;A Common Misconception&lt;/h2&gt;
&lt;p&gt;I keep seeing people frame Azure Update Manager as a WSUS replacement. It&amp;rsquo;s not — at least, not directly. What it actually replaced was &lt;strong&gt;Azure Automation Update Management&lt;/strong&gt; (the v1 solution that used Log Analytics workspaces and the &lt;code&gt;Updates&lt;/code&gt; OMS solution). That was deprecated in August 2024 and fully shut down on 28 February 2025.&lt;/p&gt;
&lt;p&gt;WSUS still works and still has its place, particularly for air-gapped environments and organisations that need granular approval workflows for specific KBs.&lt;/p&gt;</description></item>
  </channel>
</rss>
