How can we improve Azure API Management?

Allow non-premium tier API managers to have multiple proxy custom domains

We're trying to develop some API's and in order to host them through an API manager and have the endpoints resolve to the proxy domain we have to set up API managers for every single API, unless we use the premium tier. But the premium tier is SO much more expensive than the developer tier it just isn't cost effective to do that.

6 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Drew shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

APIs in Api Management are identified by their name. Let’s say the names of the the two APIs are “api1” and “api2” respectively and the default host name of the API Management instance is “constoso.azure-api.net”. Both APIs would share the same host name and would be addressed as follows:

api1: constoso.azure-api.net/api1
api2: constoso.azure-api.net/api2

Please explain why are you compelled to have individual host names for your APIs?

1 comment

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
  • Paul Laberge commented  ·   ·  Flag as inappropriate

    I'm not sure if this is the same scenario as the original poster, but this is a scenario that we are facing:

    In a PoC, we have a need for external APIs being made available via a domain (say *.thedomain.com) and any internal calls being made from another related domain (say *.internal.thedomain.com). Wecreated the proxy custom domain for the external domain (*.thedomain.com) but now we can't create a proxy custom domain for the internal domain (*.internal.thedomain.com) as the proxy option is no longer available. We haven't tested this on the premium tier of APIM but it isn't exposed as an option for the Developer tier.

    Hope this helps you understand my specific scenario.

Feedback and Knowledge Base