Azure Storage account tier availability

Artur Basinski 0 Reputation points
2025-08-04T09:24:28.7833333+00:00

Hi,

We plan on using Lifecycle policies in Azure Storage Account (ADLS).

I know there are different SLAs for tiers. The question is: if a blob is in cold tier and this tier is unavailable, can we move it to hot tier and the blob can be read again?

Would be grateful for some clarification on how tiers behave when something wrong is happening.

Thank you

Azure Data Lake Storage
Azure Data Lake Storage
An Azure service that provides an enterprise-wide hyper-scale repository for big data analytic workloads and is integrated with Azure Blob Storage.
{count} votes

1 answer

Sort by: Most helpful
  1. Shikha Ghildiyal 6,715 Reputation points Microsoft Employee Moderator
    2025-08-05T14:46:03.2166667+00:00

    Hi Artur Basinski

    Thanks for reaching out to Microsoft Q&A.

    Kindly go through this documentation for more details- https://learn.microsoft.com/en-us/azure/storage/blobs/lifecycle-management-overview?source=recommendationsAlso, Setting or changing a blob's tier as per doc- https://learn.microsoft.com/en-us/azure/storage/blobs/access-tiers-overview?source=recommendations

    To explicitly set a blob's tier when you create it, specify the tier when you upload the blob.

    After a blob is created, you can change its tier in either of the following ways:

    By calling the Set Blob Tier operation, either directly or via a lifecycle management policy. Calling Set Blob Tier is typically the best option when you're changing a blob's tier from a warmer tier to a cooler one.

    Note

    You can't rehydrate an archived blob to an online tier by using lifecycle management policies.

    By calling the Copy Blob operation to copy a blob from one tier to another. Calling Copy Blob is recommended for most scenarios where you're rehydrating a blob from the archive tier to an online tier, or moving a blob from cool or cold to hot. By copying a blob, you can avoid the early deletion penalty, if the required storage interval for the source blob hasn't yet elapsed. However, copying a blob results in capacity charges for two blobs, the source blob and the destination blob.

    Changing a blob's tier from a warmer tier to a cooler one is instantaneous, as is changing from cold or cool to hot. Rehydrating a blob from the archive tier to an online tier such as the hot, cool, or cold tier can take up to 15 hours.

    Keep in mind the following points when changing a blob's tier:

    You can't use Set Blob Tier to archive a a blob that uses an encryption scope. You can only use Set Blob Tier to move between online access tiers. For more information about encryption scopes, see Encryption scopes for Blob storage.

    If a blob is explicitly moved to the cool or cold tier and then moved to the archive tier, the early deletion charge applies.

    If a blob is explicitly moved to the cool or cold tier and then moved to the archive tier, the early deletion charge applies.

    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.