Implement and manage storage
Storage Lifecycle and Data Protection
CoreCombine soft delete, snapshots, lifecycle policies, and versioning according to deletion, retention, and recovery needs.
Aligned to the current AZ-104 study guide, verified August 21, 2026.
Why this matters
Data protection settings answer different recovery questions: undo deletion, recover a previous state, preserve share points in time, or automate movement and expiration.
Must Know
- Blob soft delete retains deleted blobs for a configured period; container soft delete protects a deleted container as a unit.
- Blob versioning automatically keeps prior versions when a blob is modified or deleted, subject to lifecycle and retention planning.
- Azure Files share snapshots capture a read-only point-in-time view, while file-share soft delete helps recover a deleted share.
- Blob lifecycle management evaluates rules that can tier or delete matching data according to age and filters.
- Protection features can be combined, but administrators must account for retained versions, snapshots, capacity, and deletion behavior.
Compare and Distinguish
- Lifecycle management vs soft delete vs versioning: automated tier/delete policy vs recovery window after deletion vs prior state on each write or delete.
- Blob soft delete vs container soft delete: recover individual deleted blobs vs recover a deleted container and its contents.
- Azure Files snapshot vs share soft delete: point-in-time share view vs recovery of a share deletion.
Scenario examples
- Scenario: Users overwrite a blob and need yesterday’s contents without restoring an entire container. Think: Enable versioning and manage retained versions with lifecycle rules.
- Scenario: An administrator accidentally deletes a complete file share. Think: Recover it through share soft delete within the retention period.
- Scenario: Blobs should move to cooler tiers and later expire automatically. Think: Configure ordered lifecycle actions with filters and age conditions.
Exam traps
- A lifecycle delete action is not a point-in-time recovery mechanism.
- A file-share snapshot does not protect a share that was deleted unless the appropriate delete-protection capability is also enabled.
- Versioning can increase retained capacity until old versions are explicitly governed.
Key takeaways
- Map each failure event to the recovery object that can reverse it.
- Combine protection and lifecycle controls deliberately so automated cleanup does not defeat retention requirements.
How it works
- Protection features retain a deleted object or historical state until its policy permits permanent removal.
- Lifecycle evaluation runs asynchronously, so an eligible object does not necessarily change at the exact instant it reaches the threshold.
Objects and administrative surfaces
- Storage account Blob service — soft-delete retention, container protection, versioning, and lifecycle policy.
- Blob container and blob — current objects, previous versions, soft-deleted objects, and lifecycle rule filters.
- Storage account File service and share — share snapshots and deleted-share retention.
When to use it
- Use versioning for frequent object changes and soft delete for accidental deletion recovery.
- Use snapshots for file-share point-in-time views and lifecycle policies for repeatable data aging.
Security and governance implications
- Restrict changes to retention and lifecycle rules because shortening protection can remove recovery options.
- Monitor retained-data growth and align deletion actions with legal and operational retention requirements.
How to reason about this
- For a missing recovery item, verify the protection feature was enabled before the event, its retention has not expired, and the correct deleted or version view is selected.
- For an unapplied lifecycle action, inspect policy enablement, filters, age basis, supported tier or object type, and asynchronous evaluation delay.
More detail
- Configure Blob and Files protection at their service scopes, set retention periods, and know which deleted or previous object appears during recovery.
- Lifecycle rules can filter by path and blob characteristics and perform supported tier or delete actions when age conditions are met.
Ready for the quiz?
- Which feature retrieves a blob’s state before it was overwritten?
- How does deleted-share recovery differ from a share snapshot?
- What happens to storage consumption when versions accumulate without lifecycle cleanup?
Related objectives
- D2.3.S4 — Configure soft delete for blobs and containers
- D2.3.S5 — Configure snapshots and soft delete for Azure Files
- D2.3.S6 — Configure blob lifecycle management
- D2.3.S7 — Configure blob versioning