Merge pull request #222183 from jimmart-dev/jammart-lcm-last-accessed-time-clarify

blobs-lifecycle-mgmt-clarify last accessed time behavior

Author: prmerger-automator[bot]

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

@@ -5,7 +5,7 @@ description: Use Azure Storage lifecycle management policies to create automated
 author: normesta
 
 ms.author: normesta
-ms.date: 09/29/2022
+ms.date: 12/21/2022
 ms.service: storage
 ms.subservice: common
 ms.topic: conceptual
@@ -170,9 +170,11 @@ The run conditions are based on age. Current versions use the last modified time
 |--|--|--|
 | daysAfterModificationGreaterThan | Integer value indicating the age in days | The condition for actions on a current version of a blob |
 | daysAfterCreationGreaterThan | Integer value indicating the age in days | The condition for actions on a previous version of a blob or a blob snapshot |
-| daysAfterLastAccessTimeGreaterThan | Integer value indicating the age in days | The condition for a current version of a blob when access tracking is enabled |
+| daysAfterLastAccessTimeGreaterThan<sup>1</sup> | Integer value indicating the age in days | The condition for a current version of a blob when access tracking is enabled |
 | daysAfterLastTierChangeGreaterThan | Integer value indicating the age in days after last blob tier change time | This condition applies only to `tierToArchive` actions and can be used only with the `daysAfterModificationGreaterThan` condition. |
 
+<sup>1</sup> If [last access time tracking](#move-data-based-on-last-accessed-time) is not enabled for a blob, **daysAfterLastAccessTimeGreaterThan** uses the date the lifecycle policy was enabled instead of the `LastAccessTime` property of the blob.
+
 ## Examples of lifecycle policies
 
 The following examples demonstrate how to address common scenarios with lifecycle policy rules.
@@ -213,6 +215,8 @@ When last access time tracking is enabled, the blob property called `LastAccessT
 
 To minimize the effect on read access latency, only the first read of the last 24 hours updates the last access time. Subsequent reads in the same 24-hour period don't update the last access time. If a blob is modified between reads, the last access time is the more recent of the two values.
 
+If last access time tracking is enabled for a blob, lifecycle management uses `LastAccessTime` to determine whether the run condition **daysAfterLastAccessTimeGreaterThan** is met. If last access time tracking is not enabled, it uses the date the lifecycle policy was enabled instead of `LastAccessTime`.
+
 In the following example, blobs are moved to cool storage if they haven't been accessed for 30 days. The `enableAutoTierToHotFromCool` property is a Boolean value that indicates whether a blob should automatically be tiered from cool back to hot if it's accessed again after being tiered to cool.
 
 ```json

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

@@ -5,7 +5,7 @@ description: Configure a lifecycle management policy to automatically move data
 author: normesta
 
 ms.author: normesta
-ms.date: 09/16/2022
+ms.date: 12/21/2022
 ms.service: storage
 ms.subservice: common
 ms.topic: conceptual
@@ -22,7 +22,7 @@ A lifecycle management policy is comprised of one or more rules that define a se
 
 - The number of days since the blob was created.
 - The number of days since the blob was last modified.
-- The number of days since the blob was last accessed. To use this condition in an action, you must first [optionally enable access time tracking](#optionally-enable-access-time-tracking).
+- The number of days since the blob was last accessed. To use this condition in an action, you should first [optionally enable last access time tracking](#optionally-enable-access-time-tracking).
 
 When the selected condition is true, then the management policy performs the specified action. For example, if you have defined an action to move a blob from the hot tier to the cool tier if it has not been modified for 30 days, then the lifecycle management policy will move the blob 30 days after the last write operation to that blob.