Undelete Blob

The Undelete Blob operation restores the contents and metadata of soft deleted blob and any associated soft deleted snapshots.

Undelete Blob is supported only on version 2017-07-29 or later.


The Undelete Blob request may be constructed as follows. HTTPS is recommended. Replace myaccount with the name of your storage account:

PUT Method Request URI HTTP Version
https://myaccount.blob.core.windows.net/mycontainer/myblob?comp=undelete HTTP/1.1

Emulated Storage Service URI

When making a request against the emulated storage service, specify the emulator hostname and Blob service port as, followed by the emulated storage account name:

PUT Method Request URI HTTP Version devstoreaccount1/mycontainer/myblob?comp=undelete HTTP/1.1

For more information, see Using the Azure Storage Emulator for Development and Testing.

URI Parameters

The following additional parameters may be specified on the request URI.

Parameter Description
timeout Optional. The timeout parameter is expressed in seconds. For more information, see Setting Timeouts for Blob Service Operations.

Request Headers (All Blob Types)

The following table describes required and optional request headers for all blob types.

Request Header Description
Authorization Required. Specifies the authentication scheme, account name, and signature. For more information, see Authentication for the Azure Storage Services.
Date or x-ms-date Required. Specifies the Coordinated Universal Time (UTC) for the request. For more information, see Authentication for the Azure Storage Services.
x-ms-version Required for all authenticated requests. Specifies the version of the operation to use for this request. For more information, see Versioning for the Azure Storage Services.
x-ms-client-request-id Optional. Provides a client-generated, opaque value with a 1 KB character limit that is recorded in the analytics logs when storage analytics logging is enabled. Using this header is highly recommended for correlating client-side activities with requests received by the server. For more information, see About Storage Analytics Logging and Azure Logging: Using Logs to Track Storage Requests.

Request Body



The response includes an HTTP status code and a set of response headers.

Status Code

A successful operation returns status code 200 (OK).

For information about status codes, see Status and Error Codes.

Response Headers

The response for this operation includes the following headers. The response may also include additional standard HTTP headers. All standard headers conform to the HTTP/1.1 protocol specification.

Syntax Description
x-ms-request-id This header uniquely identifies the request that was made and can be used for troubleshooting the request. For more information, see Troubleshooting API Operations.
x-ms-version Indicates the version of the Blob service used to execute the request.
Date A UTC date/time value generated by the service that indicates the time at which the response was initiated.

Response Body



This operation can only be called by the account owner and by anyone with a Shared Access Signature that has permission to write to this blob or its container.


When a soft deleted blob is undeleted, the blob and any associated snapshots are available for operations using other APIs. Undelete request to blob, undeletes soft deleted blob and any associated soft deleted snapshots. Attempting to undelete a blob that is not soft deleted nor has any soft deleted snapshots will succeed without any changes.

See Also

Authentication for the Azure Storage Services
Status and Error Codes Delete Blob