Skip to content

Commit fa43b34

Browse files
authored
Update 5-add-blob-lifecycle-management-rules.md
1 parent 625591c commit fa43b34

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

learn-pr/wwl-azure/configure-blob-storage/includes/5-add-blob-lifecycle-management-rules.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,19 @@
11
Every data set has a unique lifecycle. Early in the lifecycle, users tend to access some of the data in the set, but not all of the data. As the data set ages, access to all of the data in the set tends to dramatically reduce. Some data set stays idle in the cloud and is rarely accessed. Some data expires within a few days or months after creation. Other data is actively read and modified throughout the data set lifetime.
22

3-
Azure Blob Storage supports [lifecycle management](/azure/storage/blobs/lifecycle-management-policy-configure) for data sets. It offers a rich rule-based policy for GPv2 and Blob Storage accounts. You can use lifecycle policy rules to transition your data to the appropriate access tiers, and set expiration times for the end of a data set's lifecycle.
3+
Azure Blob Storage supports [lifecycle management](/azure/storage/blobs/lifecycle-management-policy-configure) for data sets. It offers a rich rule-based policy for GPv2 accounts and Premium block blob accounts. Legacy Blob Storage accounts are also supported, but GPv2 is recommended for new deployments. You can use lifecycle policy rules to transition your data to the appropriate access tiers, and set expiration times for the end of a data set's lifecycle.
44

55
> [!VIDEO https://learn-video.azurefd.net/vod/player?id=ce48b339-bc3a-412a-bf97-fb8581084431]
66
77
### Things to know about lifecycle management
88

99
You can use Azure Blob Storage lifecycle management policy rules to accomplish several tasks.
1010

11-
- Transition blobs to a cooler storage tier (Hot to Cool, Hot to Archive, Cool to Archive) to optimize for performance and cost.
11+
- Transition blobs to a cooler storage tier (Hot to Cool, Hot to Cold, Hot to Archive, Cool to Cold, Cool to Archive, Cold to Archive) to optimize for performance and cost.
1212

1313
- Delete current versions of a blob, previous versions of a blob, or blob snapshots at the end of their lifecycles.
1414

15+
- Automatically transition blobs from Cool back to Hot when accessed. This setting optimizes for unpredictable access patterns without early deletion charges.
16+
1517
- Apply rules to an entire storage account, to select containers, or to a subset of blobs using name prefixes or blob index tags as filters.
1618

1719
#### Business scenario

0 commit comments

Comments
 (0)