What is the default archive policy for azure storage blob service

Question

We are exploring azure storage blob APIs

1. Get Blob - https://learn.microsoft.com/en-us/rest/api/storageservices/get-blob?tabs=microsoft-entra-id
2. List Blob - https://learn.microsoft.com/en-us/rest/api/storageservices/list-blobs?tabs=microsoft-entra-id

Here, we wanted to know what will be the default archive policy for azure storage blob service and can we change manually or is there any way to change default duration of achieve policy

Answer 1

Hi,

Archive tier policy is working as follows:

Answer 2

@Ron Weasley In addition to information shared by Manu above on the default archive policy, you can configure lifecycle management policies to automatically transition blob data between hot, cool, cold, and archive tiers during its lifecycle. These policies are rule-based and allow you to define actions based on conditions such as the number of days since the blob was created, modified, or last accessed. For example, you can move a blob from the hot tier to the cool tier if it hasn’t been modified for a specified period.

While the default behavior follows the archive policy described above, you can customize it by creating your own lifecycle management policies. These policies allow you to set specific rules for transitioning data between tiers or expiring data based on your requirements. . If you need to change the default duration or create custom policies, you can do so using Azure Storage Explorer, Azure PowerShell, or Azure CLI.

Additional reading:

1. Access tiers for blob data
2. How to automate Azure Archive Storage to Cool/Hot tier conversion

---

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!