# Restore a blob's current content separately from undeleting its versions

> Undelete restores retained soft-deleted versions together; it does not make one of them the current blob.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-293-restore-a-blob-s-current-content-separately-from-undeleting-its-versions/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:27:03+00:00
- Modified: 2026-09-10T01:23:49+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

Undelete restores retained soft-deleted versions together; it does not make one of them the current blob.

## Potentially affected

Supported Azure Blob Storage accounts with blob versioning and blob soft delete enabled.

## DSE recommendation

Separate recovery of retained versions from the approved choice of content to promote as current.

## Article

## Source facts

With versioning enabled, deleting a blob without a version ID turns its current version into a previous version and leaves no current version. Existing previous versions remain. Deleting a specific previous version while soft delete is enabled instead retains that deleted version for the configured retention period.

Undelete Blob restores all retained soft-deleted versions, not a selected single version, and promotes none of them to current. Microsoft describes restoring those versions first and then copying the chosen previous version to a new current version. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/blobs/versioning-overview).

## Applicability

Identify the account’s supported configuration, exact blob and relevant version IDs. Confirm that the required version is still recoverable before planning restoration.

## DSE recommendation

DSE recommends recording which content the application should receive and who approves that choice. Keep restoration of historical versions separate from any operation that changes current content. Review existing application writes before promoting a version so the recovery decision accounts for concurrent activity. Do not interpret a successful undelete response as proof that the intended application data is now current.

## Verification

In an approved recovery test, inspect the recovered version list, identify the selected source and read the current blob after the separate promotion. Compare its content with the approved recovery point. Record any version that could not be recovered and any current-content discrepancy before returning the application to normal use.

## Official references

[Microsoft Learn: Blob Versioning in Azure Storage](https://learn.microsoft.com/en-us/azure/storage/blobs/versioning-overview). Source retrieved September 9, 2026.

## Primary reference

- Name: Blob Versioning in Azure Storage - Azure Storage | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/storage/blobs/versioning-overview
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Restore a blob's current content separately from undeleting its versions,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-293-restore-a-blob-s-current-content-separately-from-undeleting-its-versions/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.