You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|Set-AzDataLakeStoreItemOwner<br>Set-AzDataLakeStoreItemPermission<br>Set-AzDataLakeStoreItemAcl|Update-AzDataLakeGen2Item|The Update-AzDataLakeGen2Item cmdlet updates a single item only, and not recursively. If want to update recursively, list items by using the Get-AzDataLakeStoreChildItem cmdlet, then pipeline to the Update-AzDataLakeGen2Item cmdlet.|
287
-
|Test-AzDataLakeStoreItem|Get-AzDataLakeGen2Item|The Get-AzDataLakeGen2Item cmdlet will report an error if the item doesn't exist.|
287
+
|Test-AzDataLakeStoreItem|Get-AzDataLakeGen2Item|The Get-AzDataLakeGen2Item cmdlet reports an error if the item doesn't exist.|
Copy file name to clipboardExpand all lines: articles/storage/blobs/data-lake-storage-explorer-acl.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,14 @@
1
1
---
2
2
title: 'Storage Explorer: Set ACLs in Azure Data Lake Storage Gen2'
3
3
titleSuffix: Azure Storage
4
-
description: Use the Azure Storage Explorer to manage access control lists (ACLs) in storage accounts that has hierarchical namespace (HNS) enabled.
4
+
description: Use the Azure Storage Explorer to manage access control lists (ACLs) in storage accounts that have hierarchical namespace (HNS) enabled.
5
5
author: jimmart-dev
6
6
7
7
ms.subservice: data-lake-storage-gen2
8
8
ms.service: storage
9
9
ms.topic: how-to
10
-
ms.date: 10/28/2021
10
+
ms.date: 03/09/2023
11
11
ms.author: jammart
12
-
ms.reviewer: stewu
13
12
---
14
13
15
14
# Use Azure Storage Explorer to manage ACLs in Azure Data Lake Storage Gen2
@@ -32,7 +31,7 @@ This article shows you how to modify the ACL of file or directory and how to app
32
31
33
32
- Your user identity has been assigned the [Storage Blob Data Owner](../../role-based-access-control/built-in-roles.md#storage-blob-data-owner) role in the scope of the either the target container, storage account, parent resource group or subscription.
34
33
35
-
- You are the owning user of the target container, directory, or blob to which you plan to apply ACL settings.
34
+
- You're the owning user of the target container, directory, or blob to which you plan to apply ACL settings.
36
35
37
36
> [!NOTE]
38
37
> Storage Explorer makes use of both the Blob (blob) & Data Lake Storage Gen2 (dfs) [endpoints](../common/storage-private-endpoints.md#private-endpoints-for-azure-storage) when working with Azure Data Lake Storage Gen2. If access to Azure Data Lake Storage Gen2 is configured using private endpoints, ensure that two private endpoints are created for the storage account: one with the target sub-resource `blob` and the other with the target sub-resource `dfs`.
@@ -49,7 +48,7 @@ In the **Select Azure Environment** panel, select an Azure environment to sign i
49
48
50
49
:::image type="content" alt-text="Screenshot that shows Microsoft Azure Storage Explorer, and highlights the Select Azure Environment option." source="./media/data-lake-storage-explorer-acl/storage-explorer-select-sml.png" lightbox="./media/data-lake-storage-explorer-acl/storage-explorer-select-sml.png":::
51
50
52
-
Storage Explorer will open a webpage for you to sign in.
51
+
Storage Explorer opens a webpage for you to sign in.
53
52
54
53
After you successfully sign in with an Azure account, the account and the Azure subscriptions associated with that account appear under **ACCOUNT MANAGEMENT**. Select the Azure subscriptions that you want to work with, and then select **Open Explorer**.
55
54
@@ -61,7 +60,7 @@ When it completes connecting, Azure Storage Explorer loads with the **Explorer**
61
60
62
61
## Manage an ACL
63
62
64
-
Right-click the container, a directory, or a file, and then click**Manage Access Control Lists**. The following screenshot shows the menu as it appears when you right-click a directory.
63
+
Right-click the container, a directory, or a file, and then select**Manage Access Control Lists**. The following screenshot shows the menu as it appears when you right-click a directory.
65
64
66
65
> [!div class="mx-imgBorder"]
67
66
> 
@@ -82,7 +81,7 @@ Use the check box controls to set access and default ACLs. To learn more about t
82
81
83
82
You can apply ACL entries recursively on the existing child items of a parent directory without having to make these changes individually for each child item.
84
83
85
-
To apply ACL entries recursively, Right-click the container or a directory, and then click**Propagate Access Control Lists**. The following screenshot shows the menu as it appears when you right-click a directory.
84
+
To apply ACL entries recursively, Right-click the container or a directory, and then select**Propagate Access Control Lists**. The following screenshot shows the menu as it appears when you right-click a directory.
86
85
87
86
> [!div class="mx-imgBorder"]
88
87
> 
Copy file name to clipboardExpand all lines: articles/storage/blobs/data-lake-storage-explorer.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,14 +7,13 @@ author: normesta
7
7
ms.subservice: data-lake-storage-gen2
8
8
ms.service: storage
9
9
ms.topic: how-to
10
-
ms.date: 10/28/2021
10
+
ms.date: 03/09/2023
11
11
ms.author: normesta
12
-
ms.reviewer: stewu
13
12
---
14
13
15
14
# Use Azure Storage Explorer to manage directories and files in Azure Data Lake Storage Gen2
16
15
17
-
This article shows you how to use [Azure Storage Explorer](https://azure.microsoft.com/features/storage-explorer/) to create and manage directories and files in storage accounts that has hierarchical namespace (HNS) enabled.
16
+
This article shows you how to use [Azure Storage Explorer](https://azure.microsoft.com/features/storage-explorer/) to create and manage directories and files in storage accounts that have hierarchical namespace (HNS) enabled.
18
17
19
18
## Prerequisites
20
19
@@ -39,7 +38,7 @@ In the **Select Azure Environment** panel, select an Azure environment to sign i
39
38
40
39
:::image type="content" alt-text="Screenshot that shows Microsoft Azure Storage Explorer, and highlights the Select Azure Environment option." source="./media/data-lake-storage-explorer/storage-explorer-select-sml.png" lightbox="./media/data-lake-storage-explorer-acl/storage-explorer-select-sml.png":::
41
40
42
-
Storage Explorer will open a webpage for you to sign in.
41
+
Storage Explorer opens a webpage for you to sign in.
43
42
44
43
After you successfully sign in with an Azure account, the account and the Azure subscriptions associated with that account appear under **ACCOUNT MANAGEMENT**. Select the Azure subscriptions that you want to work with, and then select **Open Explorer**.
45
44
@@ -55,7 +54,7 @@ A container holds directories and files. To create one, expand the storage accou
55
54
56
55
:::image type="content" alt-text="Microsoft Azure Storage Explorer - Create a container" source="./media/data-lake-storage-explorer/creating-a-filesystem-sml.png" lightbox="./media/data-lake-storage-explorer/creating-a-filesystem-lrg.png" :::
57
56
58
-
Enter the name for your container. See the [Create a container](storage-quickstart-blobs-dotnet.md#create-a-container) section for a list of rules and restrictions on naming containers. When complete, press **Enter** to create the container. After the container has been successfully created, it is displayed under the **Blob Containers** folder for the selected storage account.
57
+
Enter the name for your container. See the [Create a container](storage-quickstart-blobs-dotnet.md#create-a-container) section for a list of rules and restrictions on naming containers. When complete, press **Enter** to create the container. After the container has been successfully created, it's displayed under the **Blob Containers** folder for the selected storage account.
@@ -83,7 +82,7 @@ In the **Azure Storage Explorer** application, select a directory under a storag
83
82
84
83
## Download blobs
85
84
86
-
To download files by using **Azure Storage Explorer**, with a file selected, select **Download** from the ribbon. A file dialog opens and provides you the ability to enter a file name. Select **Select Folder** to start the download of a file to the local location.
85
+
To download files by using **Azure Storage Explorer**, with a file selected, select **Download** from the ribbon. A file dialog opens and provides you with the ability to enter a file name. Select **Select Folder** to start the download of a file to the local location.
87
86
88
87
:::image type="content" alt-text="Microsoft Azure Storage Explorer - download blobs from a directory" source="media/data-lake-storage-explorer/storage-explorer-download-blob-sml.png" lightbox="media/data-lake-storage-explorer/storage-explorer-download-blob-sml.png" :::
Copy file name to clipboardExpand all lines: articles/storage/blobs/data-lake-storage-known-issues.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: normesta
7
7
ms.service: storage
8
8
ms.subservice: data-lake-storage-gen2
9
9
ms.topic: conceptual
10
-
ms.date: 11/03/2022
10
+
ms.date: 03/09/2023
11
11
ms.author: normesta
12
12
ms.reviewer: jamesbak
13
13
---
@@ -41,11 +41,11 @@ Data Lake Storage Gen2 APIs, NFS 3.0, and Blob APIs can operate on the same data
41
41
42
42
This section describes issues and limitations with using blob APIs, NFS 3.0, and Data Lake Storage Gen2 APIs to operate on the same data.
43
43
44
-
- You cannot use blob APIs, NFS 3.0, and Data Lake Storage APIs to write to the same instance of a file. If you write to a file by using Data Lake Storage Gen2 APIs or NFS 3.0, then that file's blocks won't be visible to calls to the [Get Block List](/rest/api/storageservices/get-block-list) blob API. The only exception is when you are overwriting. You can overwrite a file/blob using either API or with NFS 3.0 by using the zero-truncate option.
44
+
- You can't use blob APIs, NFS 3.0, and Data Lake Storage APIs to write to the same instance of a file. If you write to a file by using Data Lake Storage Gen2 APIs or NFS 3.0, then that file's blocks won't be visible to calls to the [Get Block List](/rest/api/storageservices/get-block-list) blob API. The only exception is when you're overwriting. You can overwrite a file/blob using either API or with NFS 3.0 by using the zero-truncate option.
45
45
46
-
- When you use the [List Blobs](/rest/api/storageservices/list-blobs) operation without specifying a delimiter, the results will include both directories and blobs. If you choose to use a delimiter, use only a forward slash (`/`). This is the only supported delimiter.
46
+
- When you use the [List Blobs](/rest/api/storageservices/list-blobs) operation without specifying a delimiter, the results include both directories and blobs. If you choose to use a delimiter, use only a forward slash (`/`). This is the only supported delimiter.
47
47
48
-
- If you use the [Delete Blob](/rest/api/storageservices/delete-blob) API to delete a directory, that directory will be deleted only if it's empty. This means that you can't use the Blob API delete directories recursively.
48
+
- If you use the [Delete Blob](/rest/api/storageservices/delete-blob) API to delete a directory, that directory is deleted only if it's empty. This means that you can't use the Blob API delete directories recursively.
49
49
50
50
These Blob REST APIs aren't supported:
51
51
@@ -55,13 +55,13 @@ These Blob REST APIs aren't supported:
-[Put Page from URL](/rest/api/storageservices/put-page-from-url)
57
57
58
-
Unmanaged VM disks are not supported in accounts that have a hierarchical namespace. If you want to enable a hierarchical namespace on a storage account, place unmanaged VM disks into a storage account that doesn't have the hierarchical namespace feature enabled.
58
+
Unmanaged VM disks aren't supported in accounts that have a hierarchical namespace. If you want to enable a hierarchical namespace on a storage account, place unmanaged VM disks into a storage account that doesn't have the hierarchical namespace feature enabled.
59
59
60
60
<aid="api-scope-data-lake-client-library"></a>
61
61
62
62
## Support for setting access control lists (ACLs) recursively
63
63
64
-
The ability to apply ACL changes recursively from parent directory to child items is generally available. In the current release of this capability, you can apply ACL changes by using Azure Storage Explorer, PowerShell, Azure CLI, and the .NET, Java, and Python SDK. Support is not yet available for the Azure portal.
64
+
The ability to apply ACL changes recursively from parent directory to child items is generally available. In the current release of this capability, you can apply ACL changes by using Azure Storage Explorer, PowerShell, Azure CLI, and the .NET, Java, and Python SDK. Support isn't yet available for the Azure portal.
65
65
66
66
## Access control lists (ACL) and anonymous read access
67
67
@@ -71,7 +71,7 @@ If [anonymous read access](./anonymous-read-access-overview.md) has been granted
71
71
72
72
## AzCopy
73
73
74
-
Use only the latest version of AzCopy ([AzCopy v10](../common/storage-use-azcopy-v10.md?toc=/azure/storage/tables/toc.json)). Earlier versions of AzCopy such as AzCopy v8.1, are not supported.
74
+
Use only the latest version of AzCopy ([AzCopy v10](../common/storage-use-azcopy-v10.md?toc=/azure/storage/tables/toc.json)). Earlier versions of AzCopy such as AzCopy v8.1, aren't supported.
75
75
76
76
<aid="storage-explorer"></a>
77
77
@@ -94,17 +94,17 @@ Third party applications that use REST APIs to work will continue to work if you
94
94
95
95
## Windows Azure Storage Blob (WASB) driver
96
96
97
-
Currently, the WASB driver, which was designed to work with the Blob API only, encounters problems in a few common scenarios. Specifically, when it is a client to a hierarchical namespace enabled storage account. Multi-protocol access on Data Lake Storage won't mitigate these issues.
97
+
Currently, the WASB driver, which was designed to work with the Blob API only, encounters problems in a few common scenarios. Specifically, when it's a client to a hierarchical namespace enabled storage account. Multi-protocol access on Data Lake Storage won't mitigate these issues.
98
98
99
-
Using the WASB driver as a client to a hierarchical namespace enabled storage account is not supported. Instead, we recommend that you use the [Azure Blob File System (ABFS)](data-lake-storage-abfs-driver.md) driver in your Hadoop environment. If you are trying to migrate off of an on-premises Hadoop environment with a version earlier than Hadoop branch-3, then please open an Azure Support ticket so that we can get in touch with you on the right path forward for you and your organization.
99
+
Using the WASB driver as a client to a hierarchical namespace enabled storage account isn't supported. Instead, we recommend that you use the [Azure Blob File System (ABFS)](data-lake-storage-abfs-driver.md) driver in your Hadoop environment. If you're trying to migrate off of an on-premises Hadoop environment with a version earlier than Hadoop branch-3, then please open an Azure Support ticket so that we can get in touch with you on the right path forward for you and your organization.
100
100
101
101
## Soft delete for blobs capability
102
102
103
103
If parent directories for soft-deleted files or directories are renamed, the soft-deleted items may not be displayed correctly in the Azure portal. In such cases you can use [PowerShell](soft-delete-blob-manage.md?tabs=dotnet#restore-soft-deleted-blobs-and-directories-by-using-powershell) or [Azure CLI](soft-delete-blob-manage.md?tabs=dotnet#restore-soft-deleted-blobs-and-directories-by-using-azure-cli) to list and restore the soft-deleted items.
104
104
105
105
## Events
106
106
107
-
If your account has an event subscription, read operations on the secondary endpoint will result in an error. To resolve this issue, remove event subscriptions. Using the dfs endpoint (abfss://URI) for non-hierarchical namespace enabled accounts will not generate events, but the blob endpoint (wasb:// URI) will generate events.
107
+
If your account has an event subscription, read operations on the secondary endpoint will result in an error. To resolve this issue, remove event subscriptions. Using the Data Lake Storage endpoint (abfss://URI) for non-hierarchical namespace enabled accounts won't generate events, but the blob endpoint (wasb:// URI) will generate events.
108
108
109
109
> [!TIP]
110
110
> Read access to the secondary endpoint is available only when you enable read-access geo-redundant storage (RA-GRS) or read-access geo-zone-redundant storage (RA-GZRS).
0 commit comments