Merge pull request #247271 from pauljewellmsft/pauljewell-devguide-cleanup

v-regandowner · web-flow · commit 9f1718bc5b23 · 2023-08-03T13:55:27.000-04:00
Blob dev guide cleanup items
diff --git a/articles/storage/blobs/storage-blob-container-create-java.md b/articles/storage/blobs/storage-blob-container-create-java.md
@@ -23,17 +23,7 @@ Blobs in Azure Storage are organized into containers. Before you can upload a bl
 - The [authorization mechanism](../common/authorize-data-access.md) must have permissions to create a blob container. To learn more, see the authorization guidance for the following REST API operation:
     - [Create Container](/rest/api/storageservices/create-container#authorization)
 
-## Name a container
-
-A container name must be a valid DNS name, as it forms part of the unique URI used to address the container or its blobs. Follow these rules when naming a container:
-
-- Container names can be between 3 and 63 characters long.
-- Container names must start with a letter or number, and can contain only lowercase letters, numbers, and the dash (-) character.
-- Two or more consecutive dash characters aren't permitted in container names.
-
-The URI for a container is in this format:
-
-`https://accountname.blob.core.windows.net/containername`
+[!INCLUDE [storage-dev-guide-about-container-naming](../../../includes/storage-dev-guides/storage-dev-guide-about-container-naming.md)]
 
 ## Create a container
 
diff --git a/articles/storage/blobs/storage-blob-container-create-javascript.md b/articles/storage/blobs/storage-blob-container-create-javascript.md
@@ -22,17 +22,7 @@ Blobs in Azure Storage are organized into containers. Before you can upload a bl
 - The [authorization mechanism](../common/authorize-data-access.md) must have permissions to create a blob container. To learn more, see the authorization guidance for the following REST API operation:
     - [Create Container](/rest/api/storageservices/create-container#authorization)
 
-## Name a container
-
-A container name must be a valid DNS name, as it forms part of the unique URI used to address the container or its blobs. Follow these rules when naming a container:
-
-- Container names can be between 3 and 63 characters long.
-- Container names must start with a letter or number, and can contain only lowercase letters, numbers, and the dash (-) character.
-- Two or more consecutive dash characters aren't permitted in container names.
-
-The URI for a container is in this format:
-
-`https://myaccount.blob.core.windows.net/mycontainer`
+[!INCLUDE [storage-dev-guide-about-container-naming](../../../includes/storage-dev-guides/storage-dev-guide-about-container-naming.md)]
 
 ## Create a container
 
diff --git a/articles/storage/blobs/storage-blob-container-create-python.md b/articles/storage/blobs/storage-blob-container-create-python.md
@@ -23,17 +23,7 @@ Blobs in Azure Storage are organized into containers. Before you can upload a bl
 - The [authorization mechanism](../common/authorize-data-access.md) must have permissions to create a blob container. To learn more, see the authorization guidance for the following REST API operation:
     - [Create Container](/rest/api/storageservices/create-container#authorization)
 
-## Container names
-
-A container name must be a valid DNS name, as it forms part of the unique URI used to address the container or its blobs. Follow these rules when naming a container:
-
-- Container names can be between 3 and 63 characters long.
-- Container names must start with a letter or number, and can contain only lowercase letters, numbers, and the dash (-) character.
-- Two or more consecutive dash characters aren't permitted in container names.
-
-The URI for a container is in this format:
-
-`https://accountname.blob.core.windows.net/containername`
+[!INCLUDE [storage-dev-guide-about-container-naming](../../../includes/storage-dev-guides/storage-dev-guide-about-container-naming.md)]
 
 ## Create a container
 
diff --git a/articles/storage/blobs/storage-blob-container-create-typescript.md b/articles/storage/blobs/storage-blob-container-create-typescript.md
@@ -22,17 +22,7 @@ Blobs in Azure Storage are organized into containers. Before you can upload a bl
 - The [authorization mechanism](../common/authorize-data-access.md) must have permissions to create a blob container. To learn more, see the authorization guidance for the following REST API operation:
     - [Create Container](/rest/api/storageservices/create-container#authorization)
 
-## Name a container
-
-A container name must be a valid DNS name, as it forms part of the unique URI used to address the container or its blobs. Follow these rules when naming a container:
-
-- Container names can be between 3 and 63 characters long.
-- Container names must start with a letter or number, and can contain only lowercase letters, numbers, and the dash (-) character.
-- Two or more consecutive dash characters aren't permitted in container names.
-
-The URI for a container is in this format:
-
-`https://myaccount.blob.core.windows.net/mycontainer`
+[!INCLUDE [storage-dev-guide-about-container-naming](../../../includes/storage-dev-guides/storage-dev-guide-about-container-naming.md)]
 
 ## Create a container
 
diff --git a/articles/storage/blobs/storage-blob-container-create.md b/articles/storage/blobs/storage-blob-container-create.md
@@ -23,17 +23,7 @@ Blobs in Azure Storage are organized into containers. Before you can upload a bl
 - The [authorization mechanism](../common/authorize-data-access.md) must have permissions to create a blob container. To learn more, see the authorization guidance for the following REST API operation:
     - [Create Container](/rest/api/storageservices/create-container#authorization)
 
-## Name a container
-
-A container name must be a valid DNS name, as it forms part of the unique URI used to address the container or its blobs. Follow these rules when naming a container:
-
-- Container names can be between 3 and 63 characters long.
-- Container names must start with a letter or number, and can contain only lowercase letters, numbers, and the dash (-) character.
-- Two or more consecutive dash characters aren't permitted in container names.
-
-The URI for a container is in this format:
-
-`https://myaccount.blob.core.windows.net/mycontainer`
+[!INCLUDE [storage-dev-guide-about-container-naming](../../../includes/storage-dev-guides/storage-dev-guide-about-container-naming.md)]
 
 ## Create a container
 
diff --git a/articles/storage/blobs/storage-blob-containers-list-java.md b/articles/storage/blobs/storage-blob-containers-list-java.md
@@ -23,7 +23,7 @@ When you list the containers in an Azure Storage account from your code, you can
 - The [authorization mechanism](../common/authorize-data-access.md) must have permissions to list blob containers. To learn more, see the authorization guidance for the following REST API operation:
     - [List Containers](/rest/api/storageservices/list-containers2#authorization)
 
-## Understand container listing options
+## About container listing options
 
 To list containers in your storage account, call the following method:
 
diff --git a/articles/storage/blobs/storage-blob-containers-list-javascript.md b/articles/storage/blobs/storage-blob-containers-list-javascript.md
@@ -24,7 +24,7 @@ When you list the containers in an Azure Storage account from your code, you can
 - The [authorization mechanism](../common/authorize-data-access.md) must have permissions to list blob containers. To learn more, see the authorization guidance for the following REST API operation:
     - [List Containers](/rest/api/storageservices/list-containers2#authorization)
 
-## Understand container listing options
+## About container listing options
 
 To list containers in your storage account, create a [BlobServiceClient](storage-blob-javascript-get-started.md#create-a-blobserviceclient-object) object then call the following method:
 
diff --git a/articles/storage/blobs/storage-blob-containers-list-python.md b/articles/storage/blobs/storage-blob-containers-list-python.md
@@ -23,7 +23,7 @@ When you list the containers in an Azure Storage account from your code, you can
 - The [authorization mechanism](../common/authorize-data-access.md) must have permissions to list blob containers. To learn more, see the authorization guidance for the following REST API operation:
     - [List Containers](/rest/api/storageservices/list-containers2#authorization)
 
-## Container listing options
+## About container listing options
 
 To list containers in your storage account, call the following method:
 
diff --git a/articles/storage/blobs/storage-blob-containers-list-typescript.md b/articles/storage/blobs/storage-blob-containers-list-typescript.md
@@ -24,7 +24,7 @@ When you list the containers in an Azure Storage account from your code, you can
 - The [authorization mechanism](../common/authorize-data-access.md) must have permissions to list blob containers. To learn more, see the authorization guidance for the following REST API operation:
     - [List Containers](/rest/api/storageservices/list-containers2#authorization)
 
-## Understand container listing options
+## About container listing options
 
 To list containers in your storage account, create a [BlobServiceClient](storage-blob-typescript-get-started.md#create-a-blobserviceclient-object) object then call the following method:
 
diff --git a/articles/storage/blobs/storage-blob-containers-list.md b/articles/storage/blobs/storage-blob-containers-list.md
@@ -23,7 +23,7 @@ When you list the containers in an Azure Storage account from your code, you can
 - The [authorization mechanism](../common/authorize-data-access.md) must have permissions to list blob containers. To learn more, see the authorization guidance for the following REST API operation:
     - [List Containers](/rest/api/storageservices/list-containers2#authorization)
 
-## Understand container listing options
+## About container listing options
 
 To list containers in your storage account, call one of the following methods:
 
diff --git a/articles/storage/blobs/storage-blob-use-access-tier-javascript.md b/articles/storage/blobs/storage-blob-use-access-tier-javascript.md
@@ -23,21 +23,10 @@ This article shows how to set or change a blob's [access tier](access-tiers-over
 - The [authorization mechanism](../common/authorize-data-access.md) must have permissions to set the blob's access tier. To learn more, see the authorization guidance for the following REST API operation:
     - [Set Blob Tier](/rest/api/storageservices/set-blob-tier#authorization)
 
-## About block blob access tiers
+[!INCLUDE [storage-dev-guide-about-access-tiers](../../../includes/storage-dev-guides/storage-dev-guide-about-access-tiers.md)]
 
-Data stored in the cloud grows at an exponential pace. To manage costs for your expanding storage needs, it can be helpful to organize your data based on how frequently it will be accessed and how long it will be retained. Azure storage offers different access tiers so that you can store your blob data in the most cost-effective manner based on how it's being used. Azure Storage access tiers include:
-
-- [**Online tiers**](access-tiers-overview.md#online-access-tiers)
-    - **Hot tier** - An online tier optimized for storing data that is accessed or modified frequently. The hot tier has the highest storage costs, but the lowest access costs.
-    - **Cool tier** - An online tier optimized for storing data that is infrequently accessed or modified. Data in the cool tier should be stored for a minimum of 30 days. The cool tier has lower storage costs and higher access costs compared to the hot tier.
-    - **Cold tier** - An online tier optimized for storing data that is infrequently accessed or modified. Data in the cold tier should be stored for a minimum of 90 days. The cold tier has lower storage costs and higher access costs compared to the cool tier.
-- [**Archive tier**](access-tiers-overview.md#archive-access-tier) - An offline tier optimized for storing data that is rarely accessed, and that has flexible latency requirements, on the order of hours. Data in the archive tier should be stored for a minimum of 180 days.
-
-## Restrictions
-
-Setting the access tier is only allowed on block blobs. To learn more about restrictions on setting a block blob's access tier, see [Set Blob Tier (REST API)](/rest/api/storageservices/set-blob-tier#remarks).
-
-To set the access tier to `Cold`, you must use a minimum [client library](/javascript/api/preview-docs/@azure/storage-blob/) version of 12.13.0.
+> [!NOTE]
+> To set the access tier to `Cold` using JavaScript, you must use a minimum [client library](/javascript/api/preview-docs/@azure/storage-blob/) version of 12.13.0.
 
 ## Set a blob's access tier during upload
 
diff --git a/articles/storage/blobs/storage-blob-use-access-tier-typescript.md b/articles/storage/blobs/storage-blob-use-access-tier-typescript.md
@@ -23,21 +23,10 @@ This article shows how to set or change a blob's [access tier](access-tiers-over
 - The [authorization mechanism](../common/authorize-data-access.md) must have permissions to set the blob's access tier. To learn more, see the authorization guidance for the following REST API operation:
     - [Set Blob Tier](/rest/api/storageservices/set-blob-tier#authorization)
 
-## About block blob access tiers
+[!INCLUDE [storage-dev-guide-about-access-tiers](../../../includes/storage-dev-guides/storage-dev-guide-about-access-tiers.md)]
 
-Data stored in the cloud grows at an exponential pace. To manage costs for your expanding storage needs, it can be helpful to organize your data based on how frequently it will be accessed and how long it will be retained. Azure storage offers different access tiers so that you can store your blob data in the most cost-effective manner based on how it's being used. Azure Storage access tiers include:
-
-- [**Online tiers**](access-tiers-overview.md#online-access-tiers)
-    - **Hot tier** - An online tier optimized for storing data that is accessed or modified frequently. The hot tier has the highest storage costs, but the lowest access costs.
-    - **Cool tier** - An online tier optimized for storing data that is infrequently accessed or modified. Data in the cool tier should be stored for a minimum of 30 days. The cool tier has lower storage costs and higher access costs compared to the hot tier.
-    - **Cold tier** - An online tier optimized for storing data that is infrequently accessed or modified. Data in the cold tier should be stored for a minimum of 90 days. The cold tier has lower storage costs and higher access costs compared to the cool tier.
-- [**Archive tier**](access-tiers-overview.md#archive-access-tier) - An offline tier optimized for storing data that is rarely accessed, and that has flexible latency requirements, on the order of hours. Data in the archive tier should be stored for a minimum of 180 days.
-
-## Restrictions
-
-Setting the access tier is only allowed on block blobs. To learn more about restrictions on setting a block blob's access tier, see [Set Blob Tier (REST API)](/rest/api/storageservices/set-blob-tier#remarks).
-
-To set the access tier to `Cold`, you must use a minimum [client library](/javascript/api/preview-docs/@azure/storage-blob/) version of 12.13.0.
+> [!NOTE]
+> To set the access tier to `Cold` using TypeScript, you must use a minimum [client library](/javascript/api/preview-docs/@azure/storage-blob/) version of 12.13.0.
 
 ## Set a blob's access tier during upload
 
diff --git a/includes/storage-dev-guides/storage-dev-guide-about-container-naming.md b/includes/storage-dev-guides/storage-dev-guide-about-container-naming.md
@@ -0,0 +1,23 @@
+---
+title: "include file"
+description: "include file"
+services: storage
+author: pauljewellmsft
+ms.service: azure-storage
+ms.topic: include
+ms.date: 08/03/2023
+ms.author: pauljewell
+ms.custom: include file
+---
+
+## About container naming
+
+A container name must be a valid DNS name, as it forms part of the unique URI used to address the container or its blobs. Follow these rules when naming a container:
+
+- Container names can be between 3 and 63 characters long.
+- Container names must start with a letter or number, and can contain only lowercase letters, numbers, and the dash (-) character.
+- Consecutive dash characters aren't permitted in container names.
+
+The URI for a container resource is formatted as follows:
+
+`https://my-account-name.blob.core.windows.net/my-container-name`
