Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

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. Dapr integration

    Hello,

    The set-backend-service (dapr) policy works fine when invoking a service that sits in the same namespace than the API gateway. In native Dapr, it is possible to invoke a service from another namespace (than the caller) using this convention:

    http://localhost:3500/v1.0/invoke/service.namespace/method/method

    However, the app-id attribute of the APIM policy does not allow to specify "service.namespace". It returns the following error:

    Error in element 'set-backend-service' on line 16, column 10: dapr app id can only contain alphanumeric characters and dashes with no dashes at the beginning or end.

    Would it be possible to take this into account?

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Policies  ·  Flag idea as inappropriate…  ·  Admin →
  2. Expose the code base of inbuilt methods in Azure APIM Policy expression

    I was using the policies on Azure APIM, and was trying to use the Decrypt method which listed as a method to be used(I was using the AES).

    Yet, it was not working as planned, and there is no documentation or sample on how to use the method(except than the method definition online).

    I had to create a Microsoft ticket to be able to debug and know how to use this method properly for decryption.

    A support engineer mentioned that the code base for the methods allowed in APIM are on a Git repod, but those are unfortunately private to…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Policies  ·  Flag idea as inappropriate…  ·  Admin →
  3. Increase Consumption tier, policy document size (currently is limited to 16 KiB)

    We are nearing go live and we hit the base policy document limit. It is very limiting for the consumption tier.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Policies  ·  Flag idea as inappropriate…  ·  Admin →
  4. Be able to ignore backend "host/port" when caching responses.

    It seems that a cache hit will miss if the response previouly stored in the cache was serverd by another backend (host/port combination).

    In fact backend "host/port" seems to be part of the key of the cache.

    Using multiple host and/or ports for the same backend destination is often helpfull (for example when targeting different backends, or if you meet SNAT port exhaustion when all request goes to the same backend ... etc) .

    Currently, the efficiency of the cache is divided by the number backends ("host/port" combinaison) you use.

    An option to cache whatever the backend used (or a…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Policies  ·  Flag idea as inappropriate…  ·  Admin →
1 2 3 4 6 Next →
  • Don't see your idea?

Feedback and Knowledge Base