edits

Author: pauljewellmsft

articles/storage/blobs/storage-blob-container-create-go.md

@@ -17,17 +17,17 @@ ms.custom: devx-track-go, devguide-go
 
 [!INCLUDE [storage-dev-guide-selector-create-container](../../../includes/storage-dev-guides/storage-dev-guide-selector-create-container.md)]
 
-Blobs in Azure Storage are organized into containers. Before you can upload a blob, you must first create a container. This article shows how to create containers with the [Azure Storage client module for Go](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/storage/azblob#section-readme).
+This article shows how to create containers with the [Azure Storage client module for Go](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/storage/azblob#section-readme). Blobs in Azure Storage are organized into containers. Before you can upload a blob, you must first create a container.
 
 [!INCLUDE [storage-dev-guide-prereqs-go](../../../includes/storage-dev-guides/storage-dev-guide-prereqs-go.md)]
 
 ## Set up your environment
 
 [!INCLUDE [storage-dev-guide-project-setup-go](../../../includes/storage-dev-guides/storage-dev-guide-project-setup-go.md)]
 
-### Authorization
+#### Authorization
 
-The authorization mechanism must have the necessary permissions to create a container.For authorization with Microsoft Entra ID (recommended), you need Azure RBAC built-in role **Storage Blob Data Contributor** or higher. To learn more, see the authorization guidance for [Create Container (REST API)](/rest/api/storageservices/create-container#authorization).
+The authorization mechanism must have the necessary permissions to create a container. For authorization with Microsoft Entra ID (recommended), you need Azure RBAC built-in role **Storage Blob Data Contributor** or higher. To learn more, see the authorization guidance for [Create Container (REST API)](/rest/api/storageservices/create-container#authorization).
 
 [!INCLUDE [storage-dev-guide-about-container-naming](../../../includes/storage-dev-guides/storage-dev-guide-about-container-naming.md)]
 
@@ -55,6 +55,8 @@ The following example creates the container if it doesn't already exist in the s
 
 :::code language="go" source="~/blob-devguide-go/cmd/create-container/create_container.go" id="snippet_create_root_container":::
 
+[!INCLUDE [storage-dev-guide-code-samples-note-go](../../../includes/storage-dev-guides/storage-dev-guide-code-samples-note-go.md)]
+
 ## Resources
 
 To learn more about creating a container using the Azure Blob Storage client module for Go, see the following resources.

articles/storage/blobs/storage-blob-container-delete-go.md

@@ -25,7 +25,7 @@ This article shows how to delete containers with the [Azure Storage client modul
 
 [!INCLUDE [storage-dev-guide-project-setup-go](../../../includes/storage-dev-guides/storage-dev-guide-project-setup-go.md)]
 
-### Authorization
+#### Authorization
 
 The authorization mechanism must have the necessary permissions to delete or restore a container. For authorization with Microsoft Entra ID (recommended), you need Azure RBAC built-in role **Storage Blob Data Contributor** or higher. To learn more, see the authorization guidance for [Delete Container (REST API)](/rest/api/storageservices/delete-container#authorization) and [Restore Container (REST API)](/rest/api/storageservices/restore-container#authorization).
 
@@ -51,6 +51,8 @@ The following example lists containers, including soft-deleted containers, and i
 
 :::code language="go" source="~/blob-devguide-go/cmd/delete-container/delete_container.go" id="snippet_restore_container":::
 
+[!INCLUDE [storage-dev-guide-code-samples-note-go](../../../includes/storage-dev-guides/storage-dev-guide-code-samples-note-go.md)]
+
 ## Resources
 
 To learn more about deleting a container using the Azure Blob Storage client module for Go, see the following resources.

articles/storage/blobs/storage-blob-container-properties-metadata-go.md

@@ -25,7 +25,7 @@ Blob containers support system properties and user-defined metadata, in addition
 
 [!INCLUDE [storage-dev-guide-project-setup-go](../../../includes/storage-dev-guides/storage-dev-guide-project-setup-go.md)]
 
-### Authorization
+#### Authorization
 
 The authorization mechanism must have the necessary permissions to work with container properties or metadata. For authorization with Microsoft Entra ID (recommended), you need Azure RBAC built-in role **Storage Blob Data Reader** or higher for the *get* operations, and **Storage Blob Data Contributor** or higher for the *set* operations. To learn more, see the authorization guidance for [Get Container Properties](/rest/api/storageservices/get-container-properties#authorization), [Set Container Metadata](/rest/api/storageservices/set-container-metadata#authorization), or [Get Container Metadata](/rest/api/storageservices/get-container-metadata#authorization).
 
@@ -67,6 +67,8 @@ Metadata is included in the response from `GetProperties`. The following example
 
 :::code language="go" source="~/blob-devguide-go/cmd/container-properties-metadata/container_properties_metadata.go" id="snippet_get_container_metadata":::
 
+[!INCLUDE [storage-dev-guide-code-samples-note-go](../../../includes/storage-dev-guides/storage-dev-guide-code-samples-note-go.md)]
+
 ## Resources
 
 To learn more about setting and retrieving container properties and metadata using the Azure Blob Storage client module for Go, see the following resources.

articles/storage/blobs/storage-blob-containers-list-go.md

@@ -25,7 +25,7 @@ When you list the containers in an Azure Storage account from your code, you can
 
 [!INCLUDE [storage-dev-guide-project-setup-go](../../../includes/storage-dev-guides/storage-dev-guide-project-setup-go.md)]
 
-### Authorization
+#### Authorization
 
 The authorization mechanism must have the necessary permissions to list blob containers. For authorization with Microsoft Entra ID (recommended), you need Azure RBAC built-in role **Storage Blob Data Contributor** or higher. To learn more, see the authorization guidance for [List Containers](/rest/api/storageservices/list-containers2#authorization).
 
@@ -71,14 +71,16 @@ You can also specify a limit for the number of results per page. This example pa
 
 :::code language="go" source="~/blob-devguide-go/cmd/list-containers/list_containers.go" id="snippet_list_containers_pages":::
 
+[!INCLUDE [storage-dev-guide-code-samples-note-go](../../../includes/storage-dev-guides/storage-dev-guide-code-samples-note-go.md)]
+
 ## Resources
 
 To learn more about listing containers using the Azure Blob Storage client module for Go, see the following resources.
 
 ### Code samples
 
 - View [code samples](https://github.com/Azure-Samples/blob-storage-devguide-go/cmd/list-containers/list_containers.go) from this article (GitHub)
-- 
+
 ### REST API operations
 
 The Azure SDK for Go contains libraries that build on top of the Azure REST API, allowing you to interact with REST API operations through familiar Go paradigms. The client library methods for listing containers use the following REST API operation:

articles/storage/blobs/storage-blob-delete-go.md

@@ -25,7 +25,7 @@ This article shows how to delete blobs using the [Azure Storage client module fo
 
 [!INCLUDE [storage-dev-guide-project-setup-go](../../../includes/storage-dev-guides/storage-dev-guide-project-setup-go.md)]
 
-### Authorization
+#### Authorization
 
 The authorization mechanism must have the necessary permissions to delete a blob, or to restore a soft-deleted blob. For authorization with Microsoft Entra ID (recommended), you need Azure RBAC built-in role **Storage Blob Data Contributor** or higher. To learn more, see the authorization guidance for [Delete Blob](/rest/api/storageservices/delete-blob#authorization) and [Undelete Blob](/rest/api/storageservices/undelete-blob#authorization).
 
@@ -43,7 +43,7 @@ If the blob has any associated snapshots, you must delete all of its snapshots t
 
 :::code language="go" source="~/blob-devguide-go/cmd/delete_blob/delete_blob.go" id="snippet_delete_blob_snapshots":::
 
-To delete *only* the snapshots and not the blob itself, you can pass the parameter `delete_snapshots="only"`.
+To delete *only* the snapshots and not the blob itself, you can pass the value `DeleteSnapshotsOptionTypeOnly` to the `DeleteSnapshots` parameter.
 
 ## Restore a deleted blob
 
@@ -76,6 +76,8 @@ The following code example identifies a version of a deleted blob, and restores
 
 :::code language="go" source="~/blob-devguide-go/cmd/delete_blob/delete_blob.go" id="snippet_restore_blob_version":::
 
+[!INCLUDE [storage-dev-guide-code-samples-note-go](../../../includes/storage-dev-guides/storage-dev-guide-code-samples-note-go.md)]
+
 ## Resources
 
 To learn more about how to delete blobs and restore deleted blobs using the Azure Blob Storage client module for Go, see the following resources.

articles/storage/blobs/storage-blob-download-go.md

@@ -17,17 +17,17 @@ ms.custom: devx-track-go, devguide-go
 
 [!INCLUDE [storage-dev-guide-selector-download](../../../includes/storage-dev-guides/storage-dev-guide-selector-download.md)]
 
-This article shows how to download a blob using the [Azure Storage client module for Go](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/storage/azblob#section-readme). You can download blob data to various destinations, including a local file path, stream, or text string. You can also open a blob stream and read from it.
+This article shows how to download a blob using the [Azure Storage client module for Go](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/storage/azblob#section-readme). You can download blob data to various destinations, including a local file path, stream, or text string.
 
 [!INCLUDE [storage-dev-guide-prereqs-go](../../../includes/storage-dev-guides/storage-dev-guide-prereqs-go.md)]
 
 ## Set up your environment
 
 [!INCLUDE [storage-dev-guide-project-setup-go](../../../includes/storage-dev-guides/storage-dev-guide-project-setup-go.md)]
 
-### Authorization
+#### Authorization
 
-The authorization mechanism must have the necessary permissions to perform a download operation. For authorization with Microsoft Entra ID (recommended), you need Azure RBAC built-in role **Storage Blob Data Contributor** or higher. To learn more, see the authorization guidance for [Get Blob](/rest/api/storageservices/get-blob#authorization).
+The authorization mechanism must have the necessary permissions to perform a download operation. For authorization with Microsoft Entra ID (recommended), you need Azure RBAC built-in role **Storage Blob Data Reader** or higher. To learn more, see the authorization guidance for [Get Blob](/rest/api/storageservices/get-blob#authorization).
 
 ## Download a blob
 
@@ -49,6 +49,8 @@ The following example downloads a blob to a stream, and reads from the stream by
 
 :::code language="go" source="~/blob-devguide-go/cmd/download-blob/download_blob.go" id="snippet_download_blob_stream":::
 
+[!INCLUDE [storage-dev-guide-code-samples-note-go](../../../includes/storage-dev-guides/storage-dev-guide-code-samples-note-go.md)]
+
 ## Resources
 
 To learn more about how to download blobs using the Azure Blob Storage client module for Go, see the following resources.

articles/storage/blobs/storage-blob-go-get-started.md

@@ -31,13 +31,19 @@ This article shows you how to connect to Azure Blob Storage by using the Azure B
 
 This section walks you through preparing a project to work with the Azure Blob Storage client module for Go.
 
-From your project directory, install packages for the Azure Blob Storage and Azure Identity client libraries using the `go get` command. The **azidentity** package is needed for passwordless connections to Azure services.
+From your GOPATH, install the [azblob](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/) module using the following command:
 
 ```console
-go get github.com/Azure/azure-sdk-for-go/sdk/storage/azblob github.com/Azure/azure-sdk-for-go/sdk/azidentity
+go get github.com/Azure/azure-sdk-for-go/sdk/storage/azblob
 ```
 
-Then open your code file and add the necessary import statements. In this example, we add the following to our *.go* file:
+To authenticate with Microsoft Entra ID (recommended), install the [`azidentity`](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/azidentity) module using the following command:
+
+```console
+go get github.com/Azure/azure-sdk-for-go/sdk/azidentity
+```
+
+Then open your code file and add the necessary import paths. In this example, we add the following to our *.go* file:
 
 ```go
 import (
@@ -46,7 +52,7 @@ import (
 )
 ```
 
-Blob client library information:
+Blob client module information:
 
 - [azblob](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/storage/azblob#section_documentation): Contains the methods that you can use to operate on the service, containers, and blobs.
 
@@ -57,7 +63,7 @@ To connect an application to Blob Storage, create a client object using [azblob.
 
 To learn more about creating and managing client objects, including best practices, see [Create and manage client objects that interact with data resources](storage-blob-client-management.md).
 
-You can authorize a client object using a Microsoft Entra authorization token, an account access key, or a shared access signature (SAS).
+You can authorize a client object using a Microsoft Entra authorization token (recommended), an account access key, or a shared access signature (SAS).
 
 <a name='azure-ad'></a>
 
@@ -81,13 +87,15 @@ To use a shared access signature (SAS) token, append the token to the account UR
 
 :::code language="go" source="~/blob-devguide-go/cmd/client-auth/client_auth.go" id="snippet_get_service_client_SAS":::
 
+> [!NOTE]
+> A user delegation SAS offers superior security to a SAS that is signed with the storage account key. Microsoft recommends using a user delegation SAS when possible. For more information, see [Grant limited access to data with shared access signatures (SAS)](../articles/storage/common/storage-sas-overview.md).
+
 ## [Account key](#tab/account-key)
 
 To use a storage account shared key, provide the key as a string and initialize a client object using [azblob.NewClientWithSharedKeyCredential](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/storage/azblob#NewClientWithSharedKeyCredential).
 
 :::code language="go" source="~/blob-devguide-go/cmd/client-auth/client_auth.go" id="snippet_get_service_client_shared_key":::
 
-
 You can also create a client object using a connection string.
 
 :::code language="go" source="~/blob-devguide-go/cmd/client-auth/client_auth.go" id="Snippet_get_service_client_connection_string":::
@@ -103,7 +111,7 @@ For information about how to obtain account keys and best practice guidelines fo
 
 As you build applications to work with data resources in Azure Blob Storage, your code primarily interacts with three resource types: storage accounts, containers, and blobs. To learn more about these resource types, how they relate to one another, and how apps interact with resources, see [Understand how apps interact with Blob Storage data resources](storage-blob-object-model.md).
 
-The following guides show you how to work with data resources and perform specific actions using the Azure Storage client library for Go:
+The following guides show you how to work with data resources and perform specific actions using the Azure Blob Storage client module for Go:
 
 | Guide | Description |
 |--|---|
@@ -116,3 +124,5 @@ The following guides show you how to work with data resources and perform specif
 | [List blobs](storage-blobs-list-go.md) | List blobs in different ways. |
 | [Delete and restore blobs](storage-blob-delete-go.md) | Delete blobs, and if soft-delete is enabled, restore deleted blobs.  |
 | [Manage properties and metadata (blobs)](storage-blob-properties-metadata-go.md) | Manage container properties and metadata. |
+
+[!INCLUDE [storage-dev-guide-code-samples-note-go](../../../includes/storage-dev-guides/storage-dev-guide-code-samples-note-go.md)]

articles/storage/blobs/storage-blob-properties-metadata-go.md

@@ -25,7 +25,7 @@ In addition to the data they contain, blobs support system properties and user-d
 
 [!INCLUDE [storage-dev-guide-project-setup-go](../../../includes/storage-dev-guides/storage-dev-guide-project-setup-go.md)]
 
-### Authorization
+#### Authorization
 
 The authorization mechanism must have the necessary permissions to work with container properties or metadata. For authorization with Microsoft Entra ID (recommended), you need Azure RBAC built-in role **Storage Blob Data Reader** or higher for the *get* operations, and **Storage Blob Data Contributor** or higher for the *set* operations. To learn more, see the authorization guidance for [Set Blob Properties](/rest/api/storageservices/set-blob-properties#authorization), [Get Blob Properties](/rest/api/storageservices/get-blob-properties#authorization), [Set Blob Metadata](/rest/api/storageservices/set-blob-metadata#authorization), or [Get Blob Metadata](/rest/api/storageservices/get-blob-metadata#authorization).
 
@@ -78,6 +78,8 @@ The following code example reads metadata on a blob and prints each key/value pa
 
 :::code language="go" source="~/blob-devguide-go/cmd/blob-properties-metadata/blob_properties_metadata.go" id="snippet_get_blob_metadata":::
 
+[!INCLUDE [storage-dev-guide-code-samples-note-go](../../../includes/storage-dev-guides/storage-dev-guide-code-samples-note-go.md)]
+
 ## Resources
 
 To learn more about how to manage system properties and user-defined metadata using the Azure Blob Storage client module for Go, see the following resources.

articles/storage/blobs/storage-blob-upload-go.md

@@ -25,7 +25,7 @@ This article shows how to upload a blob using the [Azure Storage client module f
 
 [!INCLUDE [storage-dev-guide-project-setup-go](../../../includes/storage-dev-guides/storage-dev-guide-project-setup-go.md)]
 
-### Authorization
+#### Authorization
 
 The authorization mechanism must have the necessary permissions to upload a blob. For authorization with Microsoft Entra ID (recommended), you need Azure RBAC built-in role **Storage Blob Data Contributor** or higher. To learn more, see the authorization guidance for [Put Blob](/rest/api/storageservices/put-blob#authorization) and [Put Block](/rest/api/storageservices/put-block#authorization).
 
@@ -80,6 +80,8 @@ The following code example shows how to specify data transfer options using the
 
 :::code language="go" source="~/blob-devguide-go/cmd/upload-blob/upload_blob.go" id="snippet_upload_blob_transfer_options":::
 
+[!INCLUDE [storage-dev-guide-code-samples-note-go](../../../includes/storage-dev-guides/storage-dev-guide-code-samples-note-go.md)]
+
 ## Resources
 
 To learn more about uploading blobs using the Azure Blob Storage client module for Go, see the following resources.

articles/storage/blobs/storage-blobs-list-go.md

@@ -25,7 +25,7 @@ This article shows how to list blobs using the [Azure Storage client module for
 
 [!INCLUDE [storage-dev-guide-project-setup-go](../../../includes/storage-dev-guides/storage-dev-guide-project-setup-go.md)]
 
-### Authorization
+#### Authorization
 
 The authorization mechanism must have the necessary permissions to upload a blob. For authorization with Microsoft Entra ID (recommended), you need Azure RBAC built-in role **Storage Blob Data Reader** or higher. To learn more, see the authorization guidance for [List Blobs](/rest/api/storageservices/list-blobs#authorization).
 
@@ -63,6 +63,9 @@ To organize blobs into virtual directories, use a delimiter character in the blo
 
 If you name your blobs using a delimiter, then you can choose to list blobs hierarchically. For a hierarchical listing operation, Azure Storage returns any virtual directories and blobs beneath the parent object. You can call the listing operation recursively to traverse the hierarchy, similar to how you would traverse a classic file system programmatically.
 
+> [!NOTE]
+> Blob snapshots cannot be listed in a hierarchical listing operation.
+
 ## Use a flat listing
 
 By default, a listing operation returns blobs in a flat listing. In a flat listing, blobs aren't organized by virtual directory.
@@ -124,8 +127,7 @@ Blob: folderA/folderB/file2.txt
 Blob: folderA/folderB/file3.txt
 ```
 
-> [!NOTE]
-> Blob snapshots cannot be listed in a hierarchical listing operation.
+[!INCLUDE [storage-dev-guide-code-samples-note-go](../../../includes/storage-dev-guides/storage-dev-guide-code-samples-note-go.md)]
 
 ## Resources