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. Self-hosted API Management gateway

    To expand support for hybrid use cases and enable more efficient on-premises-to-on-premises call patterns for internal-only and internal/external APIs, we will provide an option for customers to self-host a containerized version of the API Management gateway component (fully equivalent to the gateway in the cloud, not a “micro-gateway”) on-premises or other environment e.g. other public clouds. Self-hosted gateway will require and will be managed from a cloud-based Azure API Management instance.

    838 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  25 comments  ·  Gateway  ·  Flag idea as inappropriate…  ·  Admin →
  2. New API Management developer portal

    We are working on a new, open-source developer portal offering in Azure API Management, based on our own fork of the Paperbits framework (paperbits.io). It has a modern default look and feel, and is optimized for:

    - Customization, styling, and authoring through a built-in visual editor

    - Programmatic access through APIs for automating development, management, and deployment

    - Extension of the provided core functionality

    371 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  42 comments  ·  Developer portal  ·  Flag idea as inappropriate…  ·  Admin →
  3. More flexible subscriptions in Azure API Management

    Present model for providing access to APIs is based on product subscriptions owned by a user. Each subscription includes a few properties and a pair of API keys. We are working on expanding this model to allow subscriptions and keys to be owned by a group of users or not be associated with any users at all. This will allow customers the flexibility of creating an ad-hoc set of key or having keys shared by a team of users without worrying about their ownership when members leave or are added to the team.

    165 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  15 comments  ·  API management experience  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support Swagger Documentation - Object representation with nested $ref issue

    Hi,

    There is an issue regarding Swagger file for complex objects which are using nested $ref, according to the program team, it's not supported yet by API Management although it works well in Swagger UI.

    This is for me a big issue as we can't manage documentation manually in case our object definition evolve. Furthermore, even if we put manually a json object example in APIM Publisher portal, we can't define the object model associated to it.

    Could you please make Swagger documentation work with nested $ref in APIM?

    Thanks.

    90 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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…

    87 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  Pricing  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support better grouping & sorting of products & APIs

    Right now - everything is forced into alphabetical sorting. There are no grouping options. We plan to use this for our entire enterprise, and we expect to end up with hundreds of APIs and dozens of products. A simple "sort order" field will accomplish the sorting issues, may be cumbersome to maintain but we could manage. Not sure how grouping would work, but here is our example:

    Products:
    Business Unit A - Developer
    Business Unit A - Test
    Business Unit A - Production
    Business Unit A - Production Unlimited

    I may like to have a "bucket" named just "Business Unit…

    39 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Developer portal  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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  ·  1 comment  ·  Pricing  ·  Flag idea as inappropriate…  ·  Admin →
  8. RM or AZ powershell support for uploading a 3.0 open api specification to Azure api management

    I would like to see the option to add a 3.0 open api specification via a powershell cmd. The cmds, as of now, do not support 3.0 format.

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

Feedback and Knowledge Base