Azure API Management is an API gateway that can be used for different purposes, for example, to monetize APIs. We also use it for logging and security purposes such as performing authorization.

Our use case for Microsoft Azure API Management is connecting banking systems to Bloomberg Services. We're also using the solution to connect internal services within the banking system, in particular, credit simulation.

It is being used for Oracle databases i.e., API management. We use it on our platform for employee travel bookings and for integrating financial data with our end-user database. It is a seamless bridge between those systems. We've also built a custom TXO dashboard for our CFO and management team.

We use the solution to manage the APIs of the legacy app in on-premises systems at our organization. We use the solution for security purposes. It lets us put restrictions on who can consume the APIs. Also, we can keep a check on the dashboard for requests and the health of the APIs.

One of our applications went live a month ago, and it uses the whole suite of Microsoft APIs.

Since we built our product around APM, our clients use it directly. They find APM to be a simple and straightforward solution that fulfills all their API management needs.

Our clients use APM because it's a SaaS-based solution that comes with Azure Stack-managed services, making it easy for us to use and fulfill all their use cases.

The main use case is if you want to be exposed to an external endpoint. We use it for access. It can only be used by Azure API.

We use Microsoft Azure API Management with our coding.

In general, we use it for the front application, like the mobile banking application or some other service stuff. We found that it's easier to maintain these internet connections and so on, on the cloud.

We are using Microsoft Azure API Management to host APIs.

We're a bank, so one of our primary use cases for API Management is integrating our API with third parties that provide financial policies. Sometimes they want to use our services, like payment and customer inquiry, so we give them access to the API gateway. 

Azure API Management allows you to control who has access to your API gateways and assign permission levels to third parties if you want integration with third-party solutions. That has a couple of advantages. Those third parties can directly access your API directly, and you can set limits. It can also configure authentication on other API managers.

An API gateway is like a platform, and your API provides access to the resources in your environment, so this gateway is an intermediary between you and third parties. It's also the interface between your internal applications. For example, if you have a mobile app and internet banking, they can all be copied in the same API through that gateway. So, that was basically the use cases we have. So, we have almost all the API's behind the gateway.

There's a customer who wanted to migrate their API from their on-prem environment to Azure. They're looking at utilizing Azure API to manage all their other APIs. We just started with migrating one of their APIs. They're still working with it, still trying to learn the difference between what they had for on-prem and Azure. We are in the process of actually migrating a lot of their APIs.

Our company uses the solution for API orchestration and UI management. We currently have 50,000 users. 

We have a couple of use cases for this  product. It's fully cloud-native and can handle telco distribution for end-to-end distribution management. Five or six years ago, we made a  fantastic product with microservices. I was responsible for rolling it out for a large telco in Qatar. They had no distribution or end-to-end visibility or platform. So we helped them to move to a cloud platform for their entire distribution and operation. The beauty of that product is when you look at the telco distribution standpoint your maybe five or ten thousand merchant ecosystem will be connected to that platform. It helps with generating several transactions in a minute or second. And it gives that kind of scalability in the back end. 

The other use case was for banking transactions. If you have your core banking platform that is legacy, if a user wants to bring in a lot of additional alternatives, they need to have some kind of a platform for enhancements. We made a cloud to bring some kind of their operations to the cloud. We made a transaction platform for them so that their merchants could access transactions.

I use API Management for all of our AKS clusters.

There were legacy APIs running on-premises, and we wanted a modernized layer without disturbing the existing legacy layer. Microsoft Azure API management helps with that. We can wrap the modernized API layer. The modernized API layer can perform rate-limiting, monitoring, throttling, aggregating, and other boilerplate functions without disturbing the backend business logic.

I am a software architect. The organization upgraded to API premium in order for us to be able to use virtual networks and security growth. We migrate things from Google Cloud. We use the solution to have an API that is calling internal resources to expose data on the internet. Furthermore, we also use API Management for partners and mobile apps.

We use this product for Epics, Story and Function Management for Products and Accelerator Development, Deployment and Operations Management.

My primary use case is for Logic Apps events as well as for API Management functions provided by Azure. We are implementation partners and I'm a business architect.

I'm in the telecom domain and I have used Microsoft Azure API Management in cost and order management in the order process.

Microsoft Azure API Management is used for making the API calls from our internal application to another available internal application or to the external third-party applications. It can be hosted in the public environment or it can be a client application to which we are making a call and teaching the information. This solution is useful for making the API calls between the application. 

Microsoft Azure API Management is used for platform deployment, hosting, virtual servers, third-party integrations, and the Azure Marketplace.

Microsoft Azure API Management is used for integration across multiple services, API marketplace solutions, and information exchange solutions.

We have been using this solution to protect our APIs and to decouple our APIs between the host versus the outside world. It operates as a gateway pattern in front of the APIs.

It's more of a subscription driven consumption based model, where the APIs are developed to connect backend ERP systems such as SAP and deployed into a library for consumption by both internal and external consumers. The APIs are exposed to the consumers that get onto the API gateway and identify the needed API from the library, use the instructions to subscribe, quickly test and connect to the backend SAP to get the expected information/transaction processed.  Prior to this solution there was an age old EDI interface solution.  This is enabling the customers to be more flexible with their integration architecture and be more agile as it reduces the IT integration dependency and provides a better user experience.

This is part of Techwave application modernization strategy to bring solutions that can bring agility and flexibility to customers and be able to decouple business with huge IT dependent solutions.  This is helping us to help our customers migrate away from the age old EDI technology to the latest API and microservices based architectures.

I work with an enterprise and they needed to manage lots of APIs. They needed to manage information and they use this product to meet their needs.

We primarily use the solution to manage our APIs.

We use the solution for API management.

My primary use case is application monitoring.

We use the solution for API management. 

Microsoft Azure API Management provides customers with customized solutions for various use cases and situations, allowing them to deploy their API strategy and products while also managing and protecting APIs.

It provides solutions for architecting, deploying, and monitoring APIs with other Azure services. 

Users can manage their complete API lifespan using Azure API Management.

The main uses of this solution are sharing data, internal integrations, and combining different backend services into one API proxy. In the latter case, we extract the whole complexity of the integration, and after the work is done, there's a proxy available that can be used and reused by API consumers.

We use this solution because when there is a technical requirement sometimes there are technical constraints that need to be overcome, and that is best resolved through the API component. My organization predominately uses Microsoft solutions and this is why we are using this particular solution.

Our company has some internal APIs and we use Microsoft Azure API Management to help keep everyone on the same page.

We are in the healthcare industry, so all the applications which are related to one hospital, it binds to Microsoft Azure API Management, and this is our use case for it.

We use Microsoft Azure API Management for integration. We use it for managing, monitoring, and integrating with other systems, for example, for asset management and monitoring tools. If we want to integrate or enable monitoring and management, we use Microsoft Azure API Management.

I mainly use Azure APIM for access management.

My primary use case is as part of a multi-channel strategy wherein APIMs are being used with micro-products or third-party clients. Our web application firewall receives all the external and public traffic, and it re-routes to the APIM, which is on the private subnet. The APIM manages both in authentication and authorization service composition layer.

They're doing integration work between a lot of different on-premises business platforms, like Salesforce and NetSuite. We're doing integration work, but we're putting all of our APIs into the Azure cloud and using that API manager at this time.

We use it to manage the API. We have a backend API with service in the backend. We use API Management in the front to manage the vendors. They can do their own testing. It's quicker for us to put in the specifications so we can knock off the responses. We build the specs and then get an external developer to start the development without the web service being ready. 

We also use it for the security and for the clock in features.

We are a software firm and this is one of the solutions that we provide for our customers.

We use the cloud model. Our primary use case is for integration between different systems. There are many use cases for the API management tool, but the most common scenario is integration between different systems.

We use this solution to integrate with a third party with API integration.

We have company-wide APIs which are hosted in Niger, and some of the external clients access the applications via the API, and we provide the post-data information. The clients get their data from our larger API.

The tool helps to manage APIs. 

We primarily use the solution for storage. It’s for a database backup.

I am using Microsoft Azure API Management to connect external systems.

We are publishing microservices using API management. We have created various packages and policies that we are applying over there. We have also created a portal for developers so that they can see what we are doing.

We use Microsoft Azure API Management with a custom software solution.

We have two approaches to how we use the solution. We own the managed services and the other we have customers take the subscription and we manage it. 

We use the product for managing APIs - for internal as well as for external communication.

Furthermore we enable transparency, governance and re-use.  

Our primary use case is for managing internal APIs, for ordering process APIs and in general process APIs, and resource manipulation APIs. We need an API management to get a better overview, and this is one use case with analytics parts. Another use case is security, being able to rotate API keys and to manage access at a signature point. Finally, we also have the developer portals with the self-service capabilities so that developers can request access to APIs through a developer portal and manage their own keys.

We are still in the ramp-up phase, so currently we have actively two or three guys using it. We're planning to increase usage. We're in partnership with Microsoft and I'm an enterprise architect. 

Our primary use case is to provide API mapping for our clients. We're a customer of Azure and I'm a system analyst.