Skip to content

Commit 0621f8e

Browse files
committed
fixing something
1 parent 2eb8c67 commit 0621f8e

File tree

2 files changed

+3
-5
lines changed

2 files changed

+3
-5
lines changed

articles/storage/blobs/lifecycle-management-overview.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -77,8 +77,6 @@ For more information about pricing, see [Block Blob pricing](https://azure.micro
7777

7878
- 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](./immutable-storage-overview.md).
7979

80-
- Blobs can automatically tier up from cool to hot only once in 30 days. This safeguard is put into place to protect against multiple early deletion penalties charged to the account.
81-
8280
- Lifecycle management doesn't affect system containers such as the $logs or $web containers.
8381

8482
## Frequently asked questions (FAQ)

articles/storage/blobs/lifecycle-management-policy-structure.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
fy23---
1+
---
22
title: Azure Blob Storage lifecycle management policy structure
33
titleSuffix: Azure Blob Storage
44
description: Learn more about the elements of a lifecycle management policy.
@@ -86,8 +86,8 @@ You must define at least one action for each rule. Actions are applied to the fi
8686
|---|---|
8787
| **TierToCool** | Set a blob to the cool access tier.<br><br>Not supported with append blobs, page blobs, or with blobs in a premium block blob storage account.|
8888
| **TierToCold** | Set a blob to the cold access tier.<br><br>Not supported with append blobs, page blobs, or with blobs in a premium block blob storage account.|
89-
| **TierToArchive** | Set a blob to the archive access tier.<br>Rehydrating objects does not the object's last modified or last access time properties. As a result, this action can move objects back to the archive tier because the the last modified time or last access time continues to be beyond the threshold set for the rule. To avoid this scenario, add the `daysAfterLastTierChangeGreaterThan` condition to this action.<br>This action is not supported with append blobs, page blobs, or with blobs in a premium block blob storage account. Also not supported with blobs that use an encryption scope or with blobs in accounts that are configured for Zone-redundant storage (ZRS), geo-zone-redundant storage (GZRS) / read-access geo-zone-redundant storage (RA-GZRS).|
90-
| **enableAutoTierToHotFromCool** | If a blob is set to the cool tier, this action automatically moves that blob into the hot tier when the blob is accessed.<br>This action is available only when used with the **daysAfterLastAccessTimeGreaterThan** run condition. This action has no effect on blobs that were set to the cool tier prior to enabling this action in a rule. If an object was already set to the cool tier before the rule was enabled, and that object is accessed, it remains in the cool tier and is not automatically moved to the hot tier.<br><br>Not supported with previous versions or snapshots. |
89+
| **TierToArchive** | Set a blob to the archive access tier.<br><br>Rehydrating objects does not the object's last modified or last access time properties. As a result, this action can move objects back to the archive tier because the the last modified time or last access time continues to be beyond the threshold set for the rule. To avoid this scenario, add the `daysAfterLastTierChangeGreaterThan` condition to this action.<br><br>This action is not supported with append blobs, page blobs, or with blobs in a premium block blob storage account. Also not supported with blobs that use an encryption scope or with blobs in accounts that are configured for Zone-redundant storage (ZRS), geo-zone-redundant storage (GZRS) / read-access geo-zone-redundant storage (RA-GZRS).|
90+
| **enableAutoTierToHotFromCool** | If a blob is set to the cool tier, this action automatically moves that blob into the hot tier when the blob is accessed.<br><br>This action is available only when used with the **daysAfterLastAccessTimeGreaterThan** run condition. This action has no effect on blobs that were set to the cool tier prior to enabling this action in a rule. If an object was already set to the cool tier before the rule was enabled, and that object is accessed, it remains in the cool tier and is not automatically moved to the hot tier. This action moves blobs from cool to hot only one time in 30 days. This safeguard is put into place to protect against multiple early deletion penalties charged to the account.<br><br>Not supported with previous versions or snapshots. |
9191
| **Delete** | Deletes a blob.<br><br>Not supported with page blobs or blobs in an immutable container.|
9292

9393
If you define more than one action on the same blob, then lifecycle management applies the least expensive action to the blob. For example, a **delete** action is cheaper than the **tierToArchive** action and the **tierToArchive** action is cheaper than the **tierToCool** action.

0 commit comments

Comments
 (0)