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. Basic Tier

    The gap between "Developer" and "Standard" is huge.
    Developer: 32K calls/day
    Standard: 6600K calls/day (206 times what developer gives!)

    This isn't flexible at all. Of course 90% of everyone will fall between these two options and therefore will have to buy the expensive one, meaning in practice that 90% of everyone won't use the service at all and just roll their own.

    What about a Basic Tier?
    1000K calls/day
    210$/month

    658 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    33 comments  ·  Pricing  ·  Flag idea as inappropriate…  ·  Admin →
  2. 494 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    24 comments  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  3. OpenAPI v3 support in Azure API Management

    The OpenAPI Specification [https://github.com/OAI/OpenAPI-Specification] (formerly known as Swagger) defines a standard, programming language-agnostic interface description for REST APIs. Azure API Management currently supports OpenAPI versions 1.2 and 2.0. We are in the process of adding support for the recently released version 3 of the specification in both JSON and YAML formats. Our work is based on the OpenAPI.NET SDK [https://github.com/Microsoft/OpenAPI.NET] open source project.

    483 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    28 comments  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  4. API DevOps with Azure API Management

    Customers commonly use separate Azure API Management service instances for various environments, e.g., production, staging, QA. These environments are usually shared by multiple development teams, each responsible for a subset of APIs. We are working on a set of guidance, samples, and open source tools that will enable customers to automate API deployment to shared environments by multiple teams without interfering with each other.

    436 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
  5. Mutual certificate authentication for front-end / public endpoint

    Authenticate calls to developer-facing endpoint using mutual certs. Provide a policy for it and/or access to certificate from within policy expressions Context.

    431 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  3 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  6. Integration with Web API

    Today, when creating a new API there is the Help area in the solution that provides a light documentation of the API. Please add a simple way to export this to API Management.

    285 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  8 comments  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  7. Handle versioning

    A cloning option for the full api could be helpful for this.

    231 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
  8. Better documentation options

    When adding descriptions to operations or request & responses all formatting is ignored, even line breaks. Makes it difficult to provide any sort of useful documentation for people to read. Should support markdown or html at least.

    188 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Developer portal  ·  Flag idea as inappropriate…  ·  Admin →
  9. 177 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  17 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Plan should be charged on usage not reserved instances

    We was planning to create an API for our system and learning about Azure API Management, We liked the product, the only obstacle to decide if we'll use it or a VirtualMachine or WebRole was the price.
    it's too much expensive for startups.

    Today I received an anouncement from Amazon API Gateway and their plans are very attractive, they charge based on api usage not over reserved capacity. I think you should review your pricing policies to attract more customers.

    The cloud appeal is the 'pay as you go', and your plans are a big limitation for most startups.

    174 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Pricing  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow granting Administrator access without giving full admin rights to all of the Azure Subscription

    Right now the only people who can edit/create APIs have to be full administrators on the entire Azure Subscription. I need to be able to delegate administrator privileges on the api-portal without giving them the keys to the whole castle.

    153 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  12. Application Insights Integration

    Add the ability to log to Visual Studio Application Insights using the Logger entity and a log-to-applicationinsights policy. This would enable developers to get an all up dashboard view of their API Management analytics and their API analytics currently being captured today via App Insights. This dashboard view can be created today by using the log-to-eventhub policy and Stream Analytics to expose the data to PowerBI. However, logging directly to App Insights would make this a more streamlined process for developers.

    141 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  13. API Key Request Support

    A developer that wants to consume your api or service should have the ability to request a set of keys and the api owner should be allowed to grant access or deny the request. If approved by the api owner, a developer would receive a set of keys to access your api. This should be allowed in the API Management Portal of the API Developer. I think it's great that you already support these types of requests in ACS however the Management Console does not support this workflow.

    137 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Treat Headers like Parameters when defining API Operations

    Headers are not first class citizens when modeling API operations. There is no clear place to enter or describe them. The resulting header documentation on the Dev portal is poor.
    How about treating headers like you do with query string parameters, so users can add as many as required and they are pre-populated with default values when using the API test utility?

    123 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  15. Multi-region support

    Currently the API management is bound to a specific region. An application that is geo-distributed and uses traffic manager has to be constrained to a specific region...or provide the developer/customer multiple screen interfaces. The desire is to gain the advances of the api management without loosing the advances of traffic manager.

    115 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add "API Management proxy" to an Azure Virtual Network

    In this way we can reach cloud services, VMs and on-premises resources (using site-to-site VPN) without opening Internet faced end-points.

    113 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Pass developer identity/email who call certain operation, from API management to Backend for Authorization purpose.

    Please highly consider George's simple idea of adding an X-Api-Consumer-Identity: {foo} header to establish chain of trust between developer who call API management's operation and backend.

    social.msdn.microsoft.com/Forums/windowsazure/en-US/6ac9aa49-fa8f-4cb1-8594-12124622ccb6/user-authorization-?forum=azureapimgmt

    113 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. 108 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  19. Use external cache with Azure API Management

    Response caching is an effective way of reducing request latency and reducing backend load. We are working on enabling customers to use external Redis-compatible cache, e.g., Azure Redis Cache [https://azure.microsoft.com/en-us/services/cache/]. As a result, customers will get full control over the size and content of the cache. They will be able to scale cache independently from their Azure API Management instances, share it across multiple API Management instances as well as pre-load and evict cached data as needed.

    93 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Policies  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow to bind an APIM instance with multiple domain names.

    One might bind an APIM instance with a.com at the beginning and has it published to customers. Then decided to switch to b.com, but he don't want to add breaking changes to his existing customers and thus wants to keep both a.com and b.com binding to that APIM instance at the same time.

    82 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 6 7 8
  • Don't see your idea?

Feedback and Knowledge Base