Microsoft Azure API Management Reviews

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.

The basic tier is pretty good. 

It's publicly available API Management.

The price is pretty reasonable for us. 

We need better integration with VNet. 

It would be nice to not only configure it through the interface but also with an ARM template or something like that. Maybe it's possible, but it's not that easy to find.

It took us time to get used to the interface. Now that we run it, it's a little bit hard to have a testing environment and the production environment and keep it synced. If you can do that through a script, that would be far easier. However, there was a time thing on our side. We couldn't get it done, and in the end, we just set it up manually.

The licensing tiers can be misleading. 

It would be ideal if there was a way to add monetization into the mix so that we could more easily sell our APIs.

I started using the solution about three years ago, and I use it now and again on a few projects. 

We didn't have a previous solution.

I wasn't directly involved with the implementation, and I'm not sure how long it took to deploy the product. 

Some of my colleagues implemented the solution. We did it ourselves using the documentation provided by Microsoft. 

We are using a basic tier. 

For the things we do, it's reasonable in terms of cost. You can implement it in the developer solutions. That's basically more or less free. But if you implement VNET in it there, you can only upgrade it if you use premium, and premium is so expensive. That's just no fun. That was a little bit annoying since you think you have a good solution in your development environment, and then you are in production and need a premium tier to have the same configuration. We had to reconfigure some stuff.

We also looked at Apigee, and Apigee has some integrated features, however, Apigee was very complex to get started with. Apart from that, we are a Microsoft company, and we're on the Microsoft stack. It was more logical to keep everything in Azure. That's why we chose Azure API Management.

We use Azure and it suits our case pretty well. It could be better, but we might also have to learn more. Currently, I would rate it at an eight out of ten for our use case. We might also want to use it in the future to sell subscriptions, which is not possible out of the box. You can configure subscriptions, yet you still have to do the whole selling and measuring and things like that. That's not fully integrated.

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.

We use the solution for API management. 

The tool's most valuable feature is the integration of CI/CD with the API gateway. 

Microsoft Azure API Management needs to improve stability. 

Microsoft Azure API Management is stable; I rate it an eight out of ten. 

I rate the product's scalability a six to seven out of ten. 

The cloud-based version is not difficult to deploy. Microsoft Azure API Management's deployment depends on the API numbers customers want to onboard. It takes around four to six months. 

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

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 most valuable feature of Microsoft Azure API Management is monitoring.

When compared with Apigee, I prefer Microsoft Azure API Management.

When comparing the API Gateway of Microsoft Azure API Management with those of Apigee and Vital Mikram, which are other API management solutions, I prefer, Vital Mikram, the others are similar.

I would like to see more integration with other platforms, as well as increased security.

I have been working with Microsoft Azure API Management for ten years.

Azure has both a certificate and a level certification.

Microsoft Azure API Management is stable.

Microsoft Azure API Management is a scalable solution.

We have ten users in our organization.

We have a team of five to ten technicians to maintain this solution per unit.

Technical support is good.

The initial setup is straightforward.

It was deployed very quickly.

We deployed it ourselves. It was done in-house.

The price is comparable.

In my opinion, it is similar to Apigee.

I would rate Microsoft Azure API Management a seven out of ten.

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.

I have found this solution to be easy to configure, simple to use, and flexible.

If I compare this solution to others I have used in other phases of my life, having APIM being an Azure resource, it is easy to configure and deploy. However, this conversely reduced the flexibility. The difficulty is how do we configure it in a manner that a larger enterprise would probably want it to be. This creates a bit more complexity, working around the constraints of the resource itself. If comparing it to other solutions, it is more of a legacy design with an older approach. The various level components are still around resembling an on-premise type of design similar to other solutions, such as Apigee or Mulesoft. They are still predominantly carrying some legacy design. Which might be suited for organizations where they have a more complex network layout. APIM is easy to deploy, but on the other side of that, it is constrained to how Azure has designed it to be.

In an upcoming release, if not already added through an update, I think dynamic provisioning of the resource would be useful. Many times these API platforms, including others, such as Apigee, are still predominantly revolving around developers. The onboarding and the API life cycle are still revolving around humans. In this context, I would not suggest DevOps, but at least automation of common pipelines. If the platform can better support this in the workflow to provision and commission an API that would be beneficial as we work towards a more automated deployment concept. Even though there are templates, graphics, and API management commands right now, you are still in a way programmed deeply, customizing that workflow, as opposed to it being part of the platform itself.

I have been using Azure solutions for approximately four years.

The solution is stable.

The solution is scalable because it is a cloud service offering.

I have previously used Apigee and Mulesoft.

Since this is a cloud-based solution you have to abide by those financial limits, this creates some different challenges compared to other solutions.

My advice to those wanting to implement this solution is in all technology areas, each solution is use case-specific. If you are already working on the pure Azure Stack, then APIM is something that I would suggest. Unless you have a very complicated API development use case I would not try to deploy, for example, Mulesoft or Apigee on Azure. Assuming you are working on a full Azure Stack solution. 

Since it is use case-specific, rather than trying to build out. I would rather use the other repertoire of Azure to do the API development, as opposed to trying to deploy other solutions under the platform and develop from there.

My philosophy is always, use what is available, rather than trying to reinvent the wheel. Mulesoft may be powerful, but it is putting the cart on top of the wheel and try to build something on the cart. It is not a native approach.

I rate Microsoft Azure API Management a seven out of ten.

The integration with Azure Active Directory is a good security feature for authentication and authorization. There is multifactor authentication. You can also use all of the Azure AD features integrated with API Management. 

There is always room for improvement. There should be more analytics abilities so you can know how much traffic there is. Log Analyzer isn't well integrated with this solution. 

I have been using this solution for two to three years.

It's on the cloud, we don't have any hiccups or problems with the stability. 

The technical support is pretty good. Sometimes it's slow. It depends on each case. Sometimes they need to engage with the US and there's a big time difference between there and Australia so it takes longer. 

Our public APIs are mostly in Axway. B2C APIs are a combination of Azure and AWS. Cost is a big difference. Axway offers two solutions. One on-prem and the other option is cloud. It's not a SAS solution, they host us in AWS but we can push the costs for version upgrades. It's much more expensive than Azure or AWS.

You have to read about how to do it four or five times and then you can implement it. It's a publicly accessible API so it needs a security layer and then you can secure it. Otherwise, anybody can access it. You need proper controls, authentication, and authorization. You need to sort this out first. 

I would recommend doing a combination of AWS API Gateway and Azure API Management. You can authenticate APIs in Azure Active Directory and from there you expose all of your serverless components and use them as a backend with Azure. But it depends on what your use case is. It can be used as a combination or as a standalone. 

I would rate it an eight out of ten. 

To make it a ten, there should be better analytics features so we can know how our product is performing. 

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.