- You can read files directly from the Cool or cold Tier without needing to move them to the Hot Tier.
- Changing a blob's tier from a cold or cool to hot is instantaneous. Data in the cool tier should be stored for a minimum of 30 days while data in the cold tier should be stored for a minimum of 90 days.
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.
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.
Pricing
Data access charges increase as the tier gets cooler. For data in the cool, cold and archive access tier, you're charged a per-gigabyte data access charge for reads.
Billing impacts when changing a blob's tier
Additional reading:
Best practices for using blob access tiers
If you have any questions, let me know in the "comments" and I would be happy to help you. Comment is the fastest way of notifying the experts.
If the answer has been helpful, we appreciate hearing from you and would love to help others who may have the same question. Accepting answers helps increase the visibility of this question for other members of the Microsoft Q&A community.
Thank you for helping to improve Microsoft Q&A!