<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Lifecycle Management on Erwin van den Bogaard</title>
    <link>https://evdbogaard.nl/tags/lifecycle-management/</link>
    <description>Recent content in Lifecycle Management on Erwin van den Bogaard</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 13 May 2026 10:00:00 +0200</lastBuildDate>
    <atom:link href="https://evdbogaard.nl/tags/lifecycle-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Automatically deleting blobs in Azure Blob Storage</title>
      <link>https://evdbogaard.nl/posts/automatic-delete-blob-azure/</link>
      <pubDate>Wed, 13 May 2026 10:00:00 +0200</pubDate>
      <guid>https://evdbogaard.nl/posts/automatic-delete-blob-azure/</guid>
      <description>&lt;p&gt;Recently I worked on a task where I needed to remove uploaded blobs after a certain amount of time. My mind immediately went to &lt;code&gt;Azure Blob storage lifecycle management&lt;/code&gt;, but the problem appeared to be a bit more nuanced than I first thought.&lt;/p&gt;&#xA;&lt;p&gt;With lifecycle management you can define rules that automatically perform actions on blobs. Each rule consists of conditions, actions, and filters.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;Conditions&lt;/code&gt;: Specify if the rule applies based on when a blob was created, last modified, or last accessed.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;Actions&lt;/code&gt;: Specify which action to apply. This can be changing the blob&amp;rsquo;s tier or deleting it.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;Filters&lt;/code&gt;: Limits the rule to a subset of blobs. By default it applies to all blobs, but filters allow for filtering for certain tags or prefixes.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;A common use case is to automatically clean up temporary data. You&amp;rsquo;d create a rule that filters on a prefix like &lt;code&gt;tmp/&lt;/code&gt;, set a condition to match blobs that haven&amp;rsquo;t been modified in 30 days, and set the action to delete. You can also combine actions in a single rule, for example first transitioning a blob from hot to cool after 7 days and then deleting it after 90 days. As long as your blobs are organized by prefix or tagged consistently, this works great.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
