Skip to content

Commit 6cedebe

Browse files
committed
edit
1 parent 7b11f36 commit 6cedebe

File tree

2 files changed

+4
-6
lines changed

2 files changed

+4
-6
lines changed

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

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Instead of relocation, you need to:
2121
- Create a new key vault with the relocation of the associated Azure services.
2222
- Regenerate any required [keys](/azure/key-vault/keys/about-keys), [secrets](/azure/key-vault/secrets/about-secrets), or [certificates](/azure/key-vault/certificates/about-certificates). In some cases, you may need to transfer the secrets or certificates from your existing key vault to the relocated key vault.
2323

24-
![Diagram showing Azure Key vault relocation pattern](./media/key-vault/akv_relocation_pattern.png)
24+
![Diagram showing Azure Key vault relocation pattern](./media/relocation/keyvault/akv-pattern-design.png)
2525

2626
## Prerequisites
2727

@@ -135,8 +135,6 @@ To deploy the template by using Azure portal:
135135

136136
3. Select **Template deployment**.
137137

138-
![Azure Resource Manager templates library](azure-resource-manager-template-library.png)
139-
140138
4. Select **Create**.
141139

142140
5. Select **Build your own template in the editor**.
@@ -351,9 +349,9 @@ Deploy the template to create a new key vault in the target region.
351349
> 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.
352350
353351
1. Follow steps in the described under Redploy.
354-
2. For [secrets](https://learn.microsoft.com/en-us/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.
355-
3. For [certificates](https://learn.microsoft.com/en-us/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.
356-
4. [keys](https://learn.microsoft.com/en-us/azure/key-vault/keys/about-keys) should be regenerate with the relocation of the associated Azure service.
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.
353+
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.
354+
4. [keys](/azure/key-vault/keys/about-keys) should be regenerate with the relocation of the associated Azure service.
357355

358356
## Verify
359357

0 commit comments

Comments
 (0)