Blob Versioning and Soft Delete Lifecycle

Blob versioning automatically saves a previous version of a blob every time it is modified, ensuring that you can restore point-of-time data easily. Versioning and blob soft delete are designed to work together to form a highly resilient safety net. When both features are enabled, deleting a current version of a blob simply changes its status to a previous version, while deleting a previous version moves it into a soft-deleted state. To recover your data, you can run an Undelete Blob operation to restore all soft-deleted versions at once, or use a Copy Blob operation to promote a specific previous version back to the current version. To manage the costs of keeping multiple versions, you can deploy lifecycle management policies that automatically archive or delete historical versions after they reach a certain age.