Skip to content

Commit 003348e

Browse files
authored
Update backup-restore.md
removing preview headers
1 parent dfe4415 commit 003348e

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
@@ -8,7 +8,7 @@ tags: azure-key-vault
88
ms.service: key-vault
99
ms.subservice: managed-hsm
1010
ms.topic: tutorial
11-
ms.date: 12/11/2023
11+
ms.date: 01/09/2024
1212
ms.author: mbaldwin
1313
# Customer intent: As a developer using Key Vault I want to know the best practices so I can implement them.
1414
---
@@ -36,7 +36,7 @@ There are 2 ways to execute a full backup. You must provide the following inform
3636
3737
[!INCLUDE [cloud-shell-try-it.md](../../../includes/cloud-shell-try-it.md)]
3838

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

4141
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).
4242
2. Create a user assigned managed identity.
@@ -58,7 +58,7 @@ Backup is a long running operation but will immediately return a Job ID. You can
5858

5959
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.
6060

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

106106
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.
107107

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

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

136-
### Selective key restore using user assigned managed identity (preview)
136+
### Selective key restore using user assigned managed identity
137137
```
138138
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
139139
```

0 commit comments

Comments
 (0)