Skip to content

Commit dfa123a

Browse files
committed
x-links
1 parent 1348455 commit dfa123a

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/api-management/api-management-howto-migrate.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.topic: how-to
99
ms.date: 08/20/2021
1010
ms.author: danlep
1111
ms.custom: subject-moving-resources
12-
#cusomerintent: As an Azure service administrator, I want to move my service resources to another Azure region.
12+
#customerintent: As an Azure service administrator, I want to move my service resources to another Azure region.
1313
---
1414

1515
# How to move Azure API Management across regions
@@ -43,19 +43,19 @@ To move API Management instances from one Azure region to another, use the servi
4343
### Option 1: Use a different API Management instance name
4444

4545
1. In the target region, create a new API Management instance with the same pricing tier as the source API Management instance. Use a different name for the new instance.
46-
1. [Back up](api-management-howto-disaster-recovery-backup-restore.md#-back-up-an-api-management-service) the existing API Management instance to the storage account.
47-
1. [Restore](api-management-howto-disaster-recovery-backup-restore.md#-restore-an-api-management-service) the source instance's backup to the new API Management instance.
46+
1. [Back up](api-management-howto-disaster-recovery-backup-restore.md#back-up-an-api-management-service) the existing API Management instance to the storage account.
47+
1. [Restore](api-management-howto-disaster-recovery-backup-restore.md#restore-an-api-management-service) the source instance's backup to the new API Management instance.
4848
1. If you have a custom domain pointing to the source region API Management instance, update the custom domain CNAME to point to the new API Management instance.
4949

5050
### Option 2: Use the same API Management instance name
5151

5252
> [!WARNING]
5353
> This option deletes the original API Management instance and results in downtime during the migration. Ensure that you have a valid backup before deleting the source instance.
5454
55-
1. [Back up](api-management-howto-disaster-recovery-backup-restore.md#-back-up-an-api-management-service) the existing API Management instance to the storage account.
55+
1. [Back up](api-management-howto-disaster-recovery-backup-restore.md#back-up-an-api-management-service) the existing API Management instance to the storage account.
5656
1. Delete the API Management instance in the source region.
5757
1. Create a new API Management instance in the target region with the same name as the one in the source region.
58-
1. [Restore](api-management-howto-disaster-recovery-backup-restore.md#-restore-an-api-management-service) the source instance's backup to the new API Management instance in the target region.
58+
1. [Restore](api-management-howto-disaster-recovery-backup-restore.md#restore-an-api-management-service) the source instance's backup to the new API Management instance in the target region.
5959

6060
## Verify
6161

0 commit comments

Comments
 (0)