Storage account antworkscmrplus , enabled Lifecycle management policy but data size is not going down

@Riju Kumar I hope you are doing well,

You shoud take a look Policy Scope and Filters

• Does the policy target the correct blob types (e.g. blockBlob)?

 Are prefixes or filters (like container name or blob name patterns) too narrow or missing?

• Is the policy set to delete or just move to cool/archive tier?

2. Verify the Age and Conditions of Blobs • Are the blobs old enough to meet the policy criteria (e.g., "delete after 30 days")? • Do the blobs have last modified dates that qualify?

Confirm Lifecycle Policy Execution Timing

•  Lifecycle policies run once every 24 hours. Changes are not immediate.

If recently enabled, wait at least 24–48 hours before expecting visible effects

😊 If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily. Thanks!

Hello @Riju Kumar,

Hope you're doing well!

Thank you for providing additional details regarding the discrepancy between the Azure Storage Insights report.

To assist you in identifying which container is contributing to the reported 140 GB, I recommend reviewing the following links, which provide detailed guidance on calculating container-level storage usage in Azure Blob Storage

https://techcommunity.microsoft.com/blog/azurepaasblog/calculating-container-level-stats-in-azure-blob-storage/3064312

https://docs.azure.cn/en-us/storage/scripts/storage-blobs-container-calculate-size-cli

https://techcommunity.microsoft.com/blog/azurepaasblog/calculate-the-sizecapacity-of-storage-account-and-it-services-blobtable/1064046

Kindly let us know if the above helps or you need further assistance on this issue.

Please "Accept the answer" if the information helped you. This will help us and others in the community as well