COOL storage charged as HOT tier

Question

I have set the objects in my Blob from HOT to COOL tier. Partly manually using the storage explorer and partly using lifecycle management (life save for large amount of files!).

If I check my storage I see only COOL tiered files, which is what I wanted.

However if I go to cost management it only shows charges on HOT LRS and no charges on COOl LRS.

Access tier was changed between 14 and 7 days ago (not all in one go) but I always assumed going from Hot to cool was instant.

Does anyone have a clue what is going on?

Update after 1 week:

and now finally the transfer to cool is also visible in the costs. Over the course of 3 days I see that step by step all hot storage went to cool. It took 3-4 weeks from when I ordered it to go from hot to cool. It makes me wonder if it is some kind of anti-delete feature which prevents it from removing it from hot? Or does the lifecycle management only kick in after a few weeks?

Answer 1

@Sven ,
Thank you for reaching out to the Microsoft Q&A platform. Happy to answer your question.

Changing the default access tier setting for a storage account applies to all blobs in the account for which an access tier has not been explicitly set. If you toggle the default access tier setting from Hot to Cool in a general-purpose v2 account, then you are charged for write operations (per 10,000) for all blobs for which the access tier is inferred. The destination tier in your case was cool tier and hence you were charged with Cool Write Operations for hot->cool configuration change. For more information, please read the article.
https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-storage-tiers#blob-level-tiering-billing

Thanks

----------

Please "Accept as Answer" and Upvote if any of the above helped so that, it can help others in the community looking for remediation for similar issues.