Skip to content

Commit 21718e8

Browse files
authored
Update backup-restore.md
1 parent f4a4238 commit 21718e8

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -45,11 +45,11 @@ There are 2 ways to execute a full backup. You must provide the following inform
4545
5. Provide ‘storage blob data contributor’ role access to the user assigned managed identity created in step#2. Do this by going to the “Access Control” tab on the portal -> Add Role Assignment. Then select “managed identity” and select the managed identity created in step#2 -> Review + Assign
4646
6. Create the Managed HSM and associate the managed identity with below command.
4747
```azurecli-interactive
48-
az keyvault create --hsm-name mhsmdemo2 –g mhsmrgname –l mhsmlocation -- retention-days 7 --administrators "initialadmin" --mi-user-assigned "/subscriptions/subid/resourcegroups/mhsmrgname/providers/Microsoft.ManagedIdentity/userAssignedIdentities/userassignedidentitynamefromstep2"
48+
az keyvault create --hsm-name mhsmdemo2 –l mhsmlocation -- retention-days 7 --administrators "initialadmin" --mi-user-assigned "/subscriptions/subid/resourcegroups/mhsmrgname/providers/Microsoft.ManagedIdentity/userAssignedIdentities/userassignedidentitynamefromstep2"
4949
```
5050
If you have an existing Managed HSM, associate the managed identity by updating the MHSM with the below command.
5151
```azurecli-interactive
52-
az keyvault update-hsm --hsm-name mhsmdemo2 –g mhsmrgname --mi-user-assigned "/subscriptions/subid/resourcegroups/mhsmrgname/providers/Microsoft.ManagedIdentity/userAssignedIdentities/userassignedidentitynamefromstep2"
52+
az keyvault update-hsm --hsm-name mhsmdemo2 --mi-user-assigned "/subscriptions/subid/resourcegroups/mhsmrgname/providers/Microsoft.ManagedIdentity/userAssignedIdentities/userassignedidentitynamefromstep2"
5353
```
5454

5555
## Full backup
@@ -60,7 +60,7 @@ While the backup is in progress, the HSM might not operate at full throughput as
6060

6161
### Backup HSM using user assigned managed identity (preview)
6262
```azurecli-interactive
63-
az keyvault backup start --use-managed-identity true --hsm-name mhsmdemo2 -- storage-account-name mhsmdemobackup --blob-container-name mhsmdemobackupcontainer
63+
az keyvault backup start --use-managed-identity true --hsm-name mhsmdemo2 --storage-account-name mhsmdemobackup --blob-container-name mhsmdemobackupcontainer
6464
```
6565
### Backup HSM using SAS token
6666

@@ -107,7 +107,7 @@ Restore is a long running operation but will immediately return a Job ID. You ca
107107

108108
### Restore HSM using user assigned managed identity (preview)
109109
```azurecli-interactive
110-
az keyvault restore start --hsm-name mhsmdemo2 --storage-account-name mhsmdemobackup--blob-container-name mhsmdemobackupcontainer --backup-folder mhsm-backup-foldername --use-managed-identity true
110+
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
```
112112
### Restore HSM using SAS token
113113

0 commit comments

Comments
 (0)