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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. VPN/ExpressRoute support in Standard Tier

    If you must charge more for VPN make it a paid for add-on for Standard tier.

    Using the standard tier is already tough to justify for our low volume business case. Unfortunately the backend servers are in a private network so we need the ExpressRoute functionality.

    API Management was justified based on it also being the authentication gateway and firewall between the Internet and our internal APIs. The business case doesn't work if we still need to manage Internet facing reverse proxy servers or pay for Premium.

    344 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  15 comments  ·  Pricing  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support VNET for Basic Tier of APIM

    Our APIs are deployed to Service Fabric cluster in a VNET. If we want to expose our APIs through APIM, we have to use the Premium Tier of APIM since that's the only tier where VNET support is included.

    Premium Tier of APIM has bunch of other features like AD authentication, Multi-region support, 4000 reqs/sec etc., which we don't need and don't care.

    Why are all those features clubbed together and provided as an all or nothing solution?

    Basic Tier fits our use case perfectly, if only we can deploy it in a VNET.

    Service Fabric integration with APIM is…

    341 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  25 comments  ·  Pricing  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow multi-region deployment at Standard Tier

    Standard Tier currently does not allow for multi-region deployment. Premium transaction levels are so much higher and more costly, when there may only be need for a very small deployment in some geos, but need to be co-located with services already deployed to those geos. Allow for more flexibility in the deployment model, so a user can tune what they need in each different Geo (Premium in US, Standard in EU, Basic/Dev in AU).

    121 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  5 comments  ·  Pricing  ·  Flag idea as inappropriate…  ·  Admin →
  4. Better pricing structure for API Management

    We currently use 4 instances of APIM for duplicating our environments (Dev/UAT/Pre Prod and Production)

    We went with APIM as a solution for fronting some azure services and some internal services. Due to the VPN access only being available on Premium we are paying for over 32 Millions calls a day when we will barely generate a 1 Million. So we have 4 Premium APIM instances costing us £6000 a month purely for the VPN access. Forcing us to pay for a level we do not require just for a feature of the environment, it would be better if the…

    90 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Pricing  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow disabling/stopping of API Management during evaluation to preserve subscription credits

    I am evaluating API Management using Visual Studio Subscription credits. The credits are depleted even when I am not testing API Management and are likely to be exhausted before I have completed evaluation. This is both frustrating and prevents me from completing my evaluation. Other API Management providers such as apigee provide a superior evaluation experience.

    This issue has already been raised before and the answer is not satisfactory
    https://social.msdn.microsoft.com/Forums/en-US/f4522315-fd3b-4129-b758-e74b22d74145/how-can-i-quotdisablequot-but-not-delete-an-api-management-service?forum=azureapimgmt

    69 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Pricing  ·  Flag idea as inappropriate…  ·  Admin →
  6. AAD integration for all Teirs

    Just because we want a good API interface does not mean we are doing the next Facebook. APIM at Standard level would be, by far, the most expensive component of my entire end to end IoT data platform and includes far more bandwidth than I will likely require. But now you expect me to pay over 4 times as much just to integrate AD for a handful of users?

    I will either keep to Developer tier or if that is not sufficient the internal developers can use personal Microsoft accounts. On the bright side, it does eliminate a tie in…

    47 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  5 comments  ·  Pricing  ·  Flag idea as inappropriate…  ·  Admin →
  7. Provide more attractive pricing

    The premium tier is 4 times more expensive than the Standard tier. It provides Enterprise Features like VNET integration. I think that in order to increase the solution adoption, the price should be reviewed, or provide a more cost effective pricing. Many customers were thinking using APIM for their internal projects but the pricing is just huge

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Pricing  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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.

    9 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?

  9. Consumption tier of Azure API Management

    You can now choose the new Consumption tier (in select regions) when you are creating a new API Management instance. Consumption tier, a variant of API Management designed and implemented around serverless principles is a more organic fit for applications built using serverless technologies. See https://aka.ms/apimconsumptionblog for detailed information about this new tier, it's features and limits.

    For the general availability release we plan to add the following capabilities:

    - Custom hostnames
    - Client certificate authentication
    - Azure Monitor metrics
    - Automated upgrade to other tiers
    - .NET SDK and PowerShell support
    - Faster activation
    - Additional public regions

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  2 comments  ·  Pricing  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base