Microsoft Azure API Management Reviews

My major use case for Microsoft Azure API Management is for integration purposes. Microsoft Azure API Management enables us to get the data seamlessly, conduct analysis, and perform business application integration.

We use the existing services hosted in Microsoft Azure API Management without making any changes.

For transformation capabilities, we utilize ADF, Data Factory instead of Microsoft Azure API Management.

Regarding security features in Microsoft Azure API Management, we utilize token bearer authentication.

As retailers with integration to our channel partners, we haven't experienced any security issues with Microsoft Azure API Management since it isn't exposed to external parties.

We use a basic Azure function hosted in Microsoft Azure API Management rather than the integrated developer portal.

Tracking analytics and performance analytics in Microsoft Azure API Management is straightforward. We use basic features for performance analytics and log analytics due to additional subscription charges. We enabled log analytics for Microsoft Azure API Management in the past month to investigate issues such as unreachable endpoints or request timeouts.

We are not implementing any automated API creation in Microsoft Azure API Management.

I have been using Microsoft Azure API Management for more than three years.

Microsoft Azure API Management is generally stable. We only face problems during system-wide outages.

Microsoft Azure API Management is easy to scale, though the cost increases significantly with scaling.

When support is needed for Microsoft Azure API Management, we contact our CSP partner who raises a ticket with Microsoft. Support responses typically arrive within one to two hours via call and email.

Neutral

I worked with various API management tools about six or seven years ago, including developing custom APIs in Linux and JBoss. Microsoft Azure API Management as a complete package contains all the features that meet our requirements.

The implementation of Microsoft Azure API Management is straightforward.

All Microsoft Azure API Management implementation is handled through a Microsoft partner.

We haven't compared Microsoft Azure API Management with other products since we exclusively use Microsoft products.

I don't see any disadvantages in Microsoft Azure API Management for our environment.

We are implementing Dynamics 365, and through our CSP partner agreement, we have direct communication with Microsoft.

I rate Microsoft Azure API Management an eight out of ten because upgrading resources is very costly for us. Otherwise, it would receive a nine.

I use Microsoft Azure API Management (APIM). Ask me questions about Microsoft Azure API Management to know my opinion.

The functionality in Microsoft Azure API Management that I find most valuable is enabling headers, which allows me to troubleshoot issues that occur on the customer side. When something happens on the customer side, certain headers are visible in the APIM logs but not in the corresponding Application Insights log when it goes to the corresponding microservice.

In our architecture, it first goes to APIM as an orchestration layer, and then it goes to the individual microservice layer. For instance, if we discuss the payment API call, it first happens in the APIM section and then goes to the corresponding microservices. The part of APIM that I find very useful is enabling headers for troubleshooting, which you cannot do from the microservice layer logs; you can only do it from the APIM logs.

For Microsoft Azure API Management, the current problem is that the log cost is very high. It is a very good tool, and there is no doubt about that. If you are on Azure and using Azure logs for troubleshooting, then APIM logs or Application Insights logs are the best. However, in terms of cost, if your log ingestion is very high, such as 1 TB per day, then the cost is quite significant. There should be some kind of discounts for high-volume users.

For the company I work for, they use Azure APIM and are struggling with the cost. I know several companies that faced the same issue and switched to other solutions or open-source tools, but they did not get the best solution they used to have. They had to compromise due to the high cost of logs, especially APIM logs, which are extremely crucial.

If you have an Azure-native solution, then Microsoft Azure API Management is the best choice. APIM is a PaaS tool. Microsoft has structured it cleverly, as it will not allow you to directly take the data from anywhere; you need to send the APIM logs to Event Hub, and from there, someone needs to pick the data. On the other hand, microservice layer data is acceptable, but with something such as AppDynamics, which is a SaaS product, you first need to place your agent on all microservice layers to retrieve data. In APIM's case, since it's a PaaS service, you cannot attach an agent directly, and the APIM needs to write policies to forward logs to Event Hub, where AppDynamics can then collect the data. This adds complexity and cost.

I have been working with Microsoft Azure API Management for two years, and I want to clarify that APIM is used basically from a logs perspective, not actually from a product perspective. When the customer API calls come from our Azure Gateway, they go to APIM, and from APIM, they go to Application Insights. Since I take care of the monitoring side, APIM is only used for log checking and those kinds of things, not for API development, which I do not handle.

Microsoft Azure API Management is suitable for both medium and enterprise-sized companies. Small companies might prefer some kind of open-source tool because APIM is costly, and they might not be able to afford it. For mid-size or enterprise levels, they should definitely go for APIM. I've worked with multiple tools from an observability perspective, such as Dynatrace, AppDynamics, Splunk, and Elasticsearch, and I find KQL and APIM amazing and filled with useful features.

The need to manage costs is crucial because companies are stressed about it. In terms of cost, log ingestion can reach around 200 INR per GB, translating to 2 lakhs INR per day for 1 TB. For five days, that would amount to 1 million INR, which is a hefty sum for any company to sustain with this log solution.

The technical support from Microsoft is very good. They are very helpful, timely, knowledgeable, and responsive in their support efforts.

Positive

We use some dynamic alerts with Microsoft Azure API Management, which I configure via Azure alerts, but I'm not fully aware if they qualify as AI features. I also use Copilot, which is also a Microsoft initiative. However, from the APIM perspective, I have not utilized any AI features so far. As AI continues to evolve, I would be happy to adopt any AI-enabled features in Microsoft Azure API Management, but I haven't encountered any yet.

The initial setup of Microsoft Azure API Management is very simple and not complicated at all. The only prerequisite is that you need to know KQL to manage the logs and everything, but from a configuration perspective, Microsoft has well-documented processes, and it's clear in easy steps.

I am still with Microsoft Azure Monitor. I use solutions such as Microsoft Azure File Storage, App Services, and API Management. I'm very satisfied with Microsoft Azure API Management's functionality. My rating for Microsoft Azure API Management is eight out of ten.

Neutral

I am a direct consultant, and I'm using it in my projects to collect the APIs and to provide API management for different APIs with the upstream and downstream. Additionally, I'm using it to streamline operations where any upstream or downstream applications need to give the collective API. I use API Management as a gateway, providing authentication and authorization. When APIs are authenticated, the upstream or downstream verification is sent to our solutions.

Azure API Management has helped streamline our operations by acting as a gateway for upstream and downstream applications. It provides authentication and authorization, ensuring that both verified and suspicious users are managed efficiently. The use of analytics within API Management is also valuable for tracking user behavior and ensuring security.

The most valuable features include throttling, which restricts the user count whenever an API is called, and authentication, which helps identify and manage suspicious users. 

Additionally, the analytics phase of API Management is very beneficial for tracking API usage and identifying suspicious users.

Latency is an area that needs improvement, especially for multi-tenant applications. This was a big issue for us three years ago, particularly when working with Azure Data Centers. Although this problem is not as significant now, improving latency further would be beneficial.

I've used the solution for almost 13 years now.

The solution is highly stable. With high scalability and availability, it supports many users and endpoints without significant issues. The stability positively impacts our operations, allowing us to use multiple APIs effectively.

The solution is very scalable. We have around 3,500 users using it simultaneously. API Management is comfortable with handling 20 to 25 different APIs, and I would rate its scalability nine out of ten.

Technical support is very good. I logged an incident, and it was resolved promptly within three hours. I would rate their service a ten out of ten.

Positive

Before Azure API Management, we were using IaaS deployments and Windows Server 2019. API Management proved to be a great tool, offering better features, especially in terms of throttling and managing API endpoints.

The initial setup was not very difficult. I would rate it an eight out of ten for ease of setup. The solution supports both on-premises and cloud deployments, which adds to its flexibility.

We needed only three to four people for the initial deployment. Currently, we have about seven people working on the project management side for maintenance.

I don't have specific metrics on return on investment, but the organizational value is evident in its high performance and ability to manage APIs effectively.

The pricing is neither very cheap nor very expensive. I would rate it three to four on the lower side of the cost scale.

I did not evaluate other options. I chose API Management because of its excellent reputation and valuable features.

Azure API Management is a great tool to understand and use. It offers high scalability, availability, and performance. I recommend it to anyone needing a robust API management solution.

Our primary use case for Microsoft Azure API Management is to front internal APIs and make them cloud-compatible. It adds extra authentication on top of old APIs and acts as a proxy towards internal APIs, providing a single endpoint that can manage multiple APIs behind it. This is particularly useful for large companies with numerous APIs, as it helps share and create visibility for different services.

Microsoft Azure API Management helps improve our organization by providing a way to front internal APIs, add extra authentication, and create visibility for different services. It allows for secure and manageable API interactions, particularly beneficial for large companies with multiple APIs.

The most valuable features of Microsoft Azure API Management include the ability to change messages on their way in by adding or changing headers, performing authentication using JWT token validation, and throttling requests. Additionally, the ability to create a subscription model for APIs allows companies to monetize valuable data and share it securely.

Microsoft Azure API Management could be improved by enhancing the preview feature, specifically the workspaces. The feature should allow for better delegation of permissions to specific groups without affecting others. The service is extensive and expensive, and this added flexibility would make it more manageable and less prone to errors.

I have been working with Microsoft Azure API Management for around six to seven years. I've used it since it was first introduced.

Microsoft Azure API Management is very stable. I have never experienced any downtime specific to it, although there have been general downtimes in Azure.

Microsoft Azure API Management is extremely scalable. I would rate its scalability as ten out of ten.

Customer service and support from Microsoft has been very slow and inefficient. The initial support engineers are often not qualified, and the process involves multiple levels of explanation and back-and-forth, which can take an extremely long time, even for simple issues.

Neutral

The initial setup of Microsoft Azure API Management is relatively easy and can be completed in about thirty to forty minutes. However, managing it is a different story due to its complexity. Significant knowledge is required to handle the various features and functionalities effectively.

Microsoft Azure API Management is a consumption-based service rather than a licensed one. It costs around 30,000 Kronas a month, which translates to about $3,000 dollars monthly.

Users should create a design plan and think about splitting responsibilities to keep the service less complex. 

Overly complex configurations can become difficult to manage. There are many tools and libraries available, but official methods should be followed to avoid added complications. 

Keeping the setup simple will reduce the complexity and make it easier to manage.

The tool provides the data in an API, and our company fetches that data to our clients' websites. We also provide API data to the clients we handle.

The solution's most valuable feature is that it is very simple to manage, especially because I have good experience with Microsoft products. The tool is very easy to use and manage APIs.

I don't think anything needs improvement because the tool is up to date.

Sometimes, we face some issues with the tool, but they are manageable. Previously, our company's cloud services were shut down, and we used to take more time to update services, so such issues are areas where improvements are needed.

In the future, I want to see the tool offer API integrations. It can help us manage things in a more effective manner. For example, if we are integrating with any platform, it should provide ways on how we can integrate because each platform comes with different compatibility points. Changes in the tool can be helpful to deal with compatibility issues and resolve them.

The only problem with the tool is that the cloud services were shut out. That's the challenge you had. AI features could be added to the tool to make it more easy to manage.

I have been using Microsoft Azure API Management for two and a half years. My company is a managed service provider for our US clients.

It is a 99.99 percent stable solution.

It is a very easily scalable solution. There are no limitations to adding any number of devices.

The solution's technical support is satisfactory. I rate the technical support a nine out of ten.

Positive

I am only working with Microsoft Azure API Management. I don't have experience with another vendor. From the beginning of my job, I have been working with Microsoft Azure.

I think AWS and Azure are providing similar services, but Azure is a little bit easier.

The product's installation phase is simple and not too complex.

Actually, we work in a team, so we divide all the work in the team. We have a three-person team for the tool's deployment.

The solution can be deployed in a day.

The tool can help save time by around 15 to 20 percent. If I am working in AWS and with Azure, I see that Azure is much easier and helps save time while also being able to manage and deploy the API services.

I would describe the tool's price as being in the mid-range category.

The security part is handled by another person in my company. I am handling the APIs only. I also deal with the analytics part of the tool.

The product's maintenance phase is easy.

I think it is a bit easy to integrate the tool with other systems. One person who works with AWS feels that it is a bit complex to integrate it with other systems, while Azure's integration features are a bit easier to manage. In terms of integration, Azure is easier than AWS.

Currently, I don't see any API integrations.

I rate the tool an eight out of ten.

We are working on almost everything Microsoft Businesses, Dynamics CRM and Dynamics FinOps ERP. We are utilizing Microsoft Azure hosting platform. We are using API service, Azure functions, event grid, API Management, and all types of Azure services on a need basis.

The integration and API Connect are valuable when we need to connect with web services and REST APIs. Microsoft Azure API Management covers all the security guidelines, security standards, compliance, which includes data security at rest and in transit, making it good from a security perspective.

The licensing part of Microsoft is always higher than other platforms, like Amazon services and other cloud services. Microsoft should work on reducing the cost.

I have been working with API Management for almost seven years.

On a scale from one to ten, I would rate it eight out of ten for stability.

On a scale from one to ten, I would rate it eight or nine out of ten for scalability.

I have heard from others that Microsoft support often takes five to six days or even up to 15 days to resolve issues, so there is room for improvement in response time.

Positive

The initial setup is a plug and play process. It does not require a lot of customization or configuration. We just need to configure and set up these things, making it easy.

They will always need someone from the development team or a vendor to perform the setup. It is not so easy that everyone can do it on their own.

The cost is higher than that of other platforms, even if used on a consumption or need basis.

Amazon services, Oracle, SAP, and Salesforce, are competitors. However, I do not have much experience with the competing part.

Overall, I rate API Management at eight out of ten. 

While I can recommend it, for the past two years, I have also been considering open-source options. It's beneficial to research open-source tools for viable alternatives.

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're still in the early stages of exploring its full potential. It's a new implementation, so we haven't fully formed our opinions yet. But it's promising! We're cautiously optimistic about its capabilities.

Price is the first thing that comes to mind. It's quite expensive, which could be a barrier for some users.

So, pricing is an area of improvement. 

I have been using it for over a year.

It's too early to fully assess its stability because all my databases are not yet integrated. It's "stable" in the sense that it's functioning normally for the current setup. However, I can't guarantee its stability or flexibility until all our databases and financial systems are integrated. That's the true test.

It seems quite good so far. It handles our current workload well, and I'm optimistic it can scale effectively as our needs grow.

There are over 200 end users in my company. We plan to increase the further usage. 

We have taken up premium support. Premium support guys are very good in terms of technical know-how. If there was any challenge for them, they used to interact with the Microsoft guys.

We used Oracle API Management. It's good for specific things, it's an open API. But Microsoft is easier, and can do anything, the world is moving towards Datatrix for all those things. That's why we use it.

The initial setup is easy. Deployment itself is straightforward, technically speaking, but the high cost is a major drawback. It's not exactly budget-friendly.

We partnered with a Microsoft Premier Partner for the deployment. They provided valuable expertise and support.

Deployment is straightforward, not complex at all. It was a smooth process.

Currently, it's on-premises. We're migrating it to the cloud, but it's in the testing phase and undergoing acceptance testing for the new environment.

We have a team of 12  to 20 people for project management, one business manager, and one client manager.  

It helps connect all multi-environment applications to a single dashboard and give beautiful reports. It helps with internal operations by providing a single-page summary report. It's a one-stop integration page.

The price is very high. It is very expensive. We have an enterprise agreement. So, every anniversary, we renew.

Overall, I would rate the solution an eight out of ten. It's great for organizations, they can adapt. But again, it's case-by-case. The co-pilot from Microsoft is fantastic. We use that, and they went for the 300 languages and offer fantastic API. It is value for money. 

Our primary use case for Microsoft Azure API Management is as a gateway for all API management within our tech environment. It serves as a basic part of our DevOps toolchain.

Microsoft Azure API Management is a basic part of our DevOps toolchain.

Microsoft Azure API Management serves as a gateway for all API management within our tech environment and is a basic part of our DevOps toolchain. We utilize it for control and monitoring, particularly for the security aspects of our APIs. 

It provides easy integration within the Azure environment and with third-party SaaS applications, like integrating our point of sale system and our loyalty system under Mastercard.

Microsoft Azure API Management could be improved by enhancing the visual editor of the development portal. Considering that everything is moving towards low code or no code, having a management or development portal with a more intuitive visual editor would be beneficial.

I have used the solution for two to three years.

I rate the stability of Microsoft Azure API Management as nine out of ten. We have not encountered significant stability issues.

I rate the scalability of Microsoft Azure API Management as nine out of ten, indicating that it is quite scalable.

Microsoft support has greatly improved, with resolutions being fast depending on the severity of the ticket raised. I am very satisfied with the support provided by Microsoft.

Positive

The initial setup of Microsoft Azure API Management is straightforward, and I would rate the ease of setup as seven out of ten.

Azure API Management is priced reasonably. The license costs about $150 per month.

We did not evaluate any other API management solutions, as our focus was more on integration platforms.

API management is a crucial component when building an enterprise's integration platform. Microsoft Azure API Management is a good tool, especially when there are many workloads and resources within the Azure environment. 

I recommend using this tool, and I would rate it eight out of ten.

We have several layers in our infrastructure. Some of our layers are more connector-based and interfacing with our systems of record and outsource service providers. Right now, we use Microsoft Azure API Management for that. We're now deciding what to use for the process layer, which is more orchestration and data-mapping-based.

If you were truly a .NET shop and truly Microsoft cloud-centric, this is the most cloud-native offering, and there are some benefits to that. It's really easy to use for simple passthrough APIs. It feels more modern and compatible with people with .NET skill sets, and that's a strong selling point.

The solution's data mapping and orchestration are very code-intensive or require callouts to external systems. They seem suboptimal for the more complex use cases.

A simple installation is very easy, and I rate it ten out of ten. However, it goes to the other extreme when you try to do complex use cases, like orchestration, aggregation, and data mapping. For such scenarios, I rate the installation a five out of ten because of the code intensity and maintenance you would incur.

The solution appears cheaper because it's a cloud SaaS model. Its benefit is that you can use a small amount, and it'll appear very cheap. However, once you scale up to your full volume, it'll be more expensive because it'll incorporate a bunch of different services that are holistically more expensive than the alternative.

There are around ten key security characteristics I look for in a solution. On the surface, my analysis so far seems to indicate that Microsoft Azure API Management has the ability to deliver on those parameters. Given the close relationship between Microsoft and OpenAI, we hope the solution will evolve more quickly and incorporate AI more fully, but we don't know for sure.

Our goal is to create a composable financial institution. We are trying to get developers not to be the bottleneck anymore but to be more agile, to grow market share, and to grow national reach. To do all those things, you need very agile, world-class APIs. There are ways to make both work for that. We'll have to evaluate which one is the shorter path.

I would recommend the solution for cloud-native Microsoft .NET shops with simple API requirements. However, I would not recommend it for multi-cloud, larger shops with more diverse or complicated use cases.

Overall, I rate the solution a six out of ten.