add CLI example

Author: tamram

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

@@ -54,7 +54,7 @@ Microsoft recommends performing a copy operation in most scenarios where you nee
 - 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 is 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 is 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 is not 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 does not affect the source blob in the Archive tier.
+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 is not 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 does not affect the source blob in the Archive tier.
 
 To learn how to rehydrate a blob by copying it to an online tier, see [Rehydrate a blob with a copy operation](archive-rehydrate-to-online-tier.md#rehydrate-a-blob-with-a-copy-operation).
 

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

@@ -99,7 +99,7 @@ N/A
 
 #### [PowerShell](#tab/azure-powershell)
 
-To copy an archived blob to a blob in an online tier in a different storage account with PowerShell, make sure you have installed the [Az.Storage](https://www.powershellgallery.com/packages/Az.Storage/) module, version 4.4.0 or higher. Next, call the [Start-AzStorageBlobCopy](/powershell/module/az.storage/start-azstorageblobcopy) command and specify the target tier and the rehydration priority. You must specify a shared access signature (SAS) with read permissions for the archived source blob.
+To copy an archived blob to a blob in an online tier in a different storage account with PowerShell, make sure you have installed the [Az.Storage](https://www.powershellgallery.com/packages/Az.Storage/) module, version 4.4.0 or higher. Next, call the [Start-AzStorageBlobCopy](/powershell/module/az.storage/start-azstorageblobcopy) command and specify the target online tier and the rehydration priority. You must specify a shared access signature (SAS) with read permissions for the archived source blob.
 
 The following example shows how to copy an archived blob to the Hot tier in a different storage account. Remember to replace placeholders in angle brackets with your own values:
 
@@ -126,7 +126,7 @@ $srcCtx = (Get-AzStorageAccount `
 $srcBlobUri = New-AzStorageBlobSASToken -Container $srcContainer `
     -Blob $srcBlob `
     -Permission rwd `
-    -ExpiryTime (Get-Date).AddDays(7) `
+    -ExpiryTime (Get-Date).AddDays(1) `
     -FullUri `
     -Context $srcCtx
 
@@ -141,7 +141,36 @@ Start-AzStorageBlobCopy -AbsoluteUri $srcBlobUri `
 
 #### [Azure CLI](#tab/azure-cli)
 
-TBD
+To copy an archived blob to a blob in an online tier in a different storage account with the Azure CLI, make sure you have installed version 2.35.0 or higher. Next, call the [az storage blob copy start](/cli/azure/storage/blob/copy#az-storage-blob-copy-start) command and specify the target online tier and the rehydration priority. You must specify a shared access signature (SAS) with read permissions for the archived source blob.
+
+The following example shows how to copy an archived blob to the Hot tier in a different storage account. Remember to replace placeholders in angle brackets with your own values:
+
+```azurecli
+# Specify the expiry interval
+end=`date -u -d "1 day" '+%Y-%m-%dT%H:%MZ'`
+
+# Get a SAS for the source blob
+srcBlobUri=$(az storage blob generate-sas \
+            --account-name <source-account> \ 
+            --container <source-container> \
+            --name <archived-source-blob> \
+            --permissions rwd \
+            --expiry $end \
+            --https-only \
+            --full-uri \
+            --as-user \
+            --auth-mode login | tr -d '"')
+
+# Copy to the destination blob in the Hot tier
+az storage blob copy start \
+    --source-uri $srcBlobUri \
+    --account-name <dest-account> \
+    --destination-container <dest-container> \
+    --destination-blob <dest-blob> \
+    --tier Hot \
+    --rehydrate-priority Standard \
+    --auth-mode login
+```
 
 ---