API Management

Microsoft Azure API Management is a turnkey solution for publishing APIs to external and internal consumers. Quickly create consistent and modern API gateways for existing backend services hosted anywhere, secure and protect them from abuse and overuse, and gain insights into usage and health. Plus, automate and scale developer onboarding to help get your API program up and running in no time.

How can we improve Azure API Management?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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…)
    1 comment  ·  Pricing  ·  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?

  • Don't see your idea?

API Management

Feedback and Knowledge Base