When does lifecycle policy changes run in the background?

Question

If I set lifecycle policy to change tier from Hot to Cold after 0, 5, or 10 days. What time after hitting that criteria does the tier get updated? I understand that it can take 24 hours for the policy to be effective, but once it does how often does it look for new files that match the criteria?

Answer 1

Thanks for posting your question in the Microsoft Q&A forum.

Once a lifecycle management policy is in effect for an Azure Storage account, it runs in the background on a daily basis. Here are the key points about when and how the policy changes are applied:

• Initial delay: After creating or updating a policy, it can take up to 24 hours for the changes to go into effect
• Daily execution: Once active, the lifecycle management policy runs once every 24 hours
• Evaluation timing: When the policy runs, it evaluates all blobs in the account against the defined rules
• Action timing: Blobs that meet the criteria will have the specified actions applied during that daily run
• Immediate actions: Some actions, like moving blobs from cool to hot tier when accessed, can happen immediately outside the daily policy run if configured

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful

Answer 2

Hi Walia, Deepak,
Azure Storage lifecycle management policies run on a daily basis, but the exact time of day when the evaluation and change process occurs is not fixed. The policy execution can happen at any time within the 24-hour period, and this timing is managed by the Azure platform itself

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful