Azure Storage - Life Cycle Management Rules are not working

Hi Murty Addanki ,

Thank you for reaching out on Microsoft Q&A forum.

Azure Blob Storage lifecycle management relies on the concept of prefix matching, which is essentially a string-based path filter used to determine which blobs a policy should apply to. In Azure, there are no real physical folders; instead, a virtual directory structure is created using blob names separated by “/”, and lifecycle rules operate on these prefixes rather than actual directories.

A blob prefix must always begin with the container name followed by the folder path, forming a structure like container-name/folder-path/. For example, specifying container1/ targets all blobs within that container, whereas container1/logs/ applies only to blobs that start with that path, including everything under that “folder” and its subfolders. This works because prefix matching is hierarchical—once a prefix is matched, all blobs with names starting with that prefix are included automatically. [docs.azure.cn],

Lifecycle policies are defined in JSON and include filters such as prefixMatch, which restrict actions (like tiering or deletion) to specific blobs. For instance, a rule using "prefixMatch": ["container1/logs/"] will only apply to blobs stored under the logs path in that container. These rules can then perform actions like moving data to cool or archive tiers or deleting it after defined time intervals, enabling automated cost optimization across the data lifecycle. [learn.microsoft.com]

In your case, the issue was resolved after correcting the blob prefix path, which indicates that the lifecycle rule was previously not matching the intended blobs. This typically happens when the prefix is slightly incorrect—such as using the wrong folder name, missing the container name, incorrect case sensitivity, or not aligning exactly with the actual blob path. Since prefix matching is strictly string-based and case-sensitive, even a small mismatch prevents the rule from applying. Once the correct prefix (including the proper container and folder structure) was provided, the lifecycle policy successfully identified and processed the targeted blobs, thereby resolving the issue.

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

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".