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
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -89,7 +89,7 @@ You can change the authentication method for individual file shares. By default,
89
89
90
90
### Authenticate by using your Microsoft Entra account (recommended)
91
91
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.
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, an error message says you don't have permissions to list the data by using your user account with Entra ID.
93
93
94
94
Two additional RBAC permissions are required to use your Entra account:
95
95
@@ -100,7 +100,7 @@ No file shares appear in the list if your Entra account lacks permissions to vie
100
100
101
101
### Authenticate by using the storage account access key (not recommended)
102
102
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.
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, an error message says you don't have permissions to use the access key to list data.
104
104
105
105
No file shares appear in the list if you don't have access to the storage account access key.
Copy file name to clipboardExpand all lines: articles/storage/files/files-managed-identities.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.author: kendownie
9
9
ms.custom:
10
10
- devx-track-azurepowershell
11
11
zone_pivot_groups: azure-files-windows-linux
12
-
# Customer intent: As a cloud administrator, I want to improve security by authenticating managed identities to allow applications and virtual machines to access SMB Azure Files shares by using identity-based authentication with Microsoft Entra ID instead of using a storage account key.
12
+
# Customer intent: As a cloud administrator, I want to improve security by authenticating managed identities to allow applications and virtual machines to access SMB Azure file shares by using identity-based authentication with Microsoft Entra ID instead of using a storage account key.
13
13
---
14
14
15
15
# Access SMB Azure file shares by using managed identities with Microsoft Entra ID (preview)
@@ -42,15 +42,15 @@ Benefits include:
42
42
43
43
Azure provides two types of managed identities: *system assigned* and *user assigned*.
44
44
45
-
A system-assigned managed identity is restricted to one per resource and is tied to the life cycle of this resource. You can grant permissions to the managed identity by using Azure role-based access control (Azure RBAC). The managed identity is authenticated with Microsoft Entra ID, so you don't have to store any credentials in code.
45
+
A system-assigned managed identity is restricted to one per resource and is tied to the life cycle of a resource. You can grant permissions to the managed identity by using Azure role-based access control (Azure RBAC). The managed identity is authenticated with Microsoft Entra ID, so you don't have to store any credentials in code.
46
46
47
47
User-assigned managed identities enable Azure resources to authenticate to cloud services without storing credentials in code. You create this type of managed identity as a standalone Azure resource with its own life cycle. A single resource, like a VM, can use multiple user-assigned managed identities. Also, multiple VMs can share a single user-assigned managed identity.
48
48
49
49
Although you can configure both user-assigned and system-assigned managed identities on a single VM, we recommend using one or the other.
50
50
51
51
## Prerequisites
52
52
53
-
This article assumes that you have an Azure subscription with permissions to create storage accounts and assign Azure RBAC roles. To assign roles, you need role-assignment write permission (`Microsoft.Authorization/roleAssignments/write`) at the scope where you want to assign the role.
53
+
This article assumes that you have an Azure subscription with permissions to create storage accounts and assign Azure RBAC roles. To assign roles, you need role-assignment write permission (`Microsoft.Authorization/roleAssignments/write`) at the required scope.
54
54
55
55
The clients that need to authenticate by using a managed identity shouldn't be joined to any domain.
56
56
@@ -62,15 +62,15 @@ To enable the `SMBOAuth` property on your storage account, use either the Azure
62
62
63
63
### [Portal](#tab/portal)
64
64
65
-
To create a new storage account with the `SMBOAuth` property enabled by using the Azure portal, follow [these steps](create-classic-file-share.md#create-a-storage-account). Under the **Advanced** tab, select the **Enable Managed Identity for SMB** checkbox.
65
+
To create a new storage account with the `SMBOAuth` property enabled by using the Azure portal, follow [these steps](create-classic-file-share.md#create-a-storage-account). On the **Advanced** tab, select the **Enable Managed Identity for SMB** checkbox.
66
66
67
67
:::image type="content" source="media/managed-identities/enable-managed-identity.png" alt-text="Screenshot that shows how to enable a managed identity for SMB when creating a new storage account by using the Azure portal." border="true":::
68
68
69
69
Alternatively, you can enable the `SMBOAuth` property on an existing storage account, as long as the storage account doesn't have any other identity source configured.
70
70
71
71
Go to the storage account. On the service menu, under **Settings**, select **Configuration**. Under **Managed Identity for SMB**, select **Enabled**, and then select **Save**.
72
72
73
-
:::image type="content" source="media/managed-identities/enable-managed-identity-on-existing-storage-account.png" alt-text="Screenshot that shows how to enable managed identity for SMB on an existing storage account by using the Azure portal." border="true":::
73
+
:::image type="content" source="media/managed-identities/enable-managed-identity-on-existing-storage-account.png" alt-text="Screenshot that shows how to enable a managed identity for SMB on an existing storage account by using the Azure portal." border="true":::
74
74
75
75
Next, [create an SMB file share](create-classic-file-share.md) on the storage account.
76
76
@@ -129,7 +129,7 @@ To enable `SMBOAuth` on an existing storage account, run the following PowerShel
If you errors say that the policy disallows the resource, you might have a policy set on your subscription that disallows `Set-AzStorageAccount`. To work around this problem, retry by using the following command:
132
+
If errors say that the policy disallows the resource, you might have a policy set on your subscription that disallows `Set-AzStorageAccount`. To work around this problem, retry by using the following command:
@@ -166,7 +166,7 @@ Follow these steps to enable a system-assigned managed identity on a Windows VM
166
166
167
167
1. You can enable a system-assigned managed identity during VM creation on the **Management** tab.
168
168
169
-
:::image type="content" source="media/managed-identities/enable-system-assigned-managed-identity.png" alt-text="Screenshot that shows how to enable system-assigned managed identity when creating a new VM by using the Azure portal." border="true":::
169
+
:::image type="content" source="media/managed-identities/enable-system-assigned-managed-identity.png" alt-text="Screenshot that shows how to enable a system-assigned managed identity when creating a new VM by using the Azure portal." border="true":::
170
170
171
171
#### Enable a user-assigned managed identity
172
172
@@ -176,7 +176,7 @@ Follow these steps to enable a system-assigned managed identity on a Windows VM
176
176
177
177
### Assign a built-in RBAC role to the managed identity or application identity
178
178
179
-
After you enable a managed identity, grant all necessary permissions through Azure RBAC. To assign roles, sign in as a user with role-assignment write permission at the scope where you want to assign the role.
179
+
After you enable a managed identity, grant all necessary permissions through Azure RBAC. To assign roles, sign in as a user with role-assignment write permission at the required scope.
180
180
181
181
Follow these steps to assign the built-in Azure RBAC role [Storage File Data SMB MI Admin](/azure/role-based-access-control/built-in-roles/storage#storage-file-data-smb-mi-admin). This role gives admin-level access for managed identities on files and directories in Azure Files.
182
182
@@ -192,7 +192,7 @@ Follow these steps to assign the built-in Azure RBAC role [Storage File Data SMB
192
192
193
193
1. For Azure VMs or Azure Arc identities, select the managed identity for your VM or Windows device. For application identities, search for and select the application identity. Click **Select**.
194
194
195
-
1.You should now see the managed identity or application identity listed under **Members**. Select **Next**.
195
+
1.Verify that the managed identity or application identity is listed under **Members**. Select **Next**.
196
196
197
197
1. Select **Review + assign** to add the role assignment to the storage account.
198
198
@@ -226,7 +226,7 @@ The managed identity can be either [system assigned or user assigned](/entra/ide
226
226
227
227
1. Sign in to the Azure portal and follow the steps to [create a user-assigned managed identity](/entra/identity/managed-identities-azure-resources/manage-user-assigned-managed-identities-azure-portal#create-a-user-assigned-managed-identity).
228
228
229
-
1. Go to the user-assigned managed identity you just created and copy the **Client ID** value. You need this value later.
229
+
1. Go to the user-assigned managed identity that you just created and copy the **Client ID** value. You need this value later.
230
230
231
231
### Assign a built-in RBAC role to the managed identity
232
232
@@ -242,7 +242,7 @@ The managed identity can be either [system assigned or user assigned](/entra/ide
242
242
243
243
1. Under **Managed identity**, select the managed identity, and then click **Select**.
244
244
245
-
1.You should now see the managed identity listed under **Members**. Select **Next**.
245
+
1.Verify that the managed identity is listed under **Members**. Select **Next**.
246
246
247
247
1. Select **Review + assign** to add the role assignment to the storage account.
0 commit comments