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. Automated backup for APIM

    Provide automated and manual backup feature something similar to what we have in Azure Web Apps (
    https://docs.microsoft.com/en-us/azure/app-service/web-sites-backup#configure-automated-backups ).

    77 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  9 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
  2. Multiple Environment per Instance

    If you want your users to see the documentation in production, but "Try It" in your staging environment we'd have to deploy a separate APIM instance and manage content in both.

    Below is a brain dump of how I imagine this feature could be used in various aspects of the APIM solution.

    apiminstance.azure-api.net < this would be the primary
    environment.apiminstance.azure-api.net < this would be the environment specific or a custom domain per environment

    There would be no environment.apiminstance.portal.azure-api.net site

    Also if we could set the default environment to use for the Try It button that'd be fantastic.

    Each environment should…

    58 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support API definition updates as part of Visual Studio builds

    For applications developed in Visual Studio and leveraging Swashbuckle, can we get the ability to update the API definitions in APIm on each build and deploy (CI) rather than having to hand-update APIm each time.

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
  4. Publish widgets through a REST API

    Can you provide the ability to publish widgets through a Rest API? It's annoying you can't style or change the format without doing it manually.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
  5. Configure custom git repository

    At this moment, each API management instance offers a git repository which can be used to make changes to the instance. In DevOps scenarios where one team has multiple instances (dev, staging, prod) you want these changes to follow the product lifecyle along with other changes. For example: a certain release includes a new back-end API which you also want to include into APIM. You'd want the entire package to move from development into staging in one single release.

    Imho the perfect way to fix this is to hook-up each APIM release to a centralized github repo, and have it…

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
  6. PowerShell Support to Create/Import an API from a Logic App

    Currently there is no PowerShell Automation Support to Create / Import a Logic App similar to functionality for deploying an App Service API App.

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add file name to deployment error.

    When I edited my git repo locally and then pushed it back to the server there was a typo error in my code, opps... The error message was as follows and it tells me what was wrong, even what line number the error was on, but it does not tell me what policy file the error occurred in. Would be nice if you told me what file the error is in.

    Deployment operation failed due to invalid data: One or more fields contain incorrect values: Error in element 'send-request' on line 10, column 4: ; expected.

    Thanks

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
  8. Subscriptions with an expiration timespan

    Allow subscriptions to have a lifetime, and specify an expiration date. We are looking into monetization of our API's and one of the issues we are facing is that we would like to revoke access to an API based on the billing model (e.g. 3 month license).

    To minimize the custom implementation for monetization, we would like to be able to specify an expiration date.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add Support for Properties in the OAuth Servers

    Add support for Properties (e.g. {{TokenEndpoint}}) for the OAuth server endpoints.

    Currently, the UI and the actual server do not function when you update (via REST API) the OAuth server to have a tokenEndpoint = '{{TokenEndpoint}}' as the value. The REST API accepts the value but then the actual server cannot acquire a token.

    This is needed to support clone/merge/pull promotion of the config from one environment to another, e.g. from dev instance to prod instance.

    Currently the only option is to exclude that file during merge as they must have unique environment values.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow API Management to respond during backend upgrades

    Create a new management API endpoint that allows an API to be marked with the states as "being upgraded" and "in production". When an API is marked as "being upgraded" it should return a 503 status with a retry-after header instead of passing the request through.

    This would allow client applications that know how to do retries be uninterrupted by backend upgrades.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
  11. staging

    Hi,

    Would it be possible to add a staging feature to APIM? Right now it is very hard to validate configuration changes in Production. Even if you have a PPE/TEST separate environment, the configurations won't be the same.

    Deploying to production without testing is too risky.

    Would it be possible to add a staging feature, where configurations can be tested in production and if after flight configurations seem validated, then changes can be published from staging to production

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

Feedback and Knowledge Base