Merge pull request #174978 from tamram/tamram21-1007

clarify default access tier setting & fix redirect

Author: PMEds28

.openpublishing.redirection.json

@@ -28129,7 +28129,7 @@
       "redirect_document_id": false
     },
     {
-      "source_path_from_root": "/articles/blobs/storage-blob-storage-tiers.md",
+      "source_path_from_root": "/articles/storage/blobs/storage-blob-storage-tiers.md",
       "redirect_url": "/azure/storage/blobs/access-tiers-overview",
       "redirect_document_id": true
     },

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

@@ -5,7 +5,7 @@ description: Azure storage offers different access tiers so that you can store y
 author: tamram
 
 ms.author: tamram
-ms.date: 09/29/2021
+ms.date: 10/07/2021
 ms.service: storage
 ms.subservice: blobs
 ms.topic: conceptual
@@ -77,11 +77,13 @@ The following operations are supported for blobs in the archive tier:
 
 Storage accounts have a default access tier setting that indicates the online tier in which a new blob is created. The default access tier setting can be set to either hot or cool. Users can override the default setting for an individual blob when uploading the blob or changing its tier.
 
-By default, the default access tier for a new storage account is set to the hot tier. You can change the default access tier setting when you create a storage account or after it is created. If you do not change this setting, then blobs are uploaded to the hot tier by default.
+The default access tier for a new general-purpose v2 storage account is set to the hot tier by default. You can change the default access tier setting when you create a storage account or after it is created. If you do not change this setting on the storage account or explicitly set the tier when uploading a blob, then a new blob is uploaded to the hot tier by default.
 
 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. There's no charge for this change in Blob Storage accounts. You are charged for both read operations (per 10,000) and data retrieval (per GB) if you toggle from cool to hot in either general-purpose v2 or Blob Storage accounts.
+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.
+
+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.
 
 > [!NOTE]
 > The archive tier is not supported as the default access tier for a storage account.