You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/key-vault/managed-hsm/disaster-recovery-guide.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,7 +83,7 @@ For this step you'll need:
83
83
84
84
The `az keyvault security-domain restore-blob` command performs following operations:
85
85
- Decrypt the source HSM's Security Domain with the private keys you supply.
86
-
- Create a Security Domain Upload blob encrypted with the Security Domain Excahnge Key we downloaded in the previous step
86
+
- Create a Security Domain Upload blob encrypted with the Security Domain Exchange Key we downloaded in the previous step
87
87
88
88
This step can be performed offline.
89
89
@@ -95,7 +95,7 @@ az keyvault security-domain restore-blob --sd-exchange-key ContosoMHSM2-SDE.cer
95
95
96
96
## Upload Security Domain Upload blob to destination HSM
97
97
98
-
We now use the Security Domain Upload blob created in the previous step and upload it ot the destination HSM to complete the security domain recovery. The `--restore-blob` flag is used to prevent exposing keys in an online environment.
98
+
We now use the Security Domain Upload blob created in the previous step and upload it to the destination HSM to complete the security domain recovery. The `--restore-blob` flag is used to prevent exposing keys in an online environment.
99
99
100
100
```azurecli-interactive
101
101
az keyvault security-domain upload --hsm-name ContosoMHSM2 --sd-file restore_blob.json --restore-blob
0 commit comments