Skip to content

Commit cb863f5

Browse files
authored
1 parent 9b2d3bb commit cb863f5

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/relational-databases/security/encryption/setup-steps-for-extensible-key-management-using-the-azure-key-vault.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -390,7 +390,7 @@ In [step 2](#step-2-create-a-key-vault), we learned how to create a key vault an
390390
> [!NOTE]
391391
> When creating a credential to access the Managed HSM, the identity is `<name of Managed HSM>.managedhsm.azure.net`, which can be found in the Azure Key Vault Managed HSM **Overview** as the **HSM URI** in the Azure portal.
392392
>
393-
> Algorithm RSA-HSM_2048 and RSA-HSM_3072 are supported starting in SQL Server 2022 (16.x).
393+
> Algorithm RSA-HSM_2048 and RSA-HSM_3072 are supported starting in SQL Server 2022 (16.x) Cumulative Update 13.
394394
>
395395
> Automatic key rotation is supported in Azure Key Vault Managed HSM. For more information, see [Configure key auto-rotation in Azure Managed HSM](/azure/key-vault/managed-hsm/key-rotation).
396396
>

0 commit comments

Comments
 (0)