Lifecycle Management Rule Block Blob Deletion Limit?

Logesh J 0 Reputation points

How many number of blobs is supported to delete by Lifecycle Management Rule in single run ?

Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,898 questions
Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,602 questions
{count} votes

2 answers

Sort by: Most helpful
  1. SAMIT SARKAR 791 Reputation points Microsoft Employee

    Welcome to Microsoft Q&A platform and thanks for posting your question here.

    Azure Blob Storage's Lifecycle Management runs once a day and can define up to 100 rules. However, the specific number of blobs that can be deleted in a single run is not explicitly defined. It's designed to handle large amounts of data, so it should be able to manage a significant number of blobs. Please note that once you configure a policy, it can take up to 24 hours for some actions to run for the first time.

    Please refer

    Hope this helps.

    If you still have questions, please let us know in the "comments" and we would be happy to help you. Comment is the fastest way of notifying the experts.

    Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.


    0 comments No comments

  2. Anand Prakash Yadav 7,780 Reputation points Microsoft Vendor

    Hello Logesh J,

    Thank you for posting your query here!

    Azure Blob Storage Lifecycle Management Rules as such do not have a specified limit on the number of blobs that can be deleted in a single run.

    You can use Lifecycle Management Rules to set rules and perform delete actions to the filtered set of objects.

    Example: Delete blob 2,555 days (seven years) after last modification.

    When you configure or edit a lifecycle policy., it can take up to 24 hours for changes to go into effect and for the first execution to start.

    Please note that a lifecycle management policy will not delete the current version of a blob until any previous versions or snapshots associated with that blob have been deleted. If blobs in your storage account have previous versions or snapshots, then you should select Base blobs, Snapshots, and Versions in the Blob Subtype section when you are specifying a delete action as part of the policy.

    The current release supports delete operation for blockBlob and appendBlob.

    Also, the delete action of a lifecycle management policy won't work with any blob in an immutable container. With an immutable policy, objects can be created and read, but not modified or deleted. For more information, see Store business-critical blob data with immutable storage.

    Please let us know if you have any further queries. I’m happy to assist you further.

    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments