Set Blob Tier

The Set Blob Tier operation sets the tier on a blob. The operation is allowed on a page blob in a premium storage account and on a block blob in a blob storage account (locally redundant storage only). A premium page blob's tier determines the allowed size, IOPS, and bandwidth of the blob. A block blob's tier determines Hot/Cool/Archive storage type. This operation does not update the blob's ETag.

Tiers on blob storage accounts are currently in preview. For detailed information about block blob level tiering see Hot, cool and archive storage tiers.

Request

The Set Blob Tier request may be constructed as follows. HTTPS is recommended. Replace myaccount with the name of your storage account and myblob with the blob name for which the tier is to be changed.

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

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

The following table describes required and optional request headers.

Request Header Description
Authorization Required. Specifies the authentication scheme, storage 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-access-tier Required. Indicates the tier to be set on the blob. For a list of allowed premium page blob tiers, see High-performance Premium Storage and managed disks for VMs. For blob storage LRS accounts, valid values are Hot/Cool/Archive. Tiers on standard blob accounts are currently in preview. For detailed information about standard blob LRS account blob level tiering see Hot, cool and archive storage tiers.
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 see About Storage Analytics Logging and Azure Logging: Using Logs to Track Storage Requests.

Request Body

None.

Response

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

Status Code

A successful operation returns status code 200 (OK) if the new tier takes effect immediately, or status code 202 (Accepted) if the transition to the new tier is pending. For premium account page blob operation returns status code 200 (OK). For block blobs, below table describes the http status codes returned based on current tier and requested tier of the blob:

Set to Hot Set to Cool Set to Archive
Blob in Hot Tier 200 200 200
Blob in Cool Tier 200 200 200
Blob in Archive Tier 202 202 200
Blob in Archive tier rehydrating to Hot 202 409 409
Blob in Archive tier rehydrating to Cool 409 202 409

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

Response Headers

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

Response Header 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. This header is returned for requests made against version 2009-09-19 and newer.

Authorization

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

Remarks

Setting a blob's tier for page blobs in premium accounts have the following restrictions:

Setting the block blob's tier on a blob storage LRS accounts have the following restriction:

  • Setting the tier on a snapshot or a block blob with snapshots is not allowed.

The list of supported tiers is not restricted by the request version, and new tiers may be added in the future.

Note

Tiers on blob storage accounts are currently in preview. For detailed information about block blob level tiering see Hot, cool and archive storage tiers.

See Also

Authentication for the Azure Storage Services
Status and Error Codes
Blob Service Error Codes
Setting Timeouts for Blob Service Operations