@Alberto Mijares Thanks for reaching out to Microsoft Q&A.
Yes, that is correct. When you upload a new version of a blob using the "Rewrite" option, the previous version of the blob will be deleted, and a new blob will be created in the same container. If the container has a default access tier of "Hot", then the new blob will be created in the "Hot" tier. However, if the blob was originally created in the "Cool" tier, then it will remain in the "Cool" tier even if the container's default access tier is "Hot".
This is because the blob's access tier is determined by the tier it was created in, not the container's default access tier. To change the access tier of an existing blob, you can use the "Set Blob Tier" operation or the "Copy Blob" operation. Keep in mind that changing a blob's tier from "Cool" to "Hot" or "Archive" will incur additional charges.
You can also use a lifecycle management policy to automatically move blobs between access tiers based on their age or last modified time. This can help you optimize your storage costs by moving older or infrequently accessed blobs to cooler tiers. document_link: https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/access-tiers-overview.md
Hope this helps. Please let us know if you have any more questions and we will be glad to assist you further. Thank you!
Remember:
Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.
Want a reminder to come back and check responses? Here is how to subscribe to a notification.