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
Copy file name to clipboardExpand all lines: articles/storage/files/authorize-data-operations-portal.md
+21-19Lines changed: 21 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Authorize Access to Azure File Share Data in the Azure Portal
3
-
description: When you access file data using the Azure portal, the portal makes requests to Azure Files behind the scenes. These requests can be authenticated and authorized using either your Microsoft Entra account or the storage account access key.
3
+
description: Learn how requests to Azure Files for accessing file data are authenticated and authorized through a Microsoft Entra account or a storage account access key.
4
4
author: khdownie
5
5
ms.service: azure-file-storage
6
6
ms.topic: how-to
@@ -15,9 +15,9 @@ ms.author: kendownie
15
15
16
16
When you access file data by using the [Azure portal](https://portal.azure.com?azure-portal=true), the portal makes requests to the Azure Files service behind the scenes. You can authorize these requests by using either your Microsoft Entra account (preferred) or the storage account access key (less secure).
17
17
18
-
The portal shows which method you're using and enables you to switch between the two methods if you have the appropriate permissions. By default, the portal uses whichever method you're already using to authorize all file shares, but you can change this setting for individual file share operations.
18
+
The portal shows which method you're using and enables you to switch between the two methods if you have the appropriate permissions. By default, the portal uses whichever method you're already using to authorize all file shares. You can change this setting for individual file share operations.
19
19
20
-
This article explains how to authorize access to file data in the Azure portal. It doesn't cover how to set up identity-based authentication to file shares for end users. To learn about identity-based authentication, see [Overview of Azure Files identity-based authentication](storage-files-active-directory-overview.md).
20
+
This article explains how to authorize access to file data in the Azure portal. It doesn't cover how to set up identity-based authentication to file shares for users. To learn about identity-based authentication, see [Overview of Azure Files identity-based authentication](storage-files-active-directory-overview.md).
21
21
22
22
> [!WARNING]
23
23
> Accessing a file share by using storage account keys has inherent security risks. Always authenticate by using Microsoft Entra when possible. For information on how to protect and manage your keys, see [Manage storage account access keys](../common/storage-account-keys-manage.md).
@@ -35,7 +35,7 @@ To access file data from the Azure portal by using your Entra account, both of t
35
35
- You're assigned either a built-in or custom role that provides access to file data.
36
36
- You're assigned the Azure Resource Manager [Reader](../../role-based-access-control/built-in-roles.md#reader) role, at a minimum, scoped to the level of the storage account or higher. The **Reader** role grants the most restricted permissions, but another Azure Resource Manager role that grants access to storage account management resources is also acceptable.
37
37
38
-
The Azure Resource Manager **Reader** role permits users to view storage account resources, but not modify them. It doesn't provide read permissions to data in Azure Storage, but only to account management resources. The **Reader** role is necessary so that users can navigate to file shares in the Azure portal.
38
+
The Azure Resource Manager **Reader** role permits users to view storage account resources, but not modify them. It doesn't provide read permissions to data in Azure Storage, but only to account management resources. The **Reader** role is necessary so that users can go to file shares in the Azure portal.
39
39
40
40
Two built-in roles have the required permissions to access file data by using OAuth:
41
41
@@ -47,27 +47,29 @@ For information about the built-in roles that support access to file data, see [
47
47
> [!NOTE]
48
48
> The **Storage File Data Privileged Contributor** role has permissions to read, write, delete, and modify ACLs/NTFS permissions on files and directories in Azure file shares. Modifying ACLs/NTFS permissions isn't supported via the Azure portal.
49
49
50
-
Custom roles can support different combinations of the same permissions provided by the built-in roles. For more information, see [Azure custom roles](../../role-based-access-control/custom-roles.md) and [Understand role definitions for Azure resources](../../role-based-access-control/role-definitions.md).
50
+
Custom roles can support different combinations of the same permissions that the built-in roles provide. For more information, see [Azure custom roles](../../role-based-access-control/custom-roles.md) and [Understand role definitions for Azure resources](../../role-based-access-control/role-definitions.md).
51
51
52
52
### Use the storage account access key (not recommended)
53
53
54
-
To access file data by using the storage account access key, you must have an Azure role assigned to you that includes the Azure RBAC action **Microsoft.Storage/storageAccounts/listkeys/action**. This Azure role can be a built-in role or a custom role. Built-in roles that support **Microsoft.Storage/storageAccounts/listkeys/action** include the following, listed in order from least to greatest permissions:
54
+
To access file data by using the storage account access key, you must have an Azure role assigned to you that includes the Azure RBAC action `Microsoft.Storage/storageAccounts/listkeys/action`. This Azure role can be a built-in role or a custom role. Built-in roles that support `Microsoft.Storage/storageAccounts/listkeys/action` include the following, listed in order from least to greatest permissions:
55
55
56
-
-The [Reader and Data Access role](../../role-based-access-control/built-in-roles.md#reader-and-data-access)
When you attempt to access file data in the Azure portal, the portal first checks whether you have a role with **Microsoft.Storage/storageAccounts/listkeys/action**. If you have a role with this action, the portal uses the storage account key for accessing file data. If you don't have a role with this action, the portal attempts to access data by using your Entra account.
61
+
When you attempt to access file data in the Azure portal, the portal first checks whether you have a role with `Microsoft.Storage/storageAccounts/listkeys/action`. If you have a role with this action, the portal uses the storage account key for accessing file data. If you don't have a role with this action, the portal attempts to access data by using your Entra account.
62
62
63
63
> [!IMPORTANT]
64
-
> When you lock a storage account by using a Resource Manager **ReadOnly** lock, you can't perform the [List Keys](/rest/api/storagerp/storageaccounts/listkeys) operation for that storage account. **List Keys** is a POST operation, and all POST operations are prevented when a **ReadOnly** lock is configured for the account. For this reason, when you lock the account by using a **ReadOnly** lock, you must use Entra credentials to access file data in the portal. For information about accessing file data in the Azure portal by using Microsoft Entra ID, see [Use your Microsoft Entra account](#use-your-azure-ad-account).
64
+
> When you lock a storage account by using a Resource Manager `ReadOnly` lock, you can't perform the [List Keys](/rest/api/storagerp/storageaccounts/listkeys) operation for that storage account. **List Keys** is a `POST` operation, and all `POST` operations are prevented when a `ReadOnly` lock is configured for the account.
65
+
>
66
+
> For this reason, when you lock the account by using a `ReadOnly` lock, you must use Entra credentials to access file data in the portal. For information about accessing file data in the Azure portal by using Microsoft Entra ID, see [Use your Microsoft Entra account](#use-your-azure-ad-account).
65
67
66
-
The classic subscription administrator roles **Service Administrator** and **Co-Administrator** include the equivalent of the Azure Resource Manager [Owner](../../role-based-access-control/built-in-roles.md#owner) role. The **Owner** role includes all actions, including the **Microsoft.Storage/storageAccounts/listkeys/action** action, so a user with one of these administrative roles can also access file data by using the storage account key. For more information, see [Azure roles, Microsoft Entra roles, and classic subscription administrator roles](../../role-based-access-control/rbac-and-directory-admin-roles.md#classic-subscription-administrator-roles).
68
+
The classic subscription administrator roles **Service Administrator** and **Co-Administrator** include the equivalent of the Azure Resource Manager [Owner](../../role-based-access-control/built-in-roles.md#owner) role. The **Owner** role includes all actions, including the `Microsoft.Storage/storageAccounts/listkeys/action` action. A user with one of these administrative roles can also access file data by using the storage account key. For more information, see [Azure roles, Microsoft Entra roles, and classic subscription administrator roles](../../role-based-access-control/rbac-and-directory-admin-roles.md#classic-subscription-administrator-roles).
67
69
68
70
## Specify how to authorize operations on a specific file share
69
71
70
-
You can change the authentication method for individual file shares. By default, the portal uses the current authentication method. To determine the current authentication method, follow these steps.
72
+
You can change the authentication method for individual file shares. By default, the portal uses the current authentication method. To determine the current authentication method, follow these steps:
71
73
72
74
1. In the Azure portal, go to your storage account.
73
75
@@ -87,7 +89,7 @@ You can change the authentication method for individual file shares. By default,
87
89
88
90
### Authenticate by using your Microsoft Entra account (recommended)
89
91
90
-
To switch to using your Entra account, select the link highlighted in the image that says **Switch to Microsoft Entra user account**. If you have the appropriate permissions through the Azure roles that are assigned to you, you can proceed. However, if you lack the necessary permissions, you see an error message that you don't have permissions to list the data by using your user account with Entra ID.
92
+
To switch to using your Entra account, select the link highlighted in the image that says **Switch to Microsoft Entra user account**. If you have the appropriate permissions through the Azure roles that are assigned to you, you can proceed. If you lack the necessary permissions, you see an error message that you don't have permissions to list the data by using your user account with Entra ID.
91
93
92
94
Two additional RBAC permissions are required to use your Entra account:
93
95
@@ -98,23 +100,23 @@ No file shares appear in the list if your Entra account lacks permissions to vie
98
100
99
101
### Authenticate by using the storage account access key (not recommended)
100
102
101
-
To switch to using the account access key, select the link that says **Switch to access key.** If you have access to the storage account key, you can proceed. However, if you don't have access to the account key, you see an error message that you don't have permissions to use the access key to list data.
103
+
To switch to using the account access key, select the link that says **Switch to access key**. If you have access to the storage account key, you can proceed. If you don't have access to the account key, you see an error message that you don't have permissions to use the access key to list data.
102
104
103
105
No file shares appear in the list if you don't have access to the storage account access key.
## Default to Microsoft Entra authorization in the Azure portal
108
110
109
-
When you create a new storage account, you can specify that the Azure portal defaults to authorization with Entra ID when a user navigates to file data. You can also configure this setting for an existing storage account. This setting specifies the default authorization method only. A user can override this setting and choose to authorize data access by using the storage account key.
111
+
When you create a new storage account, you can specify that the Azure portal defaults to authorization with Entra ID when a user accesses file data. You can also configure this setting for an existing storage account. This setting specifies the default authorization method only. A user can override this setting and choose to authorize data access by using the storage account key.
110
112
111
113
To specify that the portal uses Entra authorization by default for data access when you create a storage account, follow these steps:
112
114
113
115
1. Create a new storage account by following the instructions in [Create an Azure storage account](../common/storage-account-create.md).
114
116
115
-
1. On the **Advanced** tab, in the **Security** section, check the box next to **Default to Microsoft Entra authorization in the Azure portal**.
117
+
1. On the **Advanced** tab, in the **Security** section, select the **Default to Microsoft Entra authorization in the Azure portal** checkbox.
116
118
117
-
:::image type="content" source="media/authorize-data-operations-portal/default-auth-account-create-portal.png" alt-text="Screenshot that shows how to configure default Microsoft Entra authorization in Azure portal for new account.":::
119
+
:::image type="content" source="media/authorize-data-operations-portal/default-auth-account-create-portal.png" alt-text="Screenshot that shows how to configure default Microsoft Entra authorization in Azure portal for a new account.":::
118
120
119
121
1. Select **Review + create** to run validation and create the storage account.
0 commit comments