Microsoft Azure API Management Reviews

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.

Microsoft Azure API Management is used for platform deployment, hosting, virtual servers, third-party integrations, and the Azure Marketplace.

Without a doubt, it has a very robust, strong marketplace where we can directly integrate with existing APIs and begin working on those.

Microsoft Azure API Management is a secure solution.

It should be easier to integrate.

We are in the process of migrating from Amazon AWS to Microsoft Azure API Management. We are just getting started, we have been using it for a few weeks.

Microsoft Azure API Management is a stable solution.

Microsoft Azure API Management is definitely a scalable product.

It is not based on how many resources will be used, but we will be using three virtual machines from the Azure platform.

We plan to increase our usage.

We are Microsoft partners, MSP, and we have our own service providers to support this activity.

We use Google Workspaces and our platform is on Microsoft Azure.

Previously, we were using AWS EC2 Instances, but because we are a Microsoft MSP and also took into account the Active Directory capabilities and the Azure Marketplace, we decided to shift more to Azure.

The initial setup is more or less straightforward.

It took a couple of weeks to complete the entire migration from Amazon AWS to Microsoft Azure API Management.

Licensing fees are paid on an annual basis.

At the moment, we are not using CRM solutions but we are looking into Zoho CRM.

We had planned to use Salesforce, but we changed our minds and decided to use Zoho CRM instead.

I would recommend this solution to others who are interested in using it.

I would rate Azure API Management a nine out of ten.

Most of the features are valuable to me. We are actively exploring the monetization aspect of Azure, and we are also working on a proof of concept to accomplish this.

The only complication I encountered was configuring the authentication in the API Management. That was a little difficult for me, but it gets better after that.

I could that the UI could be improved. All services have the use of Visual Studio to do the coding and to change the configuration. It would be beneficial to include that with Microsoft Azure API Management.

I have been working with Microsoft Azure API Management for more than two years.

Microsoft Azure API Management is a stable product.

It is easy to scale Microsoft Azure API Management.

We have fast-track support from Microsoft, which we do receive.

We are satisfied with the technical support of Microsoft.

The initial setup was simple, with no complications, other than the configuration of the authentication in the API Management.

Since everyone is isocentric here, it is reasonable for me. Rather than getting complicated with other licensing, and other products' licensing. There are many, many different types of licensing available in other products, such as perpetual for ten users. If you want more than ten users, you'll have to pay a higher license fee. As a result, we are not falling into those kinds of traps. Previously, we had to pay as you go.

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

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.

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.

I use API Management for all of our AKS clusters.

API Management's price could be lower.

I've been using API Management for a year.

API Management is stable.

API Management is scalable based on the load.

API Management does not take long to deploy.

We used an in-house team.

I would rate API Management nine out of ten.

We have been using this solution to protect our APIs and to decouple our APIs between the host versus the outside world. It operates as a gateway pattern in front of the APIs.

We use this solution for API rate limiting and for its security features against DDoS.

The scalability of this solution could be improved. The volume which the API Management task service can handle needs to be improved. Cost wise, this solution could be optimized.

This is a stable solution.

This is not a scalable solution. 

The customer service and support for this solution is average. They have not been able to provide a solution to some of the challenges we have faced. 

Neutral

The initial setup is not complex as this is a PaaS-based solution.

This is an expensive solution. 

I would advise others to evaluate their volumes, nonfunctional requirements, and just check whether the NFR performance metrics of API Management has been met. Otherwise, better take a trade-off between, because we have gone through the hard path, tried everything using it, and then we have moved from API Management to Apigee.

I would rate this solution a seven out of ten. 

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.