rename and redirect

Author: tamram

.openpublishing.redirection.json

@@ -28043,6 +28043,16 @@
       "redirect_url": "/azure/storage/blobs/concurrency-manage",
       "redirect_document_id": true
     },
+    {
+      "source_path_from_root": "/articles/storage/blobs/manage-access-tier.md",
+      "redirect_url": "/azure/storage/blobs/access-tiers-online-manage",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/storage/common/manage-account-default-access-tier.md",
+      "redirect_url": "/azure/storage/blobs/access-tiers-online-manage",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/storage/blobs/data-lake-storage-quickstart-create-databricks-account.md",
       "redirect_url": "/azure/storage/blobs/data-lake-storage-use-databricks-spark",

articles/storage/blobs/manage-access-tier.md renamed to articles/storage/blobs/access-tiers-online-manage.md

@@ -21,7 +21,53 @@ Each blob has a default access tier, either hot, cool, or archive. A blob takes
 
 ## Set the default access tier for a storage account
 
-TBD
+The default access tier setting for a general-purpose v2 storage account determines in which online tier a new blob is created by default. You can set the default access tier for a general-purpose v2 storage account at the time that you create the account or by updating an existing account's configuration.
+
+When you change the default access tier setting for an existing general-purpose v2 storage account, the change applies to all blobs in the account for which an access tier has not been explicitly set. Changing the default access tier may have a billing impact. For details, see [Default account access tier setting](access-tiers-overview.md#default-account-access-tier-setting).
+
+#### [Portal](#tab/portal)
+
+To set the default access tier for a storage account at create time in the Azure portal, follow these steps:
+
+1. Navigate to the **Storage accounts** page, and select the **Create** button.
+1. Fill out the **Basics** tab.
+1. On the **Advanced** tab, under **Blob storage**, set the **Access tier** to either *Hot* or *Cool*. The default setting is *Hot*.
+1. Select **Review + Create** to validate your settings and create your storage account.
+
+    :::image type="content" source="media/access-tiers-online-manage/set-default-access-tier-create-portal.png" alt-text="Screenshot showing how to set the default access tier when creating a storage account.":::
+
+To update the default access tier for an existing storage account in the Azure portal, follow these steps:
+
+1. Navigate to the storage account in the Azure portal.
+1. Under **Settings**, select **Configuration**.
+1. Locate the **Blob access tier (default)** setting, and select either *Hot* or *Cool*. The default setting is *Hot*, if you have not previously set this property.
+1. Save your changes.
+
+#### [PowerShell](#tab/azure-powershell)
+
+To change the default access tier setting for a storage account with PowerShell, call the [Set-AzStorageAccount](/powershell/module/az.storage/set-azstorageaccount) command, specifying the new default access tier.
+
+```azurepowershell
+$rgName = <resource-group>
+$accountName = <storage-account>
+
+# Change the storage account tier to Cool
+Set-AzStorageAccount -ResourceGroupName $rgName -Name $accountName -AccessTier Cool
+```
+
+#### [Azure CLI](#tab/azure-cli)
+
+To change the default access tier setting for a storage account with PowerShell, call the [Set-AzStorageAccount](/powershell/module/az.storage/set-azstorageaccount) command, specifying the new default access tier.
+
+```azurecli
+# Change the storage account tier to Cool
+az storage account update \
+    --resource-group <resource-group> \
+    --name <storage-account> \
+    --access-tier Cool
+```
+
+---
 
 ## Set a blob's tier on upload
 
@@ -46,9 +92,9 @@ To upload a blob or set of blobs to a specific tier from the Azure portal, follo
 1. Expand the **Advanced** section, and set the **Access tier** to *Hot* or *Cool*.
 1. Select the **Upload** button.
 
-    :::image type="content" source="media/manage-access-tier/upload-blob-to-online-tier-portal.png" alt-text="Screenshot showing how to upload blobs to an online tier in the Azure portal":::
+    :::image type="content" source="media/access-tiers-online-manage/upload-blob-to-online-tier-portal.png" alt-text="Screenshot showing how to upload blobs to an online tier in the Azure portal.":::
 
-### [PowerShell](#tab/powershell)
+### [PowerShell](#tab/azure-powershell)
 
 To upload a blob or set of blobs to a specific tier with PowerShell, call the [Set-AzStorageBlobContent](/powershell/module/az.storage/set-azstorageblobcontent) command, as shown in the following example. Remember to replace the placeholder values in brackets with your own values:
 
@@ -117,7 +163,7 @@ A blob that doesn't have an explicitly assigned tier infers its tier from the de
 
 If a blob's access tier is inferred from the default account access tier setting, then the Azure portal displays the access tier as **Hot (inferred)** or **Cool (inferred)**.
 
-:::image type="content" source="media/manage-access-tier/default-access-tier-portal.png" alt-text="Screenshot showing blobs with the default access tier in the Azure portal":::
+:::image type="content" source="media/access-tiers-online-manage/default-access-tier-portal.png" alt-text="Screenshot showing blobs with the default access tier in the Azure portal.":::
 
 #### [PowerShell](#tab/azure-powershell)
 
@@ -159,11 +205,16 @@ az storage blob show \
 
 ## Move a blob to a different online tier
 
-TBD
+You can change the tier of an existing blob in one of two ways:
+
+- By calling the [Set Blob Tier](/rest/api/storageservices/set-blob-tier) operation, either directly or via a [lifecycle management](#blob-lifecycle-management) policy, to change the blob's tier.
+- By calling the [Copy Blob](/rest/api/storageservices/copy-blob) operation to copy a blob from one tier to another. In this case, the source blob remains in the original tier, and a new blob is created in the target tier.
+
+For more information about each of these options, see [Setting or changing a blob's tier](access-tiers-overview.md#setting-or-changing-a-blobs-tier).
 
 ### Change a blob's tier
 
-TBD
+When you change a blob's tier, you move that blob and all of its data to the target tier. Calling [Set Blob Tier](/rest/api/storageservices/set-blob-tier) is typically the best option when you are changing a blob's tier from a hotter tier to a cooler one.
 
 # [Portal](#tab/portal)
 
@@ -181,7 +232,19 @@ TBD
 
 ### Copy a blob to a different online tier
 
-TBD???
+Calling [Copy Blob](/rest/api/storageservices/copy-blob) is recommended for most scenarios where you are moving a blob from Cool to Hot, or rehydrating a blob from the Archive tier. Use PowerShell, Azure CLI, or one of the Azure Storage client libraries to copy a blob to a different tier.
+
+# [Portal](#tab/portal)
+
+N/A
+
+#### [PowerShell](#tab/azure-powershell)
+
+TBD
+
+#### [Azure CLI](#tab/azure-cli)
+
+TBD
 
 ## Next steps
 

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

@@ -80,7 +80,7 @@ The default access tier for a new general-purpose v2 storage account is set to t
 
 A blob that doesn't have an explicitly assigned tier infers its tier from the default account access tier setting. If a blob's access tier is inferred from the default account access tier setting, then the Azure portal displays the access tier as **Hot (inferred)** or **Cool (inferred)**.
 
-Changing the default account access tier setting applies to all blobs in the account for which an access tier has not been explicitly set. If you toggle the default account access tier setting from hot to cool in a general-purpose v2 account, then you are charged for write operations (per 10,000) for all blobs for which the access tier is inferred. You are charged for both read operations (per 10,000) and data retrieval (per GB) if you toggle from cool to hot in a general-purpose v2 account.
+Changing the default access tier setting for a storage account applies to all blobs in the account for which an access tier has not been explicitly set. If you toggle the default access tier setting from hot to cool in a general-purpose v2 account, then you are charged for write operations (per 10,000) for all blobs for which the access tier is inferred. You are charged for both read operations (per 10,000) and data retrieval (per GB) if you toggle from cool to hot in a general-purpose v2 account.
 
 When you create a legacy Blob Storage account, you must specify the default access tier setting as hot or cool at create time. There's no charge for changing the default account access tier setting from hot to cool in a legacy Blob Storage account. You are charged for both read operations (per 10,000) and data retrieval (per GB) if you toggle from cool to hot in a Blob Storage account. Microsoft recommends using general-purpose v2 storage accounts rather than Blob Storage accounts when possible.
 
@@ -93,7 +93,7 @@ To explicitly set a blob's tier when you create it, specify the tier when you up
 
 After a blob is created, you can change its tier in either of the following ways:
 
-- By calling the [Set Blob Tier](/rest/api/storageservices/set-blob-tier) operation, either directly or via a [lifecycle management](#blob-lifecycle-management) policy. Calling [Set Blob Tier](/rest/api/storageservices/set-blob-tier) is typically the best option when changing a blob's tier from a hotter tier to a cooler one.
+- By calling the [Set Blob Tier](/rest/api/storageservices/set-blob-tier) operation, either directly or via a [lifecycle management](#blob-lifecycle-management) policy. Calling [Set Blob Tier](/rest/api/storageservices/set-blob-tier) is typically the best option when you are changing a blob's tier from a hotter tier to a cooler one.
 - By calling the [Copy Blob](/rest/api/storageservices/copy-blob) operation to copy a blob from one tier to another. Calling [Copy Blob](/rest/api/storageservices/copy-blob) is recommended for most scenarios where you are rehydrating a blob from the archive tier to an online tier, or moving a blob from cool to hot. By copying a blob, you can avoid the early deletion penalty, if the required storage interval for the source blob has not yet elapsed. However, copying a blob results in capacity charges for two blobs, the source blob and the destination blob.
 
 Changing a blob's tier from hot to cool or archive is instantaneous, as is changing from cool to hot. Rehydrating a blob from the archive tier to either the hot or cool tier can take up to 15 hours.
@@ -105,7 +105,7 @@ Keep in mind the following points when moving a blob between the cool and archiv
 
 The following table summarizes the approaches you can take to move blobs between various tiers.
 
-| Origin tier/Destination tier | Hot tier | Cool tier | Archive tier |
+| Origin/Destination | Hot tier | Cool tier | Archive tier |
 |--|--|--|--|
 | **Hot tier** | N/A | Change a blob's tier from Hot to Cool with **Set Blob Tier** or **Copy Blob**. [Learn more...](manage-access-tier.md)<br /><br />Move blobs to the Cool tier with a lifecycle management policy. [Learn more...](lifecycle-management-overview.md) | Change a blob's tier from Hot to Archive with **Set Blob Tier** or **Copy Blob**. [Learn more...](archive-blob.md) <br /><br />Archive blobs with a lifecycle management policy. [Learn more...](lifecycle-management-overview.md) |
 | **Cool tier** | Change a blob's tier from Cool to Hot with **Set Blob Tier** or **Copy Blob**. [Learn more...](manage-access-tier.md) <br /><br />Move blobs to the Hot tier with a lifecycle management policy. [Learn more...](lifecycle-management-overview.md) | N/A | Change a blob's tier from Cool to Archive with **Set Blob Tier** or **Copy Blob**. [Learn more...](archive-blob.md) <br /><br />Archive blobs with a lifecycle management policy. [Learn more...](lifecycle-management-overview.md) |