A container deleted 32 days ago cannot be undeleted if its 30-day container soft-delete retention period has expired; Azure Storage permanently deletes it when that period ends.^1^
Changing the retention period now will not recover or extend that deleted container. Retention changes apply only to containers deleted after the change; containers already deleted retain the period that was active when they were deleted.^1^
Remaining recovery options
- Check for a separate copy or backup that existed before deletion, such as:
- Another storage account or replicated application-level copy.
- An exported/on-premises backup.
- A previously configured vaulted Azure Blob backup.
Vaulted backup stores an offsite copy of block-blob data and can protect against source data loss.^2^
- Do not rely on operational Azure Blob backup to undelete the container. Microsoft documents that operational backup cannot restore a container deleted through the Delete Container operation; container soft delete is the protection mechanism for that scenario.^3^
- If a separate backup existed, create a replacement container and restore or copy the backed-up blobs into it according to that backup system’s restore procedure. If no independent copy existed, the expired soft-deleted container and its contents are not recoverable through Azure Blob Storage.
For future protection, increase Storage account → Data protection → Enable soft delete for containers to a suitable value, up to 365 days. This protects only future deletions and is not retroactive.^1^
References
- Soft delete for containers
- Architecture best practices for Azure Blob Storage
- Configure and manage backup for Azure Blobs using Azure Backup