Skip to content

Commit 77dc07f

Browse files
committed
edit
1 parent 6cedebe commit 77dc07f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/operational-excellence/relocation-key-vault.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -349,7 +349,7 @@ Deploy the template to create a new key vault in the target region.
349349
> Note: In case of moving an Azure Key Vault across regions but within same geography, a backup and restore option for secrets, keys and certificates is recommended. Ref – Backup and Restore Option. The creation of the Key Vault instance and the mapping to target dependent resources still remains the same as per the previous approach.
350350
351351
1. Follow steps in the described under Redploy.
352-
2. For [secrets](azure/key-vault/secrets/about-secrets) read the value in the source key vault and recreate the secret in the target key vault and set the value.
352+
2. For [secrets](/azure/key-vault/secrets/about-secrets) read the value in the source key vault and recreate the secret in the target key vault and set the value.
353353
3. For [certificates](/azure/key-vault/certificates/about-certificates) export the certificate into a PFX file and import the PFX file into the target key vault. In case you cannot export the private key (exportable is not set) you have to generate certificate a new certificate and import it into the target key vault.
354354
4. [keys](/azure/key-vault/keys/about-keys) should be regenerate with the relocation of the associated Azure service.
355355

0 commit comments

Comments
 (0)