Skip to content

Commit 4e19fc4

Browse files
Merge pull request #262787 from chen-karen/main
Update backup-restore.md
2 parents 7497334 + 003348e commit 4e19fc4

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/key-vault/managed-hsm/backup-restore.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.custom: devx-track-azurecli
99
ms.service: key-vault
1010
ms.subservice: managed-hsm
1111
ms.topic: tutorial
12-
ms.date: 12/11/2023
12+
ms.date: 01/09/2024
1313
ms.author: mbaldwin
1414
# Customer intent: As a developer using Key Vault I want to know the best practices so I can implement them.
1515
---
@@ -37,7 +37,7 @@ There are 2 ways to execute a full backup. You must provide the following inform
3737
3838
[!INCLUDE [cloud-shell-try-it.md](../../../includes/cloud-shell-try-it.md)]
3939

40-
#### Prerequisites if backing up and restoring using user assigned managed identity (preview):
40+
#### Prerequisites if backing up and restoring using user assigned managed identity:
4141

4242
1. Ensure you have the Azure CLI version 2.54.0 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install the Azure CLI](/cli/azure/install-azure-cli).
4343
2. Create a user assigned managed identity.
@@ -59,7 +59,7 @@ Backup is a long running operation but will immediately return a Job ID. You can
5959

6060
While the backup is in progress, the HSM might not operate at full throughput as some HSM partitions will be busy performing the backup operation.
6161

62-
### Backup HSM using user assigned managed identity (preview)
62+
### Backup HSM using user assigned managed identity
6363
```azurecli-interactive
6464
az keyvault backup start --use-managed-identity true --hsm-name mhsmdemo2 --storage-account-name mhsmdemobackup --blob-container-name mhsmdemobackupcontainer
6565
```
@@ -106,7 +106,7 @@ There are 2 ways to execute a full restore. You must provide the following infor
106106

107107
Restore is a long running operation but will immediately return a Job ID. You can check the status of the restore process using this Job ID. When the restore process is in progress, the HSM enters a restore mode and all data plane command (except check restore status) are disabled.
108108

109-
### Restore HSM using user assigned managed identity (preview)
109+
### Restore HSM using user assigned managed identity
110110
```azurecli-interactive
111111
az keyvault restore start --hsm-name mhsmdemo2 --storage-account-name mhsmdemobackup --blob-container-name mhsmdemobackupcontainer --backup-folder mhsm-backup-foldername --use-managed-identity true
112112
```
@@ -134,7 +134,7 @@ az keyvault restore start --hsm-name mhsmdemo2 --storage-account-name mhsmdemoba
134134

135135
Selective key restore allows you to restore one individual key with all its key versions from a previous backup to an HSM.
136136

137-
### Selective key restore using user assigned managed identity (preview)
137+
### Selective key restore using user assigned managed identity
138138
```
139139
az keyvault restore start --hsm-name mhsmdemo2 --storage-account-name mhsmdemobackup --blob-container-name mhsmdemobackupcontainer --backup-folder mhsm-backup-foldername --use-managed-identity true --key-name rsa-key2
140140
```

0 commit comments

Comments
 (0)