<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Azure Policy on Erwin van den Bogaard</title>
    <link>https://evdbogaard.nl/tags/azure-policy/</link>
    <description>Recent content in Azure Policy on Erwin van den Bogaard</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 07 Jul 2026 10:00:00 +0200</lastBuildDate>
    <atom:link href="https://evdbogaard.nl/tags/azure-policy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using Azure Policy to prevent unscoped blob lifecycle rules</title>
      <link>https://evdbogaard.nl/posts/blob-lifecycle-policy/</link>
      <pubDate>Tue, 07 Jul 2026 10:00:00 +0200</pubDate>
      <guid>https://evdbogaard.nl/posts/blob-lifecycle-policy/</guid>
      <description>&lt;p&gt;Azure Blob Storage lifecycle management is a nice way to move blobs between tiers or delete them after a certain amount of time. You configure the rule once and Azure takes care of the rest. The part that can be easy to miss is that a rule without filters applies to everything in the storage account.&lt;/p&gt;&#xA;&lt;p&gt;That can be fine when you really do want a global rule, but most of the time it is risky. A missing &lt;code&gt;prefixMatch&lt;/code&gt; or &lt;code&gt;blobIndexMatch&lt;/code&gt; can suddenly transition or delete far more blobs than intended. In production you probably have reviews and deployment checks in place, but in lower environments it is still easy for someone to push a bad change and create a mess that takes time to clean up.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
