Microsoft Azure API Management Reviews

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.

We are using Azure API Management as a platform. We have a ServiceNow instance. We connect it to the internet to have an internal connection network through on-premises systems. Here, we need to expose our APIs to security. So we take the help of Azure API Management for security purposes. Also, we can use dashboards to get information about API requests.

The solution's most valuable feature is the ability to create policies. You can customize the business and security rules directly with it instead of creating new systems for managing the same. With this policy, you can develop anything with them.

It is a good solution. The latest versions of Azure API Management have included many new features. At the moment, our APIs don't follow the RESTful concepts. So, we face a challenge at the initial stage of the project. We need to get cache policy requests. We have to develop rules internally for cache requests with the policy methods. So many other companies must be needing this feature. They should work on it in Azure API Management's following versions. 

We have been using the solution for four years now.

It is a stable solution, but updates don't work.

We have more than 400 developers and more than 1,000,000 consumers using this tool.

We have a technical consultant. Microsoft support is excellent. They offer a good support solution.

I didn't know about any other API Management solution before, but I had read about the Apigee from Google. Azure is better as it's easier to use and has more features than Google.

It takes work. One needs to learn about this tool, the policies, and how to work with them.

We have consulting companies that help us. The API Management is simple to deploy. We have instances for the production, developer, and staging environments. We have three instances, and the APIs also come with ARM templates. We have a central repository of Azure. Creating a new instance takes a long time, but implementing a new API is faster.

The solution comes with a standard license. Its price is one of its drawbacks. Some costs need to be more affordable for us. Frankly, Azure is our most expensive resource; it's costly.

The solution is very easy to maintain. With it, we can integrate all other products and easily manage them. We have all the interactions in the same cloud.

In API Management, we have segmented consumers' APIs and secrets' APIs. We have global secrets and patents. It is easy to use after you learn and research about the tool. So, one must learn about this tool before implementing it or have a consultant to help with the initial feedback and organizing API products.

I would like to rate the solution as an eight as the price is not low, and it becomes difficult to afford it. It's easy to use, but it could have been easier.

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.

We use Azure API Management as a migration tool and for security. We have services interfacing with Boomi and APG, and we're migrating them to Azure API Management and Azure Logic App. This involves writing integration logic in Logic API and exposing APIs securely to external networks. We also integrate Snowflake with ServiceNow data using Kafka and Azure API.

Our primary advantage with Azure API Management is the ability to achieve real-time data updates for user queries. This is vital in retail, where customer concerns need immediate attention. By using Azure API Management with Snowflake and Kafka, we maintain accuracy and speed in our data processes and transactions.

Security is the top feature of Azure API Management. It allows the use of existing identity servers or OpenID for secure API sharing. The speed of deployment and the ability to integrate legacy databases using API wrappers for external exposure are also valuable.

Azure API Management lacks integration capabilities seen in other tools. It should at least handle basic transformations, which currently fall to Azure Logic Apps. Including a mapper, like IBM API Connect, would be beneficial. There's a need for better integration features without additional solutions.

I have been working with Azure API Management for approximately two years.

Azure API Management is stable. I haven’t encountered significant issues, and I would give it a nine out of ten for stability.

Azure API Management earns a seven for scalability. I feel there are fewer features to explore, compared to other API management solutions.

Microsoft technical support is excellent, and I would rate it ten out of ten.

Positive

Google APG and IBM API Connect are some of the tools used earlier. They were preferred for their integration capabilities and better mapping features.

The cloud setup for API management is simple. However, for hybrid or on-premise models, it requires considerable resource allocation, needing multiple virtual cores and a Cassandra database.

Azure solutions are priced very low, which is a benefit. However, if additional features are required, like AI integration, more investment might be necessary.

Google APG and Kong API were evaluated as alternatives. Google is considered better because it offers integrated features within API management, like Gen A features.

Azure API Management is better suited for enterprises due to its extensive toolset and roadmap for data integration and scalability. For smaller companies, lightweight alternatives like WSO2 are recommended.

I'd rate the solution seven out of ten.

We primarily use the solution to manage our APIs.

The ease of use of the solution is excellent. It's a very user-friendly solution. 

The initial setup is quite straightforward. 

We found the solution to be very stable.

The solution can scale if you need it to.

Technical support is very helpful.

The solution has very fair pricing.

The lack of wording in the API could be improved. In the API you need to delete the suffix. It is annoying that you need to have a suffix. We can add a suffix at the API level, not at the operation level, and that could be improved on.

There are a couple of features that are lagging.

I've been working with the solution for five years or so. It's been a few years at this point. 

We have found the solution to be quite stable. There are no bugs or glitches. It doesn't crash or freeze. Its performance is reliable. 

The solution scales well. If a company needs to expand it, it can do so with relative ease.

We have about 15-20 users on the solution so far.

Technical support has been very good. They are quite helpful and responsive. We are very satisfied with the level of support provided to us.

The initial setup is straightforward. A company shouldn't have any problems during the process.

The cost of the solution is very fair. It's not overly expensive. It offers very good value.

We are Microsoft partners.

I'd recommend the solution to other individuals and organizations. Overall, I've been quite satisfied with its capabilities.

I'd rate the solution seven out of ten.

I like API Management's ability to do hybrid cloud stuff.

Some of the DevOps stuff could be easier to work with. The migration paths are a little complicated, and moving code around could be more seamless. There should be less manual migration when several teams work together to publish code to the DevOps. 

For example, if you and I are working on the same application, and there are conflicts, you should be able to resolve those conflicts more easily. It shows you the conflicts, and you have to fix them yourself. Better conflict resolution with software migration is what I recommend.

I've been working with Azure API Management for maybe five years in total.

Azure API Management is relatively stable.

Azure is a pay-as-you-go model. You build out your virtual environment and pay a monthly price depending on CPU cores, storage, etc.

I rate Azure API Management nine out of 10. I prefer Microsoft products to the others out there because Microsoft has always catered to software developers as opposed to Amazon or Google, which do a lot of other things. Microsoft has always had the best development toolsets, and it's better for application developers.

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.

If I want to expose API endpoints to clients, we use this solution. 

The API management is great. It comes out of the box ready to go and comes with policies. 

It is stable.

Technical support is good.

We have witnessed an ROI.

We have to put the logs in Datadog. We need to use some other product to do all of the things we want. That costs extra. However, there are other solutions, like Dynatrace, that offer more features and have more functionalities. Right now, we have to use logic apps. You need more third-party apps to fill in the gaps. 

If I want to connect to other apps to Saleforce or Snowflake, et cetera, I need a quicker way to do mapping and to integrate everything together. 

I need to have microservice access. 

I'd like to have better flexibility and more capabilities. 

I've been using the solution for three to four years. 

I'd rate the stability seven or eight out of ten. It's reliable. There are no bugs or glitches. 

We do not scale the solution. We don't need multi-tenancy or anything like that. Our understanding is that if we did need to scale it would cost more. 

Technical support is very good and is available around the clock. 

Positive

I'm familiar with a variety of other solutions, including Mulesoft.

I have witnessed an ROI while using the solution. 

The pricing is expensive, however, it does offer great value. I'd rate the solution seven or eight out of ten in terms of value for money.

I'm not sure which version of the solution I'm using. 

The product covers all of the basic needs you will need. If you need more robust options, Mulesoft might be a good option. However, this is a pretty good tool

I'd rate the solution an eight out of ten.

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.

The policies on offer are the most valuable aspect of the solution. 

The solution is reliable and very stable. 

I don't really have anything in mind at the moment in terms of areas of improvement. It does what we need it to do for the most part.

Technical support could be more helpful and responsive. They are quite slow. 

The documentation around the solution is lacking. Users will need to do a lot of digging and googling in order to get the answers they need. 

The premium version is very expensive. 

I've been using the solution for about two years now. It hasn't been too long at this point. 

The solution was stable. We didn't have issues with bugs or glitches. It didn't crash or freeze. it was pretty reliable and the performance was pretty good. 

Technical support was a bit slow, actually. We did engage technical support once or twice and it took quite a bit of time for them to come back to us. By the time they'd come back, we'd kind of solved the problem ourselves. They weren't overly helpful.

I'm just a developer, so I didn't really get involved in the pricing. Therefore, I can't speak to the exact costs of the agreements involved in terms of licensing. That said, I do know that we used the developer license just to try things out. My understanding is that the premium version is quite expensive.

I'm a customer and an end-user. My company does not have a special business relationship with Microsoft.

I'd rate the solution at a seven out of ten.

While technical support and documentation are lacking, I would still recommend the product to others. 

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.