Microsoft Azure API Management Reviews

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're pretty much using all of the monetizations features out of the API manager so we can put up a portal and have a dev portal and then a prod portal and do rate limiting.

They're trying to implement versioning and trying to be able to manage different versions of your API all at the same time, but they're not doing that just quite right yet.

I have been using this solution for a year. 

We haven't had any issues with stability. Those things are pretty solid.

I haven't dug too deeply into how to scale it yet. My current customer doesn't have a high volume of stuff yet.

In terms of users, there are only two or three of us engineers that deal with it directly. We're running several dozen APIs that are production APIs.

I give technical support a solid B rating. They're not bad on doing support at all. They're not necessarily fast, but they're not bad.

It's very straightforward to set it up. It really is. That's one of its strengths, that it's very easy to get started.

The versioning makes deployments more complicated than you would like, so you have to build some of your own toolings.

Licensing is the tricky part. For Azure, if you have your Azure subscription, the API Management is a free tool. There's no extra cost for that. 

My advice would be to choose wisely. Look around. That's the free entry stuff, so that's why I'm kind of looking around for another tooling solution, to see if I can get more full-featured support.

In the next release, I would love to see them actually support out of the box, like a canary deployment pattern, or out of the box just a blue-green rolling deployment pattern. Right now, how you want to do your deployments, you've got to tool it yourself.

I would rate it a seven out of ten. They're not bad.

My primary use case is application monitoring.

We had all our Saas applications on the cloud, so it's easier to centralize everything in Azure, including configuration and maintenance. There's also no need to get another portal for maintenance on additional things, so we can monitor the issue directly.

The most valuable features are the Active Directory integration and wireless backup.

Azure API Management could be improved with better integration with all of Microsoft's tools. They should also provide basic cybersecurity tools in the package.

I've been using this solution for two years.

Azure API Manager is stable.

This solution is scalable.

Microsoft's technical support is helpful, although there are some issues with time zones.

Positive

The initial setup was easy - it didn't take long, and the additional features were added normally.

We implemented using an integrator.

There are no additional costs above the main license.

We're very satisfied with Azure API Management. We've had no issues with bugs, everything runs smoothly, and the connection between the cloud and the on-premise infrastructure was good. I would rate this solution nine out of ten.

I primarily utilize the platform for integrations, monitoring, and process automation within our business workflows.

The solution's configuration capabilities are the most effective features for enhancing API security.

The product's navigation feature needs enhancement. 

I have been working with the platform for approximately three to four years.

I rate the solution's scalability around eight or nine.

The support services are good. However, they could be improved. 

Positive

The deployment process is not overly difficult. However, each API integration presents interface connectivity and parameters, which can introduce challenges.

The time required for deployment varies depending on the integration interface in question.

I rate the solution's pricing between three and four, as it could be more competitive.

The platform's insights improve over time, allowing us to monitor system health and receive notifications for updates.

We integrate it with Dynamics and other business tools, which enhances our data analysis and reporting capabilities. It facilitates better insights and easier data manipulation, although I rely on my team for detailed analytics.

I recommend the platform, particularly for organizations that require API utilization and integration, as it has proven to be effective in our experience.

Overall, I rate it an eight out of ten. 

We use the solution for API management.

The most valuable features are the API and integrations.

The implementation has room for improvement and can be more user-friendly.

I have been using the solution for one year.

I give the stability an eight out of ten.

The technical support team is good.

Positive

I give the initial setup an eight out of ten. The deployment took one business day. We require two people to complete the implementation.

The implementation is completed in-house.

Compared to other solutions the cost is a seven out of ten.

I give the solution an eight out of ten.

We have an Enterprise Agreement with Microsoft, so they are providing whatever support or help is needed.

For people that are already using other Microsoft Azure solutions, I recommend Microsoft Azure API Management.

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

The most valuable feature of Microsoft Azure API Management is the developer portal because it's very quick and easy to get something published.

Microsoft Azure API Management could improve the documentation. The documentation feels like marketing information and not sufficient technical information. Your easiest option is to purchase services from a Microsoft partner and this is their marketing.

In a feature release, there could be a better Canary release. They have a release but you need to code it yourself.

I have been using Microsoft Azure API Management for approximately two and a half years.

We have approximately 30 people using the solution in my company.

The support from Microsoft Azure API Management is okay.

The initial setup of Microsoft Azure API Management took us three days.

We did the implementation of the solution in-house.

We are paying standard fees to use Microsoft Azure API Management.

My advice to others is before getting into the solution, it is best to be certified so that all of the details you would need to know that are not easily available online, you would be mindful. It is a very good solution, but some features feel hidden at best.

I rate Microsoft Azure API Management an eight out of ten.

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

We really like the scalability.

It’s easy to set up.

The cloud deployment performance could be better.

Technical support could use some improvement.

I’ve been using the solution for three years.

It is stable. However, its performance is not better than an on-premises deployment.

The solution can scale and is easy to expand. It’s actually quite impressive.

We have about ten clients using the solution.

Technical support could be better. There’s a lot of bouncing around. It’s not orderly.

It is a straightforward setup. The implementation is not difficult or complex. The deployment is quick as well. It only took two or three days to get everything up and running.

We have about five technical people who can handle the setup and implementation process.

We are a Microsoft-managed partner, so we do have some pricing from the distributor.

The licensing is dynamic as it is based on cloud usage.

I can recommend Azure Block Storage to other people. However, they need to have an open mind in order to use cloud storage.

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

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.

The most valuable features are authentication and authorization. I would also argue that the mediation and translation from SOAP to REST technology is equally important because it makes it possible to open up legacy systems that couldn't be opened before.

An improvement would be to provide more information about additional prices and the onboarding process.

I've been using this solution since 2016.

Azure is very much stable.

This solution is very scalable.

You really need an expert to onboard the solution because it comes with more complexity than you might think. Also, internal teams often start playing with the solution during onboarding instead of sticking to best practices, which can result in having to start the process over again.

The ROI on API management as a concept metric that we are using in conversations is that we can reduce integration lead times by 90%. So, where an integration would take a hundred days before, we can deliver that same integration in ten days after implementing Azure.

Azure's pricing is very competitive compared to platforms like Apigee and MuleSoft. However, when you start with Azure API management, you also need to onboard the Azure console and the Azure cloud environment, which comes with a price.

Azure is the best-priced quality solution in the market. If you have business-critical processes running over API management, I would advise installing managed services either internally or from a partner to have that very close follow-up. I rate this solution eight out of ten.

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

Furthermore we enable transparency, governance and re-use.  

- Being a PaaS component it helped reducing maintance efforts
- Homogenous solution for information exchange between internal and external stakeholders 

The most valuable feature would be the easy integration into the entire Microsoft environment, like Access Directory, the collaboration tooling, the development tooling, basically the integration into the Microsoft universe.

Multi-tenant functionalities is missing from the system, especially when it comes to purpose specific requirements such as CI, branding, language, content structure. If you're aware of the details of API Management provided by Azure, there are two areas. One is for developers, and the other is for consumers. In order to support the best, or all the different use cases we have, the multi-tenant support would be appreciated.

I've been using the product for about three years. 

The product is stable, it's good. It depends a little bit on the tier, on the different settings, and different customizations that are possible. But in general, it's a stable solution.

Technical support to a certain extent is good, it's available in the internet, if you wish. The moment you need to reach out for serious technical support in terms of incidents, or on-site support, or whatever, it becomes a little more challenging.

The initial setup for us was easy. It helps that we have Azure knowledge within the company.

Understand the different Tiers (from small to large including VNet-integrated express route)

Start small and be aware that the developer version has all features enabled which also requires the highest possible Tier.

Approach API Management in the two areas "tooling" and "governance".

Tooling required end-to-end thinking from a developer, consumer and infrastructure perspective. For each multiple examples can be shared.

For governance start with the obvious fitting to your organization. Do not follow all recommendations from the start, hence expect an iterative approach.

I would recommend this product and would rate it an eight out of 10.