You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Azure Blob Storage empowers organizations to efficiently manage and scale their data storage needs, even as data volumes grow and usage patterns evolve. Leveraging blob lifecycle management, customers can proactively optimize costs by implementing rule-based policies that automatically transition data to cooler tiers or expire it when it is no longer needed. This seamless automation ensures that data is always stored in the most cost-effective manner, maximizing budget efficiency while maintaining easy access and robust data management. With blob lifecycle management, organizations can confidently scale their storage environments, knowing that their costs are optimized and their data is managed according to real-world usage.
16
+
Azure Blob Storage empowers organizations to efficiently manage and scale their data storage needs, even as data volumes grow and usage patterns evolve. By leveraging blob lifecycle management, customers can proactively optimize costs by implementing rule-based policies that automatically transition data to cooler tiers or expire it when it is no longer needed. This seamless automation ensures that data is always stored in the most cost-effective manner which maximizes budget efficiency while maintaining easy access and robust data management. With blob lifecycle management, organizations can confidently scale their storage environments, knowing that their costs are optimized and their data is managed according to real-world usage.
17
17
18
18
With the lifecycle management policy, you can:
19
19
@@ -31,11 +31,11 @@ A lifecycle management policy is a collection of rules in a JSON document. To le
31
31
32
32
Lifecycle management policies are supported for block blobs and append blobs in general-purpose v2, premium block blob, and Blob Storage accounts. Lifecycle management doesn't affect system containers such as the $logs or $web containers.
33
33
34
-
A *rule* is a definition of the conditions, the associated actions and filters that are to be implemented. The following table describes each element.
34
+
A *rule* is a definition of the conditions, along with the associated actions and filters that will be used to process objects. The following table describes each rule element.
35
35
36
36
| Rule element | Description |
37
37
|---|---|
38
-
| Conditions | Conditions are based on the following limited set of blob properties which include Creation Time, Last Modified Time and Last Accessed Time (if access time tracking is enabled).|
38
+
| Conditions | Conditions are based on the following three blob properties: Creation Time, Last Modified Time and Last Accessed Time (if access time tracking is enabled) |
39
39
| Actions | Actions are applied to the filtered blobs that meet the associated conditions. You must define at least one action per rule such as changing the blob tier to the cool tier or deleting blobs. |
40
40
| Filters | Filters limit rule actions to a subset of blobs within the storage account by using path prefixes and blob tags. If more than one filter is defined, a logical AND runs on all filters. You can use a filter to specify which blobs to include. A filter provides no means to specify which blobs to exclude. |
0 commit comments