Microsoft Azure API Management Reviews

The solution has pretty stable capabilities.

Their construction tool allows users to easily publish information about the API. It's basically just one click.

You can configure the subscription management onsite and link everything.

The developer portal that exposed the API documentation is great. You can just test the APIs in a very easy way. 

The web portal is useful. You can build a pretty comprehensive portal where users can sign in and you can basically leave the API there.

The API management provided offers good integration with different management systems, like OpenID, for example.

The user management is pretty seamless.

Pricing is definitely an aspect that can be improved. They should offer an additional free tier. For example, if there was a tier for new accounts created, it may help their services by getting people onboarded. Once you will give access to someone and they try it they'll see, "Okay, it works and you can pretty quickly add something on top of it". After that, the client will end up staying, and probably paying.

The cost is also complex in terms of calculating how much everything will ultimately be priced at. It's not straightforward as it takes into account multiple factors.

Technical support could be more flexible and try to meet the client's needs a bit more effectively.

The solution needs to provide more use cases so that we can refer them to clients. It will help answer any questions in relation to performance and load management.

I've been using the solution for about a year at this point.

There are some bugs that exist in this construction tool for the developer portal. We are submitting these bugs to Azure, so they already know about it. Overall, it's pretty stable.

In terms of Azure technical support, we've had no issues in regards to response times. They are prompt. However, in some particular cases, they unable to be flexible. For example, with MQTT blockers, while you might want another port, they might tell you to use the hosted solution in order to get them to configure it. We'd just like them to have more flexibility with requests like this.

In terms of corporate security nowadays, it's very important to be flexible. At the end of the day we get stuck in the bureaucracy. If they could practice flexibility, it would be better for their clients, who may not have the wiggle room on their end.  

That said, we're mostly satisfied with their level of service.

The solution has a kind of calculator and it's not always straightforward to figure out the logic in pricing. There are lots of services that are managed in different ways. For a non-technical person, it's a nightmare to figure everything out.

At the end of the day, you have to build approximate pricing for the solution. According to my experiences in multiple projects, you do get preliminary pricing that is close to or the same as the estimate.  

Right now, for a particular client, we're using a managed version of the solution, however, in the future, I foresee us hosting it somewhere in the cloud.

We're using the most up to date version of the solution.

Overall, the solution has a lot of great features. There are a few bugs here and there, however, a the end of the day, there's lots of value provided.

I'd rate the solution at an eight, on a scale from one to ten. It's got a rather high cost and still has some areas that need some improvement. Otherwise, I'd rate it higher.

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 like that security features can be integrated with API Management. I also like that you can perform rate-limiting and throttling functions.

You can host multiple API gateways in different locations. If one goes down, then another will take over. Microsoft Azure API Management is good in terms of nonfunctional requirements.

The documentation is neat and organized, and as a result, we rarely have the need to contact technical support. 

Microsoft Azure API Management is lagging behind Apigee and should also have a better CICD process.

I used it for six months.

It's a stable solution.

Because it is on Microsoft Azure, we don't have to worry about scalability. I would give scalability a rating of ten out of ten.

Technical support is very poor and needs a lot of improvement. The process is not straightforward, and they are hard to reach.

Because it is a cloud solution, the initial setup is straightforward.

It is an expensive solution, but any API solution will be expensive.

Overall, I would rate Microsoft Azure API Management at nine on a scale from one to ten.

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.

Other than the cost, it is difficult to customize. The external policies are impossible to look at and configure.

The deployment time is too long. It is difficult to have multiple authentication mechanisms and authorization mechanisms at the same time.

Microsoft Azure API Management has not improved since I last used it in 2017.

By using Azure you are forced to use their technologies. For example, I wanted to use PostgreSQL, but I could only use SQL server. I also wanted to use Java or TypeScript, but the only option is .NET, which we do not use. They are very difficult to collaborate with as the solution does not integrate with other products. 

They do not offer extensions, if you want to use a Swagger extension you have to use XMLs, which are very complicated.

Another concern is that Microsoft Azure often does not have enough Linux machines in the region. If you want to deploy on Linux, and there are not enough, they will tell you to deploy in another region, or it has to be on the Windows server instead.

I have been using Microsoft Azure API Management for two years.

The solution is a bit more stable than it was in 2017. It is reliable.

Azure API is scalable. We have 20 people working with this product as a gateway to the outside world.

Technical support with Microsoft is poorer than AWS, but better than the one from Google Cloud. They reply too late. We had premium technical support at one point, however, they did not reply with anything we needed at the time. There is a concern with the knowledge base as well as the procedure in how they are instructed to reply.

I would rate technical support a three out of five.

Neutral

We switched to Microsoft Azure API Management because two years ago, someone in the organization decided to use this solution. I would never have made that decision.

I have had prior experience with API Gateway and Apigee.

The solution takes one hour to deploy. Like everything on Azure, it is difficult to create the deployment scripts because the ARM and Bicep that they use are awful. Deployment is very complex.

I would rate the experience of the setup of Azure API Management a two out of five.

The solution doesn't require maintenance as it is cloud-based. However, it does require monitoring.

The upgrade to Azure API costs 2000 euros per month, per instance, per unit. Our finance department asked us to find cost reductions. After conducting an analysis, I came to the conclusion that it was impossible unless we sacrificed security.

Azure API Management is the most expensive solution on the market. AWS is at least four times less expensive. Any price comparison needs to include the additional cost of the security you will need to purchase from Microsoft, which comes from their premium plan. The only way to reduce the cost is to sacrifice security when using Microsoft data.

I rate the pricing a one out of five.

The other option is API Apigee. It is the best in class and less expensive. Its deployment to API Gateway from AWS is easy and fast. 

In AWS API Management you can build everything from open API specification files. AWS has Swagger extensions that are built in that can define everything in Swagger.

I would switch solutions if I could. 

Any organization looking to implement Microsoft Azure API Management should look at other alternatives. Be cautious of the marketing behind Azure products. Once you decide on your solution, it is difficult to change.

I would rate this product a four out of 10 overall.

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

This is a One Place solution for the majority of needs in an IT and Software development environment.

Microsoft Azure API Management is better because it has a DevOps integration by default.

It would be better if it were easier to transition to Azure from JIRA. For example, there are different nomenclature that must be addressed when you shift to Azure from JIRA. JIRA's storage, tasks, and epics are treated differently from Azure. 

Here they might become functions, which is not an option in JIRA because that nomenclature difference is there. 

JIRA has sub-tasks, but sub-tasks don't exist in Azure. The nomenclature and the linking between Epics and a function and a story are different, and people may have to learn to adapt to the new nomenclature.

I have been using Microsoft Azure Project Management for about Two and a half years.

Microsoft Azure API Management is pretty stable. We are Microsoft gold partners, so we have not faced any issues until now.

Microsoft Azure API Management is scalable. The Microsoft platform supports my organization, which is 35,000 employees strong.

Technical support is pretty good. 

We were using JIRA which can be enhanced by using third-party tools, this is a costly business so we shifted to the Microsoft platform, which was integrated for development as well as management. So that's a better way of doing things.

The initial setup is straightforward. It was an organization-wide integration, so we have never faced any issues.

It's free for less than ten users. If you want to go beyond that, its paid. But when you use all features of Azure its a very cost effective solution.

Costs depend on the size, complexity, usage, and what facility you want to integrate. So, we use Microsoft Azure and have the entire DevOps and Visual Studio on the cloud. We get all enterprise flavor with very optimum cost, when compared to multivendor environment.

I would tell potential users to go for it. It's a good platform. Even though the ecosystem may not be that strong, it's a better option for a software development company. You can explore other options to save some bucks if you are not into software development. However, for an IT company, Microsoft Azure is the better option.

On a scale from one to ten, I would give Microsoft Azure API Management an eight.

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 like the API management functions.

In terms of the flexibility of API Management, it's quite a complex solution when compared with Apigee. If they could come up with an easy way of enhancing, that would be a great help, particularly for those consulting.

I've been using this solution for two years. 

The solution is stable. 

We deployed a Kubernetes instance so that we can scale.

The technical support is great, they help us out whenever we need it.

Positive

From previous experience, I know that Apigee is more flexible than Azure API.

The initial setup is not so straightforward and really depends on the landscape. If a customer has different business streams such as credit cards, debit cards, payment accounts and credit accounts it can be more complicated. Things have improved recently. Previously, a deployment could have taken up to 18 months.  We can now do a similar implementation in around six to eight months. 

There are a lot of competitors in the market that provide the same kind of services but I think cost-wise and resource-wise, Microsoft is ahead and I recommend this product to our customers. That said, there are some functions we don't currently have. It's okay for a mid-size organization but for larger-scale deployments, it's lacking in some areas. As a result, I rate this solution eight out of 10. 

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's most valuable features are the microservices we used to use. They were API callers to receive communication with the network and building system, to complete the request. The response would be through the processing system.

I have been using Microsoft Azure API Management for approximately one year.

Microsoft Azure API Management is stable.

Microsoft Azure API Management is 90 to 99 percent scalable. We have three instances running in parallel.

We have approximately 500 to 800 internal users using this solution with three applications in operation.

We do not have plans to increase usage.

We have not contacted technical support. We have our own team.

The cloud deployment of Microsoft Azure API Management could be better.

Our team of 14 to 15 members implements and supports the solution.

I would recommend this solution to others.

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

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. 

The Application Gateway we have found to be the most useful in Microsoft Azure API Management. We have integrated the Microsoft Azure API Management with Application Gateway. Application Gateway is a type of load balancer that we are using for the high availability of our API calls. 

Microsoft is releasing new features approximately every three to four months on each and every solution. Although it's not mandatory that we are using all the features of this particular solution because it depends on the business requirements. Whatever the features the Microsoft Azure API Management has, we are happy with them and we are using them.

The solution is secure and has all the components that we require. We are using the solution with the best practices.

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

Microsoft Azure API Management is a stable solution, it has high availability.

The solution is scalable.

We have used technical support once or twice a year. However, there is not much technical assistance required.

I rate the technical support from Microsoft Azure API Management a four out of five.

The initial setup of Microsoft Azure API Management is straightforward. It took us approximately 30 minutes to complete.

I would rate the initial setup of Microsoft Azure API Management a four out of five.

I rate Microsoft Azure API Management a nine 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.