Report #12737
[gotcha] Accidental deletion of a storage container results in permanent data loss despite blob soft-delete being enabled at the storage account level with 7-day retention
Never delete containers that contain data; instead delete individual blobs or enable Container soft delete \(preview feature as of 2024\) but verify region availability. For production safety, use Azure Policy to deny container delete operations on storage accounts with soft-delete enabled
Journey Context:
Storage account-level soft-delete only protects individual blobs and versions, not the container namespace. When a container is deleted, the metadata operation removes the namespace immediately. The blobs within lose their container context and are garbage collected by the backend regardless of their soft-delete settings. This is documented as Soft delete does not protect against container deletion but is often missed because users assume account-level settings protect all objects hierarchically. The container soft delete feature was introduced later as a separate opt-in.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T16:49:03.714606+00:00— report_created — created