storage lifecycle

What it is

Azure Blob Storage lifecycle management is a set of rules that automatically changes the tier of eligible blobs or deletes them as they age. A policy can reduce storage cost when data becomes less useful, without someone moving every file by hand.

Think of a records room. Recent invoices stay in the filing cabinet; older ones move to cheaper off-site storage; records past an approved retention date are discarded. The written rule decides what happens, not a person remembering each month.

Why it exists

Northwind may keep recent receipt files readily available but rarely open receipts from last year. A lifecycle policy can move selected files to a cooler tier after a defined period and later delete only data whose retention requirements allow deletion.

Key ideas

• A policy contains rules. A rule combines conditions, filters, and actions in JSON configuration.
• Conditions can use creation, last-modified, and—when access-time tracking is enabled—last-accessed time.
• Filters can target the whole account, selected containers, name prefixes, or blob index tags. Filters select what to include; they do not provide an exclusion list.
• Actions can tier eligible blobs or delete current versions, previous versions, and snapshots. Support depends on blob and account type.
• Changes to a policy can take up to 24 hours to take effect and begin their first run. Policy execution is periodic, not an exact clock for each blob.

Northwind example

Priya approves a rule for Northwind’s receipt container: files tagged record=receipt move to a cooler tier after 90 days and are considered for deletion only after the company’s approved retention period. Luis tests the rule against non-production data first and monitors its outcome. A newly accessed blob might move back to hot immediately, but Northwind does not assume this makes every archive operation free or instantaneous.

Lifecycle policy versus backup

| Question | Lifecycle management | Backup | | --- | --- | --- | | Main purpose | Control cost and routine retention through automated actions. | Recover data after loss, corruption, or another failure. | | Deletes data? | It can, when its rule matches. | It preserves recovery copies under its configured policy. | | Safe substitute for the other? | No. | No. |

Before a delete rule, identify legal retention, restore needs, soft-delete settings, immutable data, and the people allowed to approve deletion.

Common confusion

• Lifecycle management does not guarantee that an object disappears at a precise moment. Processing is periodic and can take longer under account load.
• A cheaper tier changes cost and access characteristics; it is not a backup copy.
• A policy cannot override immutability. Delete actions do not work for blobs in an immutable container.

Related

blob-storage · storage-account · azure-backup · redundancy-lrs-zrs-grs · northwind-traders-case-study

Sources and re-audit

• Microsoft Learn — Azure Blob Storage lifecycle management overview, checked 2026-09-16.