API Management service instance to multiple Azure regions

Question

API Management service instance to multiple Azure regions

Gaurav Pandey 56

As per the below screenshot only the gateway component of API Management is deployed to all regions, and service management component and developer portal won't be available in secondary region due to which access to the developer, management portal and ability to change configuration (e.g. adding APIs, applying policies) will not be available until the Primary region comes back online.
So, what's the possibility to get developer and management portal in secondary region when Primary region goes offline? Just want to understand is it possible to deploy developer and management portal in secondary region quickly (or how much time it will take) when primary region is impacted and secondary region becomes active.

Reference Post: https://learn.microsoft.com/en-us/answers/questions/602508/apim-dr-setup-using-multi-region-deployment-vs-bac.html

1 answer

Your answer

Answer 1

MayankBargali-MSFT 70,896

@Gaurav Pandey If the primary region has an issue then unfortunately you will not able to access the developer portal and change the configuration as mentioned in the document.
There is no way to deploy the developer portal/configuration operation to the secondary region. You need to wait till the issue is resolved to access the developer portal/configuration operation as only API services handling the request are only available to the secondary regions.

Gaurav Pandey 56 Reputation points

2021-11-08T02:22:52.207+00:00

Thanks @MayankBargali-MSFT for clarifying, so access to the developer portal and ability to change configuration (e.g. adding APIs, applying policies) will be impaired until the Primary region comes back online.
Then, will i be able to update the connection string of backend service of secondary region when primary region goes offline.
MayankBargali-MSFT 70,896 Reputation points

2021-11-09T06:57:32.51+00:00

@Gaurav Pandey As you cannot change the API, add API, update API, etc operation so that means you will not able to update the backend API as it is the update API operation. You can use ATM (Azure Traffic Manager) as the backend URL and configure ATM with different endpoints (multiple backend URLs) so you can failover/change from primary to the secondary endpoint using ATM and there will be no configuration update at APIM end.

Share via

API Management service instance to multiple Azure regions

1 answer

Your answer