Merge pull request #110580 from xyh1/patch-110

Updates for GA

Author: v-shils

articles/storage/blobs/media/storage-tiers/rehydrate-status.png

@@ -5,7 +5,7 @@ services: storage
 author: mhopkins-msft
 
 ms.author: mhopkins
-ms.date: 11/14/2019
+ms.date: 04/08/2020
 ms.service: storage
 ms.subservice: blobs
 ms.topic: conceptual
@@ -27,15 +27,21 @@ While a blob is in the archive access tier, it's considered offline and can't be
 
 ## Copy an archived blob to an online tier
 
-If you don't want to rehydrate your archive blob, you can choose to do a [Copy Blob](https://docs.microsoft.com/rest/api/storageservices/copy-blob) operation. Your original blob will remain unmodified in archive while a new blob is created in the online hot or cool tier for you to work on. In the Copy Blob operation, you may also set the optional *x-ms-rehydrate-priority* property to Standard or High (preview) to specify the priority at which you want your blob copy created.
-
-Archive blobs can only be copied to online destination tiers within the same storage account. Copying an archive blob to another archive blob is not supported.
+If you don't want to rehydrate your archive blob, you can choose to do a [Copy Blob](https://docs.microsoft.com/rest/api/storageservices/copy-blob) operation. Your original blob will remain unmodified in archive while a new blob is created in the online hot or cool tier for you to work on. In the Copy Blob operation, you may also set the optional *x-ms-rehydrate-priority* property to Standard or High to specify the priority at which you want your blob copy created.
 
 Copying a blob from archive can take hours to complete depending on the rehydrate priority selected. Behind the scenes, the **Copy Blob** operation reads your archive source blob to create a new online blob in the selected destination tier. The new blob may be visible when you list blobs but the data is not available until the read from the source archive blob is complete and data is written to the new online destination blob. The new blob is as an independent copy and any modification or deletion to it does not affect the source archive blob.
 
+Archive blobs can only be copied to online destination tiers within the same storage account. Copying an archive blob to another archive blob is not supported. The following table indicates CopyBlob's capabilities.
+
+|                                           | **Hot tier source**   | **Cool tier source** | **Archive tier source**    |
+| ----------------------------------------- | --------------------- | -------------------- | ------------------- |
+| **Hot tier destination**                  | Supported             | Supported            | Supported within the same account; pending rehydrate               |
+| **Cool tier destination**                 | Supported             | Supported            | Supported within the same account; pending rehydrate               |
+| **Archive tier destination**              | Supported             | Supported            | Unsupported         |
+
 ## Pricing and billing
 
-Rehydrating blobs out of archive into hot or cool tiers are charged as read operations and data retrieval. Using High priority (preview) has higher operation and data retrieval costs compared to standard priority. High priority rehydration shows up as a separate line item on your bill. If a high priority request to return an archive blob of a few gigabytes takes over 5 hours, you won't be charged the high priority retrieval rate. However, standard retrieval rates still apply as the rehydration was prioritized over other requests.
+Rehydrating blobs out of archive into hot or cool tiers are charged as read operations and data retrieval. Using High priority has higher operation and data retrieval costs compared to standard priority. High priority rehydration shows up as a separate line item on your bill. If a high priority request to return an archive blob of a few gigabytes takes over 5 hours, you won't be charged the high priority retrieval rate. However, standard retrieval rates still apply as the rehydration was prioritized over other requests.
 
 Copying blobs from archive into hot or cool tiers are charged as read operations and data retrieval. A write operation is charged for the creation of the new blob copy. Early deletion fees don't apply when you copy to an online blob because the source blob remains unmodified in the archive tier. High priority retrieval charges do apply if selected.
 
@@ -65,8 +71,9 @@ Blobs in the archive tier should be stored for a minimum of 180 days. Deleting o
 1. Select **Save** at the bottom.
 
 ![Change storage account tier](media/storage-tiers/blob-access-tier.png)
+![Check rehydrate status](media/storage-tiers/rehydrate-status.png)
 
-# [Powershell](#tab/azure-powershell)
+# [PowerShell](#tab/azure-powershell)
 The following PowerShell script can be used to change the blob tier of an archive blob. The `$rgName` variable must be initialized with your resource group name. The `$accountName` variable must be initialized with your storage account name. The `$containerName` variable must be initialized with your container name. The `$blobName` variable must be initialized with your blob name. 
 ```powershell
 #Initialize the following with your resource group, storage account, container, and blob names

articles/storage/blobs/storage-blob-rehydration.md

@@ -5,20 +5,20 @@ services: storage
 author: mhopkins-msft
 
 ms.author: mhopkins
-ms.date: 08/09/2019
+ms.date: 04/08/2020
 ms.service: storage
 ms.subservice: blobs
 ms.topic: include
 ms.reviewer: hux
 ms.custom: include file
 ---
 
-To read data in archive storage, you must first change the tier of the blob to hot or cool. This process is known as rehydration and can take hours to complete. We recommend large blob sizes for optimal rehydration performance. Rehydrating several small blobs concurrently may add additional time. There are currently two rehydrate priorities, High (preview) and Standard, which can be set via the optional *x-ms-rehydrate-priority* property on a [Set Blob Tier](https://docs.microsoft.com/rest/api/storageservices/set-blob-tier) or [Copy Blob](https://docs.microsoft.com/rest/api/storageservices/copy-blob) operation.
+To read data in archive storage, you must first change the tier of the blob to hot or cool. This process is known as rehydration and can take hours to complete. We recommend large blob sizes for optimal rehydration performance. Rehydrating several small blobs concurrently may add additional time. There are currently two rehydrate priorities, High and Standard, which can be set via the optional *x-ms-rehydrate-priority* property on a [Set Blob Tier](https://docs.microsoft.com/rest/api/storageservices/set-blob-tier) or [Copy Blob](https://docs.microsoft.com/rest/api/storageservices/copy-blob) operation.
 
 * **Standard priority**: The rehydration request will be processed in the order it was received and may take up to 15 hours.
-* **High priority (preview)**: The rehydration request will be prioritized over Standard requests and may finish in under 1 hour. High priority may take longer than 1 hour, depending on blob size and current demand. High priority requests are guaranteed to be prioritized over Standard priority requests.
+* **High priority**: The rehydration request will be prioritized over Standard requests and may finish in under 1 hour. High priority may take longer than 1 hour, depending on blob size and current demand. High priority requests are guaranteed to be prioritized over Standard priority requests.
 
 > [!NOTE]
 > Standard priority is the default rehydration option for archive. High priority is a faster option that will cost more than Standard priority rehydration and is usually reserved for use in emergency data restoration situations.
 
-Once a rehydration request is initiated, it cannot be canceled. During rehydration, you may check the *Archive Status* blob property to confirm if the tier has changed. The status reads "rehydrate-pending-to-hot" or "rehydrate-pending-to-cool" depending on the destination tier. Upon completion, the archive status property is removed, and the *Access Tier* blob property reflects the new hot or cool tier.
+Once a rehydration request is initiated, it cannot be canceled. During the rehydration process, the *x-ms-access-tier* blob property will continue to show as archive until rehydration is completed to an online tier. To confirm rehydration status and progress, you may call [Get Blob Properties](https://docs.microsoft.com/rest/api/storageservices/get-blob-properties) to check the *x-ms-archive-status* and the *x-ms-rehydrate-priority* blob properties. The archive status can read "rehydrate-pending-to-hot" or "rehydrate-pending-to-cool" depending on the rehydrate destination tier. The rehydrate priority will indicate the speed of "High" or "Standard". Upon completion, the archive status and rehydrate priority properties are removed, and the access tier blob property will update to reflect the selected hot or cool tier.