An Azure service that stores unstructured data in the cloud as blobs.
Hi Catheryn Kidwell,
Thanks for reaching out in Microsoft Q&A forum,
If I used the hot tier instead of cool could I restore it back to archive tier immediately? I would also like to avoid being penalized for moving storage tier in less than 30 days. Guidance around managing data after restoring would be appreciated.
You can safely return your restored data to the archive tier right away, even if you upload it to hot first, without triggering any 30-day penalties. Just follow a simple workflow to keep costs low and avoid issues.
Steps:
Upload the folder directly to the Hot tier (not Cool), verify your data is intact, then immediately change it to Archive using the Azure portal, CLI, or PowerShell. Hot tier has no minimum storage duration, so there's no early deletion fee when moving to Archive.
Here's the CLI example for a single blob (adapt for batch):
az storage blob set-tier --account-name <storage-account> --container-name <container> --name <blob> --tier Archive --auth-mode login
For folders, use az storage blob upload-batch to Hot first, then bulk set-tier.
No Penalties Hit You
- Hot → Archive: Instant and free of fees (no 30/90/180-day minimums apply here).
- Cool would penalize: If you'd gone Cool → Archive within 30 days, you'd pay prorated Cool storage for remaining days.
- Your original rehydration to Cool was fine for download; now treat this as fresh data in Hot.
Post-Restoration
Keep rarely accessed data in Hot briefly (minutes) for checks, then archive. Set up lifecycle policies to automate Hot > Archive after 0 days for future-proofing. Monitor bills in Azure Cost Management to confirm no surprises.
Official Docs:
Kindly let us know if the above helps or you need further assistance on this issue.
Please do not forget to
and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.