Microsoft Azure API Management Reviews

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 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.

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.

The ability to easily connect back to Service Fabric is the most important for us.

The importing of existing APIs is extremely easy. It's one of the better products.

The main benefit is that we are already on ExpressRoute. It is easy to integrate into our local network. Because we are mostly a Microsoft shop, we mostly use Azure API management because we don't want to run in different cloud providers right now since we are a financial company.

Microsoft Azure API Management should have the ability to allow multitenancy.

While the solution works well for us, I would like to see simple or integrated reporting built into the solution.

There is always room for improvement.

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

Microsoft Azure API Management is extremely stable.

Microsoft Azure API Management is very easy to scale.

I don't have any prior experience. We haven't had any issues or needed to contact the product's technical support.

The initial setup is straightforward. It is very easy to set up.

Because everything is automated directly from our pipelines, maintenance is a very small task that we require.

It is very easy to deploy, and configure.

We are partners.

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

We use this solution to integrate with a third party with API integration.

So far, we are satisfied with the product. The stability and performance are good.

It is easy to install, and it scales well too.

The technical support is good, and we get prompt support.

It could be more user friendly for developers. It would be nice if developers could view things more easily.

I've been using this solution for nearly six months.

It's a cloud-based solution.

So far, there's good stability, and we have not had any issues with it.

Because it is on the Azure platform, it is always scalable and is easy to scale as well. If you want to use it more, then we can add more resources.

We started using Microsoft Azure API Management six months ago as a POC, and now it's online. We probably have about 30,000 users.

We hope to increase usage by moving all API onto API Management.

Microsoft's technical support is good. We have the premium support package, so we get support straight away. 

The initial setup is straightforward.

Because you need to define the API contract, initially it may take about two months. However, this is not due to the Microsoft product.

We had our internal consultant handle the implementation. We had a team including an integration engineer.

We pay for a yearly license.

I would recommend Microsoft Azure API Management and would rate it at eight on a scale from one to ten. 

We are in the healthcare industry, so all the applications which are related to one hospital, it binds to Microsoft Azure API Management, and this is our use case for it.

I like the integration function of Microsoft Azure API Management. Integration of this solution is easy.

There's some area for improvement for this solution's performance. Sometimes it can be challenging. We're working with design patents and we're hoping to see the performance issues sorted out.

We've been working with Microsoft Azure API Management for a year now.

Microsoft Azure API Management is a stable product, but we have not been able to test it yet on a multi-cloud environment.

Microsoft Azure API Management is scalable. There are no issues with its scalability.

Microsoft has a good technical support team. They are very helpful.

Integration of this solution is easy. I won't call it an initial setup. It's an integration.

I was able to work with Apigee.

We used Microsoft Azure API Management only in the Microsoft environment, but not in a multi-cloud environment.

Microsoft Azure API Management is cloud-based, in particular, it is a single cloud centered around Microsoft components and not on the Cross components.

I have no idea on how long it took to implement Microsoft Azure API Management. The testing and development team is the best resource on how long it took.

The number of users of this solution in the group I'm associated with is 300,000. Increasing the number of users will depend on the mergers and acquisitions, and how the group is doing.

For maintenance, we have a backend support team that handles application support. The major point is that if the API has a lot of issues, particularly in data silos, Microsoft Azure API Management has made it more convenient to manage those.

We're still trying and testing the integration function of this solution, and we're also trying to go deeper into its performance.

My rating for Microsoft Azure API Management is a nine out of ten.

I don't have any variance data with Apigee. Apigee is better than Microsoft. I have more numbers for Apigee compared to Microsoft.

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.

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.

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.

We have company-wide APIs which are hosted in Niger, and some of the external clients access the applications via the API, and we provide the post-data information. The clients get their data from our larger API.

The way the API management handles the calls and call throttling is excellent. 

The API management and the hosting of the API platform are great.

We haven't used API model that much, so I'm not in a good position to say recommendations as we are still exploring the Azure API management. We need more time to fully take in the solution before pointing our its flaws.

The documentation could be improved for the customer. The instructions on the district API and the initial stages of working with the solution need to be documented better so that users are more informed and they can have an improved experience.

I've been using the solution for three years now.

The stability of the solution is good. We haven't had any issues. I can't recall bugs or glitches. It doesn't crash or freeze. It's reliable.

The scalability of the solution is very good. If a company needs to expand it, it should be able to do so quite easily.

Currently, we have between 500-600 users in our organization on the solution.

We haven't really used technical support too often. Therefore, I can't really speak to their level of knowledge or responsiveness to issues.

We previously used IBM Open Shift. We switched due to the fact that the company was going to Azure and we didn't want multiple clients.

The initial setup isn't too difficult and doesn't take too long. You need to handle it to have the management gateway. Of course, every time it is deployed, then it needs to be configured to work with API. That could take some time.

For the deployment and maintenance, the size of the team you need depends on the project. We had a couple of developers on ours, for example.

I assisted with the implementation. I tend to handle it myself.

It's my understanding that the licensing is very clear. However, I'm not involved in it in any way, and therefore, I'm not sure what the cost structure is. 

We're just a customer. 

We do plan to continue to use the product going forward.

I'm not sure if I would recommend the solution. It depends on how their organization and architecture is, and if they're doing on-prem or cloud, depending on the requirement. It's very hard to say.

That said, I would rate it overall at eight out of ten.