Skip to content

Commit 5a93d41

Browse files
committed
edit pass: azure-files-authorization-and-access-control
1 parent 2723f49 commit 5a93d41

2 files changed

Lines changed: 14 additions & 14 deletions

File tree

articles/storage/files/authorize-data-operations-portal.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ You can change the authentication method for individual file shares. By default,
8989

9090
### Authenticate by using your Microsoft Entra account (recommended)
9191

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.
9393

9494
Two additional RBAC permissions are required to use your Entra account:
9595

@@ -100,7 +100,7 @@ No file shares appear in the list if your Entra account lacks permissions to vie
100100

101101
### Authenticate by using the storage account access key (not recommended)
102102

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.
104104

105105
No file shares appear in the list if you don't have access to the storage account access key.
106106

articles/storage/files/files-managed-identities.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.author: kendownie
99
ms.custom:
1010
- devx-track-azurepowershell
1111
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.
1313
---
1414

1515
# Access SMB Azure file shares by using managed identities with Microsoft Entra ID (preview)
@@ -42,15 +42,15 @@ Benefits include:
4242

4343
Azure provides two types of managed identities: *system assigned* and *user assigned*.
4444

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.
4646

4747
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.
4848

4949
Although you can configure both user-assigned and system-assigned managed identities on a single VM, we recommend using one or the other.
5050

5151
## Prerequisites
5252

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.
5454

5555
The clients that need to authenticate by using a managed identity shouldn't be joined to any domain.
5656

@@ -62,15 +62,15 @@ To enable the `SMBOAuth` property on your storage account, use either the Azure
6262

6363
### [Portal](#tab/portal)
6464

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.
6666

6767
:::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":::
6868

6969
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.
7070

7171
Go to the storage account. On the service menu, under **Settings**, select **Configuration**. Under **Managed Identity for SMB**, select **Enabled**, and then select **Save**.
7272

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":::
7474

7575
Next, [create an SMB file share](create-classic-file-share.md) on the storage account.
7676

@@ -129,7 +129,7 @@ To enable `SMBOAuth` on an existing storage account, run the following PowerShel
129129
Set-AzStorageAccount -ResourceGroupName <resource-group> -Name <storage-account-name> -EnableSmbOAuth $true
130130
```
131131

132-
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:
133133

134134
```powershell
135135
Set-AzStorageAccount -ResourceGroupName <resource-group> -Name <storage-account-name> -EnableSmbOAuth $true -AllowBlobPublicAccess $false
@@ -166,7 +166,7 @@ Follow these steps to enable a system-assigned managed identity on a Windows VM
166166

167167
1. You can enable a system-assigned managed identity during VM creation on the **Management** tab.
168168

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":::
170170

171171
#### Enable a user-assigned managed identity
172172

@@ -176,7 +176,7 @@ Follow these steps to enable a system-assigned managed identity on a Windows VM
176176

177177
### Assign a built-in RBAC role to the managed identity or application identity
178178

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.
180180

181181
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.
182182

@@ -192,7 +192,7 @@ Follow these steps to assign the built-in Azure RBAC role [Storage File Data SMB
192192

193193
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**.
194194

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**.
196196

197197
1. Select **Review + assign** to add the role assignment to the storage account.
198198

@@ -226,7 +226,7 @@ The managed identity can be either [system assigned or user assigned](/entra/ide
226226

227227
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).
228228

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.
230230

231231
### Assign a built-in RBAC role to the managed identity
232232

@@ -242,7 +242,7 @@ The managed identity can be either [system assigned or user assigned](/entra/ide
242242

243243
1. Under **Managed identity**, select the managed identity, and then click **Select**.
244244

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**.
246246

247247
1. Select **Review + assign** to add the role assignment to the storage account.
248248

@@ -583,7 +583,7 @@ const char* extern_smb_version();
583583
584584
### API description
585585
586-
The following table lists the API commands and their usage. Returned values follow standard C conventions (0 for success, nonzero for errors).
586+
The following table lists the API commands and their usage. Returned values follow standard C conventions (zero for success, nonzero for errors).
587587
588588
| **Command** | **Description** |
589589
|-------------|-----------------|

0 commit comments

Comments
 (0)