Merge pull request #208202 from normesta/lifecycle-management

Content for tug-a-war changes

Author: v-regandowner

articles/storage/blobs/archive-blob.md

@@ -7,7 +7,7 @@ author: normesta
 
 ms.service: storage
 ms.topic: how-to
-ms.date: 07/21/2022
+ms.date: 08/24/2022
 ms.author: normesta
 ms.reviewer: fryu
 ms.subservice: blobs
@@ -285,29 +285,57 @@ You can use the Azure portal, PowerShell, Azure CLI, or an Azure Resource Manage
 
 To create a lifecycle management policy to archive blobs in the Azure portal, follow these steps:
 
+#### Step 1: Create the rule and specify the blob type
+
 1. Navigate to your storage account in the portal.
-1. Under **Data management**, locate the **Lifecycle management** settings.
-1. Select the **Add a rule** button.
-1. On the **Details** tab, specify a name for your rule.
-1. Specify the rule scope: either **Apply rule to all blobs in your storage account**, or **Limit blobs with filters**.
-1. Select the types of blobs for which the rule is to be applied, and specify whether to include blob snapshots or versions.
+
+2. Under **Data management**, locate the **Lifecycle management** settings.
+
+3. Select the **Add a rule** button.
+
+4. On the **Details** tab, specify a name for your rule.
+
+5. Specify the rule scope: either **Apply rule to all blobs in your storage account**, or **Limit blobs with filters**.
+
+6. Select the types of blobs for which the rule is to be applied, and specify whether to include blob snapshots or versions.
 
     :::image type="content" source="media/archive-blob/lifecycle-policy-details-tab-portal.png" alt-text="Screenshot showing how to configure a lifecycle management policy - Details tab.":::
 
+#### Step 2: Add rule conditions
+
 1. Depending on your selections, you can configure rules for base blobs (current versions), previous versions, or blob snapshots. Specify one of two conditions to check for:
 
     - Objects were last modified some number of days ago.
+    - Objects were created some number of days ago.
     - Objects were last accessed some number of days ago.
 
     Only one of these conditions can be applied to move a particular type of object to the Archive tier per rule. For example, if you define an action that archives base blobs if they haven't been modified for 90 days, then you can't also define an action that archives base blobs if they haven't been accessed for 90 days. Similarly, you can define one action per rule with either of these conditions to archive previous versions, and one to archive snapshots.
 
-1. Next, specify the number of days to elapse after the object is modified or accessed.
-1. Specify that the object is to be moved to the Archive tier after the interval has elapsed.
+8. Next, specify the number of days to elapse after the object is modified or accessed.
+
+9. Specify that the object is to be moved to the Archive tier after the interval has elapsed.
+
+    > [!div class="mx-imgBorder"]
+    > ![Screenshot showing how to configure a lifecycle management policy - Base blob tab.](./media/archive-blob/lifecycle-policy-base-blobs-tab-portal.png)
+
+10. If you chose to limit the blobs affected by the rule with filters, you can specify a filter, either with a blob prefix or blob index match.
+   
+#### Step 3: Ensure that the rule excludes rehydrated blobs
+
+If you rehydrate a blob by changing it's tier, this rule will move the blob back to the archive tier if the last modified time, creation time, or last access time is beyond the threshold set for the policy. 
+
+If you selected the **Last modified** rule condition, you can prevent this from happening by selecting **Skip blobs that have been rehydrated in the last**, and then entering the number of days you want a rehydrated blob to be excluded from this rule.
+
+> [!div class="mx-imgBorder"]
+> ![Screenshot showing the skip blobs that have been rehydrated in the last setting.](./media/archive-blob/lifecycle-policy-base-blobs-tab-portal-exclude-rehydrated-blobs.png)
+
+> [!NOTE]
+> This option appears only if you selected the **Last modified** rule condition.
+
+Select the **Add** button to add the rule to the policy.
 
-    :::image type="content" source="media/archive-blob/lifecycle-policy-base-blobs-tab-portal.png" alt-text="Screenshot showing how to configure a lifecycle management policy - Base blob tab.":::
 
-1. If you chose to limit the blobs affected by the rule with filters, you can specify a filter, either with a blob prefix or blob index match.
-1. Select the **Add** button to add the rule to the policy.
+#### View the policy JSON
 
 After you create the lifecycle management policy, you can view the JSON for the policy on the **Lifecycle management** page by switching from **List view** to **Code view**.
 
@@ -324,7 +352,8 @@ Here's the JSON for the simple lifecycle management policy created in the images
         "actions": {
           "baseBlob": {
             "tierToArchive": {
-              "daysAfterLastAccessTimeGreaterThan": 90
+              "daysAfterLastAccessTimeGreaterThan": 90,
+              "daysAfterLastTierChangeGreaterThan": 7
             }
           }
         },

articles/storage/blobs/archive-rehydrate-overview.md

@@ -5,7 +5,7 @@ services: storage
 author: normesta
 
 ms.author: normesta
-ms.date: 07/26/2022
+ms.date: 08/24/2022
 ms.service: storage
 ms.subservice: blobs
 ms.topic: conceptual
@@ -52,6 +52,7 @@ You must copy the archived blob to a new blob with a different name or to a diff
 Microsoft recommends performing a copy operation in most scenarios where you need to move a blob from the Archive tier to an online tier, for the following reasons:
 
 - A copy operation avoids the early deletion fee that is assessed if you change the tier of a blob from the Archive tier before the required 180-day period elapses. For more information, see [Archive access tier](access-tiers-overview.md#archive-access-tier).
+
 - If there's a lifecycle management policy in effect for the storage account, then rehydrating a blob with [Set Blob Tier](/rest/api/storageservices/set-blob-tier) can result in a scenario where the lifecycle policy moves the blob back to the Archive tier after rehydration because the last modified time is beyond the threshold set for the policy. A copy operation leaves the source blob in the Archive tier and creates a new blob with a different name and a new last modified time, so there's no risk that the rehydrated blob will be moved back to the Archive tier by the lifecycle policy.
 
 Copying a blob from the Archive tier can take hours to complete depending on the rehydration priority selected. Behind the scenes, a blob copy operation reads your archived source blob to create a new online blob in the selected destination tier. The new blob may be visible when you list the blobs in the parent container before the rehydration operation is complete, but its tier will be set to Archive. The data isn't available until the read operation from the source blob in the Archive tier is complete and the blob's contents have been written to the new destination blob in an online tier. The new blob is an independent copy, so modifying or deleting it doesn't affect the source blob in the Archive tier.
@@ -88,9 +89,9 @@ Once a [Set Blob Tier](/rest/api/storageservices/set-blob-tier) request is initi
 To learn how to rehydrate a blob by changing its tier to an online tier, see [Rehydrate a blob by changing its tier](archive-rehydrate-to-online-tier.md#rehydrate-a-blob-by-changing-its-tier).
 
 > [!CAUTION]
-> Changing a blob's tier doesn't affect its last modified time. If there is a [lifecycle management](./lifecycle-management-overview.md) policy in effect for the storage account, then rehydrating a blob with **Set Blob Tier** can result in a scenario where the lifecycle policy moves the blob back to the Archive tier after rehydration because the last modified time is beyond the threshold set for the policy.
+> Changing a blob's tier doesn't affect its last modified time. If there is a [lifecycle management](./lifecycle-management-overview.md) policy in effect for the storage account, then rehydrating a blob with **Set Blob Tier** can result in a scenario where the lifecycle policy moves the blob back to the Archive tier after rehydration because the last modified time is beyond the threshold set for the policy. 
 >
-> To avoid this scenario, rehydrate the archived blob by copying it instead, as described in the [Copy an archived blob to an online tier](#copy-an-archived-blob-to-an-online-tier) section. Performing a copy operation creates a new instance of the blob with an updated last modified time, so it won't trigger the lifecycle management policy.
+> To avoid this scenario, add the `daysAfterLastTierChangeGreaterThan` condition to the `tierToArchive` action of the policy. Alternatively, you can rehydrate the archived blob by copying it instead, as described in the [Copy an archived blob to an online tier](#copy-an-archived-blob-to-an-online-tier) section. Performing a copy operation creates a new instance of the blob with an updated last modified time, so it won't trigger the lifecycle management policy.
 
 ## Check the status of a blob rehydration operation
 

articles/storage/blobs/archive-rehydrate-to-online-tier.md

@@ -7,7 +7,7 @@ author: normesta
 
 ms.service: storage
 ms.topic: how-to
-ms.date: 07/26/2022
+ms.date: 08/24/2022
 ms.author: normesta
 ms.reviewer: fryu
 ms.custom: devx-track-azurepowershell
@@ -18,7 +18,7 @@ ms.subservice: blobs
 
 To read a blob that is in the Archive tier, you must first rehydrate the blob to an online tier (Hot or Cool) tier. You can rehydrate a blob in one of two ways:
 
-- By copying it to a new blob in the Hot or Cool tier with the [Copy Blob](/rest/api/storageservices/copy-blob) operation. Microsoft recommends this option for most scenarios.
+- By copying it to a new blob in the Hot or Cool tier with the [Copy Blob](/rest/api/storageservices/copy-blob) operation. 
 - By changing its tier from Archive to Hot or Cool with the [Set Blob Tier](/rest/api/storageservices/set-blob-tier) operation.
 
 When you rehydrate a blob, you can specify the priority for the operation to either standard priority or high priority. A standard-priority rehydration operation may take up to 15 hours to complete. A high-priority operation is prioritized over standard-priority requests and may complete in less than one hour for objects under 10 GB in size. You can change the rehydration priority from *Standard* to *High* while the operation is pending.

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: 05/09/2022
+ms.date: 08/24/2022
 ms.service: storage
 ms.subservice: common
 ms.topic: conceptual
@@ -101,7 +101,8 @@ The following sample rule filters the account to run the actions on objects that
               "daysAfterModificationGreaterThan": 30
             },
             "tierToArchive": {
-              "daysAfterModificationGreaterThan": 90
+              "daysAfterModificationGreaterThan": 90,
+              "daysAfterLastTierChangeGreaterThan": 7
             },
             "delete": {
               "daysAfterModificationGreaterThan": 2555
@@ -164,6 +165,7 @@ 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 |
+| 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. |
 
 ## Examples of lifecycle policies
 
@@ -235,7 +237,7 @@ In the following example, blobs are moved to cool storage if they haven't been a
 
 ### Archive data after ingest
 
-Some data stays idle in the cloud and is rarely, if ever, accessed. The following lifecycle policy is configured to archive data shortly after it's ingested. This example transitions block blobs in a container named `archivecontainer` into an archive tier. The transition is accomplished by acting on blobs 0 days after last modified time:
+Some data stays idle in the cloud and is rarely, if ever, accessed. The following lifecycle policy is configured to archive data shortly after it's ingested. This example transitions block blobs in a container named `archivecontainer` into an archive tier. The transition is accomplished by acting on blobs 0 days after last modified time. 
 
 ```json
 {
@@ -251,7 +253,9 @@ Some data stays idle in the cloud and is rarely, if ever, accessed. The followin
         },
         "actions": {
           "baseBlob": {
-              "tierToArchive": { "daysAfterModificationGreaterThan": 0 }
+              "tierToArchive": { 
+                "daysAfterModificationGreaterThan": 0
+              }
           }
         }
       }
@@ -387,9 +391,15 @@ The platform runs the lifecycle policy once a day. Once you configure a policy,
 
 The updated policy takes up to 24 hours to go into effect. Once the policy is in effect, it could take up to 24 hours for the actions to run. Therefore, the policy actions may take up to 48 hours to complete. If the update is to disable or delete a rule, and enableAutoTierToHotFromCool was used, auto-tiering to Hot tier will still happen. For example, set a rule including enableAutoTierToHotFromCool based on last access. If the rule is disabled/deleted, and a blob is currently in cool and then accessed, it will move back to Hot as that is applied on access outside of lifecycle management. The blob won't then move from Hot to Cool given the lifecycle management rule is disabled/deleted. The only way to prevent autoTierToHotFromCool is to turn off last access time tracking.
 
-### I manually rehydrated an archived blob. How do I prevent it from being moved back to the Archive tier temporarily?
+### I rehydrated an archived blob. How do I prevent it from being moved back to the Archive tier temporarily?
 
-When a blob is moved from one access tier to another, its last modification time doesn't change. If you manually rehydrate an archived blob to hot tier, it would be moved back to archive tier by the lifecycle management engine. Disable the rule that affects this blob temporarily to prevent it from being archived again. Re-enable the rule when the blob can be safely moved back to archive tier. You may also copy the blob to another location if it needs to stay in hot or cool tier permanently.
+If there's a lifecycle management policy in effect for the storage account, then rehydrating a blob by changing it's tier can result in a scenario where the lifecycle policy moves the blob back to the archive tier. This can happen if the last modified time, creation time, or last access time is beyond the threshold set for the policy. There's three ways to prevent this from happening:
+
+- Add the `daysAfterLastTierChangeGreaterThan` condition to the tierToArchive action of the policy. This condition applies only to the last modified time. See [Use lifecycle management policies to archive blobs](archive-blob.md#use-lifecycle-management-policies-to-archive-blobs).
+
+- Disable the rule that affects this blob temporarily to prevent it from being archived again. Re-enable the rule when the blob can be safely moved back to archive tier. 
+
+- If the blob needs to stay in the hot or cool tier permanently, copy the blob to another location where the lifecycle manage policy is not in effect.
 
 ### The blob prefix match string didn't apply the policy to the expected blobs
 

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

@@ -38,7 +38,8 @@ To enable last access time tracking with the Azure portal, follow these steps:
 1. Navigate to your storage account in the Azure portal.
 1. In the **Data management** section, select **Lifecycle management**.
 
-    :::image type="content" source="media/lifecycle-management-policy-configure/last-access-tracking-enable.png" alt-text="Screenshot showing how to enable last access tracking in Azure portal":::
+   > [!div class="mx-imgBorder"]
+   > ![Screenshot showing how to enable last access tracking in Azure portal.](media/lifecycle-management-policy-configure/last-access-tracking-enable.png)
 
 #### [PowerShell](#tab/azure-powershell)