Skip to content

Commit e6ae75a

Browse files
committed
reword paragraph about referencing 'blob' endpoint during copy operations
1 parent 09addbb commit e6ae75a

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

articles/storage/common/storage-private-endpoints.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: jimmart-dev
77

88
ms.service: storage
99
ms.topic: conceptual
10-
ms.date: 03/03/2023
10+
ms.date: 06/22/2023
1111
ms.author: jammart
1212
ms.reviewer: santoshc
1313
ms.subservice: common
@@ -65,7 +65,6 @@ When you create a private endpoint, you must specify the storage account and the
6565

6666
You need a separate private endpoint for each storage resource that you need to access, namely [Blobs](../blobs/storage-blobs-overview.md), [Data Lake Storage Gen2](../blobs/data-lake-storage-introduction.md), [Files](../files/storage-files-introduction.md), [Queues](../queues/storage-queues-introduction.md), [Tables](../tables/table-storage-overview.md), or [Static Websites](../blobs/storage-blob-static-website.md). On the private endpoint, these storage services are defined as the **target sub-resource** of the associated storage account.
6767

68-
6968
If you create a private endpoint for the Data Lake Storage Gen2 storage resource, then you should also create one for the Blob Storage resource. That's because operations that target the Data Lake Storage Gen2 endpoint might be redirected to the Blob endpoint. Similarly, if you add a private endpoint for Blob Storage only, and not for Data Lake Storage Gen2, some operations (such as Manage ACL, Create Directory, Delete Directory, etc.) will fail since the Gen2 APIs require a DFS private endpoint. By creating a private endpoint for both resources, you ensure that all operations can complete successfully.
7069

7170
> [!TIP]
@@ -148,12 +147,11 @@ Clients in VNets with existing private endpoints face constraints when accessing
148147

149148
This constraint is a result of the DNS changes made when account A2 creates a private endpoint.
150149

151-
152150
### Copying blobs between storage accounts
153151

154152
You can copy blobs between storage accounts by using private endpoints only if you use the Azure REST API, or tools that use the REST API. These tools include AzCopy, Storage Explorer, Azure PowerShell, Azure CLI, and the Azure Blob Storage SDKs.
155153

156-
Only private endpoints that target the Blob storage resource are supported. Private endpoints that target the Data Lake Storage Gen2 or the File resource are not yet supported. Also, copying between storage accounts by using the Network File System (NFS) protocol is not yet supported.
154+
Only private endpoints that target the `blob` storage resource endpoint are supported. This includes REST API calls against Data Lake Storage Gen2 accounts in which the `blob` resource endpoint is referenced explicitly or implicitly. Private endpoints that target the Data Lake Storage Gen2 `dfs` endpoint or the `file` resource endpoint are not yet supported. Copying between storage accounts by using the Network File System (NFS) protocol is not yet supported.
157155

158156
## Next steps
159157

0 commit comments

Comments
 (0)