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.

How can we improve Azure API Management?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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.

    343 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      started  ·  12 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
    • 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 ).

      52 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        under review  ·  8 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
      • 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…

        40 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          under review  ·  3 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
        • 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
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            under review  ·  2 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
          • 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
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              under review  ·  0 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
            • 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.

              7 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                0 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
              • 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
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)
                  You have left! (?) (thinking…)
                  0 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →

                  Thanks for the suggestion. Unfortunately, this is not a trivial change for us and we won’t be able to accommodate this now, but will keep it in the backlog. We understand the desire for having more descriptive and actionable errors and will try to add additional information to error messages.

                • 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…

                  4 votes
                  Vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)
                    You have left! (?) (thinking…)
                    0 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
                  • 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
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)
                      You have left! (?) (thinking…)
                      under review  ·  0 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
                    • 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
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        Signed in as (Sign out)
                        You have left! (?) (thinking…)
                        under review  ·  0 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
                      • 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
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)
                          You have left! (?) (thinking…)
                          0 comments  ·  Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
                        • Don't see your idea?

                        API Management

                        Feedback and Knowledge Base