Skip to content

Commit 51fd020

Browse files
committed
update
1 parent 8b59615 commit 51fd020

2 files changed

Lines changed: 1 addition & 5 deletions

File tree

articles/cloud-hsm/authentication.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Authentication is a crucial aspect of securely accessing and operating within Az
1515

1616
## Cloud HSM CLI authentication
1717

18-
You can authenticate by using CLI tools like `azcloudhsm_util` in either interactive mode or single-command mode. In interactive mode, use the `loginHSM` command. For single-command mode, include `singlecmd` and parameters for `loginHSM`. We advise you to securely store your HSM credentials when your application isn't using them.
18+
You can authenticate by using CLI tools like `azcloudhsm_util` in either interactive mode or single-command mode. In interactive mode, use the `login` command. For single-command mode, include `singlecmd` and parameters for `loginHSM`. We advise you to securely store your HSM credentials when your application isn't using them.
1919

2020
### Interactive mode
2121

articles/key-vault/keys/how-to-configure-key-rotation.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,6 @@ ms.author: mbaldwin
1515
# Configure cryptographic key auto-rotation in Azure Key Vault
1616

1717
## Overview
18-
1918
Automated cryptographic key rotation in [Key Vault](../general/overview.md) allows users to configure Key Vault to automatically generate a new key version at a specified frequency. To configure rotation you can use key rotation policy, which can be defined on each individual key.
2019

2120
Our recommendation is to rotate encryption keys at least every two years to meet cryptographic best practices.
@@ -25,9 +24,6 @@ For more information about how objects in Key Vault are versioned, see [Key Vaul
2524
## Integration with Azure services
2625
This feature enables end-to-end zero-touch rotation for encryption at rest for Azure services with customer-managed key (CMK) stored in Azure Key Vault. Please refer to specific Azure service documentation to see if the service covers end-to-end rotation.
2726

28-
> [!NOTE]
29-
> When rotating customer-managed keys used by Azure services, the time required for each service to detect and apply the new key version varies (from one hour to 24 hours or more). Consult the specific Azure service documentation for guidance on when you can safely disable the old key version after rotation.
30-
3127
For more information about data encryption in Azure, see:
3228
- [Azure Encryption at Rest](/azure/security/fundamentals/encryption-atrest#azure-encryption-at-rest-components)
3329
- [Azure services data encryption support table](/azure/security/fundamentals/encryption-models#supporting-services)

0 commit comments

Comments
 (0)