Build blob lifecycle management rules for tiering, deletion, and snapshots.
Last verified: May 2026
Output will appear here...The Azure Blob Lifecycle Builder helps you create lifecycle management policies for Azure Blob Storage containers. Lifecycle policies automate transitioning blobs between access tiers (Hot, Cool, Cold, Archive) and deleting old blobs based on age or last access time. This tool provides a visual rule builder with support for prefix filters, blob types, and multiple actions per rule, generating the JSON policy you can apply to your storage account.
Your team's Azure Storage account holds 800 TB of CI build artifacts in Hot tier, costing ~$15K/month. Most artifacts are accessed once during the build, never again. The builder generates a 2-rule policy: Rule 1 = move to Cool after 30 days; Rule 2 = move to Archive after 90 days; delete after 365 days. After 3 months of policy execution, 600 TB has tiered down. New monthly cost: ~$2,500. Annual savings: ~$150,000.
Last access time tracking adds storage transaction costs (every read updates a timestamp). For high-traffic Hot tier blobs, this can add $0.05-0.10/GB to your monthly bill. Only enable last-access tracking for containers where you actually plan to use it for lifecycle decisions.
Archive tier has a 180-day minimum storage duration. If your lifecycle rule moves blobs to Archive after 30 days and your retention policy deletes them after 60 days, you'll pay 180-day equivalent for blobs that only existed in Archive for 30 days. Always set Archive transition such that blobs stay there for at least 180 days.
Lifecycle rules evaluate once per day, not in real-time. A rule that says 'delete after 90 days' might delete a blob on day 90.5, not the moment it crosses the threshold. For audit-sensitive lifecycles, factor in the 24-hour delay when designing retention.
The builder constructs a lifecycle management policy JSON document containing rules with filter sets (prefixMatch, blobIndexMatch, blobTypes), conditions (daysAfterCreationGreaterThan, daysAfterModificationGreaterThan, daysAfterLastAccessTimeGreaterThan), and actions (tierToCool, tierToCold, tierToArchive, delete, enableAutoTierToHotFromCool). It validates that conditions and actions are logically consistent (e.g., delete > tier transitions in days), and outputs JSON ready for the Set-AzStorageAccountManagementPolicy or az storage account management-policy create commands.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.