Skip to content

Commit 6e0f197

Browse files
committed
fix links
1 parent e5e528d commit 6e0f197

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,12 +25,12 @@ Azure NetApp Files volume encryption with customer-managed keys with the managed
2525
* Customer-managed keys with managed HSM is supported using the 2022.11 or later API version.
2626
* Customer-managed keys with managed HSM is only supported for Azure NetApp Files accounts that don't have existing encryption.
2727
* Before creating a volume using customer-managed key with managed HSM volume, you must have:
28-
* created an [Azure Key Vault](../key-vault/general/overview.md), containing at least one key.
28+
* created an [Azure Key Vault](/azure/key-vault/general/overview), containing at least one key.
2929
* The key vault must have soft delete and purge protection enabled.
3030
* The key must be type RSA.
3131
* created a VNet with a subnet delegated to Microsoft.Netapp/volumes.
3232
* a user- or system-assigned identity for your Azure NetApp Files account.
33-
* [provisioned and activated a managed HSM.](../key-vault/managed-hsm/quick-create-cli.md)
33+
* [provisioned and activated a managed HSM.](/azure/key-vault/managed-hsm/quick-create-cli)
3434

3535
## Supported regions
3636

@@ -115,7 +115,7 @@ To use a system-assigned identity, the Azure Key Vault must be configured to use
115115
* "Microsoft.KeyVault/vaults/keys/read"
116116
* "Microsoft.KeyVault/vaults/keys/encrypt/action"
117117
* "Microsoft.KeyVault/vaults/keys/decrypt/action"
118-
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)
118+
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](/azure/key-vault/general/rbac-guide#using-azure-rbac-secret-key-and-certificate-permissions-with-key-vault)
119119
120120
:::image type="content" source="./media/configure-customer-managed-keys/encryption-user-assigned.png" alt-text="Screenshot of user-assigned submenu." lightbox="./media/configure-customer-managed-keys/encryption-user-assigned.png":::
121121

0 commit comments

Comments
 (0)