Delete Blob operation marks the specified blob or snapshot for deletion. The blob is later deleted during garbage collection.
Note that in order to delete a blob, you must delete all of its snapshots. You can delete both at the same time with the
Delete Blob operation.
Delete Blob request may be constructed as follows. HTTPS is recommended. Replace myaccount with the name of your storage account:
|DELETE Method Request URI||HTTP Version|
Emulated Storage Service URI
When making a request against the emulated storage service, specify the emulator hostname and Blob service port as
127.0.0.1:10000, followed by the emulated storage account name:
|DELETE Method Request URI||HTTP Version|
For more information, see Using the Azure Storage Emulator for Development and Testing.
The following additional parameters may be specified on the request URI.
||Optional. The snapshot parameter is an opaque
The following table describes required and optional request headers.
||Required. Specifies the authentication scheme, account name, and signature. For more information, see Authentication for the Azure Storage Services.|
||Required. Specifies the Coordinated Universal Time (UTC) for the request. For more information, see Authentication for the Azure Storage Services.|
||Required for all authenticated requests. For more information, see Versioning for the Azure Storage Services.|
||Required if the blob has an active lease.
To perform this operation on a blob with an active lease, specify the valid lease ID for this header. If a valid lease ID is not specified on the request, the operation will fail with status code 403 (Forbidden).
||Required if the blob has associated snapshots. Specify one of the following two options:
This header should be specified only for a request against the base blob resource. If this header is specified on a request to delete an individual snapshot, the Blob service returns status code 400 (Bad Request).
If this header is not specified on the request and the blob has associated snapshots, the Blob service returns status code 409 (Conflict).
||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.|
This operation also supports the use of conditional headers to delete the blob only if a specified condition is met. For more information, see Specifying Conditional Headers for Blob Service Operations.
The response includes an HTTP status code and a set of response headers.
A successful operation returns status code 202 (Accepted).
For information about status codes, see Status and Error Codes.
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.
||This header uniquely identifies the request that was made and can be used for troubleshooting the request. For more information, see Troubleshooting API Operations.|
||Indicates the version of the Blob service used to execute the request. This header is returned for requests made against version 2009-09-19 and above.|
||A UTC date/time value generated by the service that indicates the time at which the response was initiated.|
This operation can be performed by the account owner or by anyone using a Shared Access Signature that has permission to delete the blob.
When a blob is successfully deleted, it is immediately removed from the storage account's index and is no longer accessible to clients. The blob's data is later removed from the service during garbage collection.
If the blob has an active lease, the client must specify a valid lease ID on the request in order to delete it.
If a blob has a large number of snapshots, it's possible that the
Delete Blob operation will time out. If this happens, the client should retry the request.
For version 2013-08-15 and later, the client may call
Delete Blob to delete uncommitted blobs. An uncommitted blob is a blob that was created with calls to the Put Block operation but never committed using the Put Block List operation. For earlier versions, the client must commit the blob first before deleting it.