Skip to content

Commit 4354a6e

Browse files
committed
acrolinx
1 parent dee1720 commit 4354a6e

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

articles/azure-netapp-files/configure-customer-managed-keys-hardware.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Azure NetApp Files volume encryption with customer-managed keys with the managed
2424

2525

2626
* Customer-managed keys with managed HSM is supported using the 2022.11 or later API version.
27-
* Customer-managed keys with managed HSM is only supported for Azure NetApp Files accounts that do not have existing encryption.
27+
* Customer-managed keys with managed HSM is only supported for Azure NetApp Files accounts that don't have existing encryption.
2828
* Before creating a volume using customer-managed key with managed HSM volume, you must have:
2929
* created an [Azure Key Vault](../key-vault/general/overview.md), containing at least one key.
3030
* The key vault must have soft delete and purge protection enabled.
@@ -162,7 +162,7 @@ To use a system-assigned identity, the Azure Key Vault must be configured to use
162162
1. In the Azure portal, navigate to Azure NetApp Files then select **Encryption**.
163163
1. In the **Encryption** menu, provide the following values:
164164
* For **Encryption key source**, select **Customer Managed Key**.
165-
* For **Key URI**, select **Enter Key URI** the provide the URI for the managed HSM.
165+
* For **Key URI**, select **Enter Key URI** then provide the URI for the managed HSM.
166166
* Select the NetApp **Subscription**.
167167
* For **Identity type**, select **User-assigned**.
168168
1. When you select **User-assigned**, a context pane opens to select the identity.
@@ -171,11 +171,10 @@ To use a system-assigned identity, the Azure Key Vault must be configured to use
171171
* "Microsoft.KeyVault/vaults/keys/read"
172172
* "Microsoft.KeyVault/vaults/keys/encrypt/action"
173173
* "Microsoft.KeyVault/vaults/keys/decrypt/action"
174-
The user-assigned identity you select is added to your NetApp account. Due to RBAC being customizable, the Azure portal does not configure access to the key vault. For more information, see [Using Azure RBAC secret, key, and certificate permissions with Key Vault](../key-vault/general/rbac-guide.md#using-azure-rbac-secret-key-and-certificate-permissions-with-key-vault)
174+
The user-assigned identity you select is added to your NetApp account. Due to RBAC being customizable, the Azure portal doesn't configure access to the key vault. For more information, see [Using Azure RBAC secret, key, and certificate permissions with Key Vault](../key-vault/general/rbac-guide.md#using-azure-rbac-secret-key-and-certificate-permissions-with-key-vault)
175175
176176
:::image type="content" source="../media/azure-netapp-files/encryption-user-assigned.png" alt-text="Screenshot of user-assigned submenu." lightbox="../media/azure-netapp-files/encryption-user-assigned.png":::
177177
178-
179178
1. Select **Save**.
180179
181180
## Next steps

0 commit comments

Comments
 (0)