Azure Blob Storage lifecycle management can automatically move older data to less expensive storage tiers or delete data when it reaches the end of its required lifetime.
This guide explains how to create a lifecycle rule through the Azure portal.
Before you begin
Identify:
- The Azure storage account you want to manage
- The containers or blob prefixes the rule should cover
- The blob types included in the rule
- How long data should remain in each storage tier
- Whether the rule may eventually delete data
Review retention, backup, legal, and operational requirements before enabling deletion.
Create a lifecycle management rule
- Sign in to the Azure portal.
- Open the required storage account.
- Under Data management, select Lifecycle management.
- Open the List View tab.
- Select Add a rule.
- Enter a descriptive rule name, such as
archive-project-records. - Choose whether the rule applies to every blob or only blobs that match filters.
- Select the applicable blob type and subtype.
Use a name that describes the data and action. This makes the rule easier to review later.
Define the lifecycle actions
Open the Base blobs section and configure the required conditions. For example, a rule could:
- Move blobs to the cool tier 30 days after modification
- Move blobs to the archive tier after 90 days
- Delete blobs after 365 days
Use periods that reflect actual access patterns. Moving frequently accessed data to a colder tier can introduce retrieval charges and delays.
If you use a condition based on the last access date, enable access time tracking for the storage account first. Azure charges for last-access-time updates as storage transactions.
Limit the rule with filters
If the rule should apply only to selected data, open Filter set and add a filter. You can use:
- Container and path prefixes
- Blob index tags
- Blob types
For example, a prefix can restrict the rule to a path such as project-records/completed/.
Filters should be as specific as practical. A broad rule may evaluate far more objects than intended and could affect active data.
Save the rule
Review the rule and select Add. The rule will appear in the lifecycle management list. Azure runs lifecycle policies periodically. A policy does not necessarily process every eligible object immediately, and large storage accounts can take multiple days to complete.
Verify the policy safely
- Apply the rule to a small test container or prefix.
- Use longer time thresholds during initial testing.
- Confirm that the filter identifies only the expected blobs.
- Review Azure Monitor logs and lifecycle completion events where available.
- Check the resulting blob tiers before expanding the rule.
Azure lifecycle rules operate on the complete policy document. When the policy is updated programmatically, make sure existing rules remain in the submitted policy.
Important limitations
- Lifecycle management does not affect the
$logsand$websystem containers. - A lifecycle rule cannot rehydrate an archived blob to an online tier.
- Deletion does not override an immutable storage policy.
- With blob soft delete enabled, a lifecycle deletion places the blob into its soft-deleted state for the configured retention period.
- Storage transactions generated by tiering actions can create charges.
