Skip to content

Commit 8dff9cc

Browse files
authored
Update backup-restore.md
1 parent f4a7e23 commit 8dff9cc

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Only following built-in roles have permission to perform full backup:
2525
- Managed HSM Administrator
2626
- Managed HSM Backup
2727

28-
There are 2 ways to execute a full backup:
28+
There are 2 ways to execute a full backup/restore:
2929
1. Assigning an User-Assigned Managed Identity (UAMI) to the Managed HSM service. You can backup and restore your MHSM using a user assigned managed identity regardless of whether your storage account has public network access or private network access enabled. If storage account is behind a private endpoint, the UAMI method works with trusted service bypass to allow for backup and restore.
3030
2. Using storage container SAS token with permissions 'crdw'. Backing up and restoring using storage container SAS token requires your storage account to have public network access enabled.
3131

0 commit comments

Comments
 (0)