Merge pull request #190080 from tamram/tamram22-0228

blob archive & rehydration - incorporate final feedback

Author: AnnaMHuff

articles/storage/blobs/access-tiers-overview.md

@@ -37,11 +37,13 @@ Usage scenarios for the Cool access tier include:
 - Older data sets that are not used frequently, but are expected to be available for immediate access.
 - Large data sets that need to be stored in a cost-effective way while additional data is being gathered for processing.
 
+To learn how to move a blob to the Hot or Cool tier, see [Set a blob's access tier](access-tiers-online-manage.md).
+
 Data in the Cool tier has slightly lower availability, but offers the same high durability, retrieval latency, and throughput characteristics as the Hot tier. For data in the Cool tier, slightly lower availability and higher access costs may be acceptable trade-offs for lower overall storage costs, as compared to the Hot tier. For more information, see [SLA for storage](https://azure.microsoft.com/support/legal/sla/storage/v1_5/).
 
 A blob in the Cool tier in a general-purpose v2 accounts is subject to an early deletion penalty if it is deleted or moved to a different tier before 30 days has elapsed. This charge is prorated. For example, if a blob is moved to the Cool tier and then deleted after 21 days, you'll be charged an early deletion fee equivalent to 9 (30 minus 21) days of storing that blob in the Cool tier.
 
-The Hot and Cool tiers support all redundancy configurations. For more information about data redundancy options in Azure Storage, see [Azure Storage redundancy](../common/storage-redundancy.md).  
+The Hot and Cool tiers support all redundancy configurations. For more information about data redundancy options in Azure Storage, see [Azure Storage redundancy](../common/storage-redundancy.md).
 
 ## Archive access tier
 
@@ -51,6 +53,8 @@ The Archive tier is an offline tier for storing data that is rarely accessed. Th
 - Original (raw) data that must be preserved, even after it has been processed into final usable form
 - Compliance and archival data that needs to be stored for a long time and is hardly ever accessed
 
+To learn how to move a blob to the Archive tier, see [Archive a blob](archive-blob.md).
+
 Data must remain in the Archive tier for at least 180 days or be subject to an early deletion charge. For example, if a blob is moved to the Archive tier and then deleted or moved to the Hot tier after 45 days, you'll be charged an early deletion fee equivalent to 135 (180 minus 45) days of storing that blob in the Archive tier.
 
 While a blob is in the Archive tier, it can't be read or modified. To read or download a blob in the Archive tier, you must first rehydrate it to an online tier, either Hot or Cool. Data in the Archive tier can take up to 15 hours to rehydrate, depending on the priority you specify for the rehydration operation. For more information about blob rehydration, see [Overview of blob rehydration from the Archive tier](archive-rehydrate-overview.md).
@@ -202,6 +206,6 @@ For information about feature support by region, see [Azure products available b
 
 ## Next steps
 
-- [How to manage the tier of a blob in an Azure Storage account](manage-access-tier.md)
-- [How to manage the default account access tier of an Azure Storage account](../common/manage-account-default-access-tier.md)
-- [Optimize costs by automating Azure Blob Storage access tiers](./lifecycle-management-overview.md)
+- [Set a blob's access tier](access-tiers-online-manage.md)
+- [Archive a blob](archive-blob.md)
+- [Optimize costs by automatically managing the data lifecycle](lifecycle-management-overview.md)

articles/storage/blobs/archive-blob.md

@@ -7,7 +7,7 @@ author: tamram
 
 ms.service: storage
 ms.topic: how-to
-ms.date: 10/25/2021
+ms.date: 03/01/2022
 ms.author: tamram
 ms.reviewer: fryu
 ms.subservice: blobs
@@ -94,6 +94,16 @@ az storage blob upload-batch \
     --auth-mode login
 ```
 
+### [AzCopy](#tab/azcopy)
+
+To archive a single blob on upload with AzCopy, call the [azcopy copy](../common/storage-ref-azcopy-copy.md) command. Provide a local file as the source and the target blob URI as the destination, and specify the Archive tier as the target tier, as shown in the following example. Remember to replace the placeholder values in brackets with your own values:
+
+```azcopy
+azcopy copy "C:\temp\myTextFile.txt" "https://<storage-account>.blob.core.windows.net/<container>/myTextFile-archived.txt" --blob-type BlockBlob --block-blob-tier Archive
+```
+
+For additional examples, see [Upload files to Azure Blob storage by using AzCopy](../common/storage-use-azcopy-blobs-upload.md).
+
 ---
 
 ## Archive an existing blob
@@ -158,6 +168,10 @@ az storage blob set-tier \
     --auth-mode login
 ```
 
+### [AzCopy](#tab/azcopy)
+
+N/A
+
 ---
 
 ### Archive an existing blob with a copy operation
@@ -172,7 +186,7 @@ N/A
 
 #### [PowerShell](#tab/azure-powershell)
 
-To copy an blob from an online tier to the Archive tier with PowerShell, call the [Start-AzStorageBlobCopy](/powershell/module/az.storage/start-azstorageblobcopy) command and specify the Archive tier. Remember to replace placeholders in angle brackets with your own values:
+To copy a blob from an online tier to the Archive tier with PowerShell, call the [Start-AzStorageBlobCopy](/powershell/module/az.storage/start-azstorageblobcopy) command and specify the Archive tier. Remember to replace placeholders in angle brackets with your own values:
 
 ```azurepowershell
 # Initialize these variables with your values.
@@ -188,7 +202,7 @@ $ctx = (Get-AzStorageAccount `
         -ResourceGroupName $rgName `
         -Name $accountName).Context
 
-# Copy the source blob to a new destination blob in Hot tier with Standard priority.
+# Copy the source blob to a new destination blob in Archive tier.
 Start-AzStorageBlobCopy -SrcContainer $srcContainerName `
     -SrcBlob $srcBlobName `
     -DestContainer $destContainerName `
@@ -199,7 +213,7 @@ Start-AzStorageBlobCopy -SrcContainer $srcContainerName `
 
 #### [Azure CLI](#tab/azure-cli)
 
-To copy an blob from an online tier to the Archive tier with Azure CLI, call the [az storage blob copy start](/cli/azure/storage/blob/copy#az_storage_blob_copy_start) command and specify the Archive tier. Remember to replace placeholders in angle brackets with your own values:
+To copy a blob from an online tier to the Archive tier with Azure CLI, call the [az storage blob copy start](/cli/azure/storage/blob/copy#az_storage_blob_copy_start) command and specify the Archive tier. Remember to replace placeholders in angle brackets with your own values:
 
 ```azurecli
 az storage blob copy start \
@@ -212,6 +226,18 @@ az storage blob copy start \
     --auth-mode login
 ```
 
+#### [AzCopy](#tab/azcopy)
+
+To copy a blob from an online tier to the Archive tier with AzCopy, specify the URI for the source blob and the URI for the destination blob. The destination blob should have a different name from the source blob, and should not already exist.
+
+When the copy source is a blob, you must provide an account SAS token on the source blob. If you are using Azure Active Directory (Azure AD) to authorize the copy operation, then the SAS is required only on the source blob, as shown in the following example. If you are using the account access key to authorize the copy operation, then you must provide a SAS token on both the source and destination blobs. For more information, see [Copy blobs between Azure storage accounts by using AzCopy](../common/storage-use-azcopy-blobs-copy.md).
+
+Remember to replace placeholders in angle brackets with your own values:
+
+```azcopy
+azcopy copy "https://<source-account>.blob.core.windows.net/sample-container/blob1.txt?sv=2020-08-04&ss=b&srt=sco&sp=r&se=2022-03-02T05:21:32Z&st=2022-03-01T21:21:32Z&spr=https&sig=<signature>" "https://<dest-account>.blob.core.windows.net/sample-container/blob1-archived.txt" --blob-type BlockBlob --block-blob-tier Archive
+```
+
 ---
 
 ## Bulk archive
@@ -224,6 +250,73 @@ To archive blobs with a batch operation, use one of the Azure Storage client lib
 
 For an in-depth sample application that shows how to change tiers with a batch operation, see [AzBulkSetBlobTier](/samples/azure/azbulksetblobtier/azbulksetblobtier/).
 
+## Use lifecycle management policies to archive blobs
+
+You can optimize costs for blob data that is rarely accessed by creating lifecycle management policies that automatically move blobs to the Archive tier when they have not been accessed or modified for a specified period of time. After you configure a lifecycle management policy, Azure Storage runs it once per day. For more information about lifecycle management policies, see [Optimize costs by automatically managing the data lifecycle](lifecycle-management-overview.md).
+
+You can use the Azure portal, PowerShell, Azure CLI, or an Azure Resource Manager template to create a lifecycle management policy. For simplicity, this section shows how to create a lifecycle management policy in the Azure portal only. For additional examples showing how to create lifecycle management policies, see [Configure a lifecycle management policy](lifecycle-management-policy-configure.md).
+
+> [!CAUTION]
+> Before you use a lifecycle management policy to move data to the Archive tier, verify that that data does not need to be deleted or moved to another tier for at least 180 days. Data that is deleted or moved to a different tier before the 180 day period has elapsed is subject to an early deletion fee.
+>
+> Also keep in mind that data in the Archive tier must be rehydrated before it can be read or modified. Rehydrating a blob from the Archive tier can take several hours and has associated costs.
+
+To create a lifecycle management policy to archive blobs in the Azure portal, follow these steps:
+
+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.
+
+    :::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.":::
+
+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 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 have not been modified for 90 days, then you cannot also define an action that archives base blobs if they have not 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.
+
+    :::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.
+
+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**.
+
+Here's the JSON for the simple lifecycle management policy created in the images shown above:
+
+```json
+{
+  "rules": [
+    {
+      "enabled": true,
+      "name": "sample-archive-rule",
+      "type": "Lifecycle",
+      "definition": {
+        "actions": {
+          "baseBlob": {
+            "tierToArchive": {
+              "daysAfterLastAccessTimeGreaterThan": 90
+            }
+          }
+        },
+        "filters": {
+          "blobTypes": [
+            "blockBlob"
+          ]
+        }
+      }
+    }
+  ]
+}
+```
+
 ## See also
 
 - [Hot, Cool, and Archive access tiers for blob data](access-tiers-overview.md)

articles/storage/blobs/archive-rehydrate-handle-event.md

@@ -7,7 +7,7 @@ author: tamram
 
 ms.service: storage
 ms.topic: how-to
-ms.date: 10/25/2021
+ms.date: 02/28/2022
 ms.author: tamram
 ms.reviewer: fryu
 ms.subservice: blobs
@@ -26,7 +26,7 @@ For more information about rehydrating blobs from the Archive tier, see [Overvie
 
 ## Prerequisites
 
-This article shows you how to use [Visual Studio 2019](https://visualstudio.microsoft.com/vs/) to develop an Azure Function with .NET. You can install Visual Studio Community for free. Make sure that you [configure Visual Studio for Azure Development with .NET](/dotnet/azure/configure-visual-studio).
+This article shows you how to use [Visual Studio 2019](https://visualstudio.microsoft.com/vs/) or later to develop an Azure Function with .NET. You can install Visual Studio Community for free. Make sure that you [configure Visual Studio for Azure Development with .NET](/dotnet/azure/configure-visual-studio).
 
 To debug the Azure Function locally, you will need to use a tool that can send an HTTP request, such as Postman.
 

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

@@ -5,7 +5,7 @@ services: storage
 author: tamram
 
 ms.author: tamram
-ms.date: 10/25/2021
+ms.date: 03/01/2022
 ms.service: storage
 ms.subservice: blobs
 ms.topic: conceptual
@@ -18,13 +18,11 @@ While a blob is in the Archive access tier, it's considered to be offline and ca
 
 - [Copy an archived blob to an online tier](#copy-an-archived-blob-to-an-online-tier): You can rehydrate an archived blob 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.
 
-- [Change a blob's access tier to an online tier](#change-a-blobs-access-tier-to-an-online-tier): You can rehydrate an archived blob to the Hot or Cool tier by changing its tier using the [Set Blob Tier](/rest/api/storageservices/set-blob-tier) operation.
+- [Change an archived blob's access tier to an online tier](#change-a-blobs-access-tier-to-an-online-tier): You can rehydrate an archived blob to the Hot or Cool tier by changing its tier using the [Set Blob Tier](/rest/api/storageservices/set-blob-tier) operation.
 
-Rehydrating a blob from the Archive tier can take several hours to complete. Microsoft recommends rehydrating larger blobs for optimal performance. Rehydrating several small blobs concurrently may require additional time. A maximum of 10 GiB per storage account may be rehydrated per hour.
+Rehydrating a blob from the Archive tier can take several hours to complete. Microsoft recommends archiving larger blobs for optimal performance when rehydrating. Rehydrating a large number of small blobs may require additional time due to the processing overhead on each blob. A maximum of 10 GiB per storage account may be rehydrated per hour with priority retrieval.
 
-You can configure [Azure Event Grid](../../event-grid/overview.md) to raise an event when you rehydrate a blob from the Archive tier to an online tier and to send the event to an event handler. For more information, see [Handle an event on blob rehydration](#handle-an-event-on-blob-rehydration).
-
-For more information about access tiers in Azure Storage, see [Hot, Cool, and Archive access tiers for blob data](access-tiers-overview.md).
+To learn how rehydrate an archived blob to an online tier, see [Rehydrate an archived blob to an online tier](archive-rehydrate-to-online-tier.md).
 
 ## Rehydration priority
 
@@ -92,7 +90,7 @@ During the blob rehydration operation, you can call the [Get Blob Properties](/r
 
 ## Handle an event on blob rehydration
 
-Rehydration of an archived blob may take up to 15 hours, and repeatedly polling **Get Blob Properties** to determine whether rehydration is complete is inefficient. Using [Azure Event Grid](../../event-grid/overview.md) to capture the event that fires when rehydration is complete offers better performance and cost optimization.
+Rehydration of an archived blob may take up to 15 hours, and repeatedly polling **Get Blob Properties** to determine whether rehydration is complete is inefficient. Microsoft recommends that you use [Azure Event Grid](../../event-grid/overview.md) to capture the event that fires when rehydration is complete for better performance and cost optimization.
 
 Azure Event Grid raises one of the following two events on blob rehydration, depending on which operation was used to rehydrate the blob:
 
@@ -115,7 +113,8 @@ For more information about pricing for block blobs and data rehydration, see [Az
 
 ## See also
 
-- [Hot, Cool, and Archive access tiers for blob data](access-tiers-overview.md).
+- [Hot, Cool, and Archive access tiers for blob data](access-tiers-overview.md)
+- [Archive a blob](archive-blob.md)
 - [Rehydrate an archived blob to an online tier](archive-rehydrate-to-online-tier.md)
 - [Run an Azure Function in response to a blob rehydration event](archive-rehydrate-handle-event.md)
 - [Reacting to Blob storage events](storage-blob-event-overview.md)

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

@@ -7,7 +7,7 @@ author: tamram
 
 ms.service: storage
 ms.topic: how-to
-ms.date: 11/01/2021
+ms.date: 03/01/2022
 ms.author: tamram
 ms.reviewer: fryu
 ms.custom: devx-track-azurepowershell

articles/storage/blobs/media/archive-blob/lifecycle-policy-base-blobs-tab-portal.png

@@ -7,7 +7,7 @@ author: tamram
 
 ms.service: storage
 ms.topic: conceptual
-ms.date: 12/30/2021
+ms.date: 03/01/2022
 ms.author: tamram
 ms.subservice: common
 ---
@@ -130,7 +130,7 @@ Storage accounts containing archived blobs support account failover. After failo
 
 ### Storage resource provider
 
-Microsoft provides two REST APIs for working with Azure Storage resources. These APIs form the basis of all actions you can perform against Azure Storage. The Azure Storage REST API enables you to work with data in your storage account, including blob, queue, file, and table data. The Azure Storage resource provider REST API enables you to work with the storage account and related resources. Management operations pertain to operations that will try and talk to the Azure Storage Resource Provider.
+Microsoft provides two REST APIs for working with Azure Storage resources. These APIs form the basis of all actions you can perform against Azure Storage. The Azure Storage REST API enables you to work with data in your storage account, including blob, queue, file, and table data. The Azure Storage resource provider REST API enables you to manage the storage account and related resources.
 
 After a failover is complete, clients can again read and write Azure Storage data in the new primary region. However, the Azure Storage resource provider does not fail over, so resource management operations must still take place in the primary region. If the primary region is unavailable, you will not be able to perform management operations on the storage account.