We just raised a $30M Series A: Read our story

Microsoft Azure API Management OverviewUNIXBusinessApplication

Microsoft Azure API Management is #2 ranked solution in top API Management tools. IT Central Station users give Microsoft Azure API Management an average rating of 8 out of 10. Microsoft Azure API Management is most commonly compared to Apigee:Microsoft Azure API Management vs Apigee. Microsoft Azure API Management is popular among the large enterprise segment, accounting for 66% of users researching this solution on IT Central Station. The top industry researching this solution are professionals from a computer software company, accounting for 29% of all views.
What is Microsoft Azure API Management?
Microsoft Azure API Management ensures an organization's API program reaches its fullest potential. With API management, organizations can publish web services as APIs reliably, securely and at scale. Use API Management to drive API consumption among internal teams, partners, and developers while benefiting from business and operational insights available in the admin portal.

Microsoft Azure API Management was previously known as Azure API Management, MS Azure API Management.

Microsoft Azure API Management Buyer's Guide

Download the Microsoft Azure API Management Buyer's Guide including reviews and more. Updated: November 2021

Microsoft Azure API Management Customers
adnymics GmbH, LG CNS, Centrebet, netfabb GmbH, MedPlast, Accelera Solutions, Sochi Organizing Committee, realzeit GmbH, Opensistemas
Microsoft Azure API Management Video

Archived Microsoft Azure API Management Reviews (more than two years old)

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
LS
Chief Technical Lead at a tech vendor with 201-500 employees
Real User
Very easy to set up a new solution and to deploy it to production

Pros and Cons

  • "The ease of setting up a new solution is the most valuable feature. It's very easy to set up a new solution and to deploy it to production."
  • "The developer console for external users could be improved, especially in the testing site."

What is our primary use case?

We use the cloud model. Our primary use case is for integration between different systems. There are many use cases for the API management tool, but the most common scenario is integration between different systems.

What is most valuable?

The ease of setting up a new solution is the most valuable feature. It's very easy to set up a new solution and to deploy it to production.

What needs improvement?

The developer console for external users could be improved, especially in the testing site. I would like to see the security management for the APIs to be more granular.

For how long have I used the solution?

I have been using this solution for a year and a half.

What do I think about the stability of the solution?

It is very stable.

What do I think about the scalability of the solution?

It's quite scalable. We've tested it in different little scenarios and it's quite scalable.

For deployment, I would advise a specialist. There is no need to dedicate any staff to the maintenance of the solution.

How are customer service and technical support?

I would rate their technical support an eight out of ten. It could use a bit of improvement. 

Which solution did I use previously and why did I switch?

I previously used RabbitMQ for another project. Both solutions have different approaches. One can work on-premises. On the whole, I still prefer is Azure API Management. I believe it's an easier solution set up and run.

How was the initial setup?

The initial setup was very straightforward and simple. The deployment only took a few hours. 

What about the implementation team?

I deployed the solution myself. 

What other advice do I have?

I would recommend this solution to someone considering it. I would rate it a nine out of ten. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
it_user692298
Business Integration Architect & managing partner at a tech services company
Consultant
Policies allow us to control and enrich the API behavior without code changes.

Pros and Cons

  • "Monitoring: It gives us a detailed overview of how clients are using the API and it allows us to see the consumption trends in real-time."
  • "The documentation and configuration of APIs."
  • "There were no scalability issues."
  • "Security could be improved."

What is most valuable?

  • Monitoring: It gives us a detailed overview of how clients are using the API and it allows us to see the consumption trends in real-time.
  • Policies: It allows us to control and enrich the API behavior without the need to make code changes
  • The documentation and configuration of APIs.

How has it helped my organization?

Internally, we use this product to give our employees a catalog of all the APIs that we implemented over the years. They get detailed documentation on how to use those APIs and can develop their own solutions on top.

What needs improvement?

Security could be improved.

For how long have I used the solution?

I have used this solution for a year.

What do I think about the stability of the solution?

There were no stability issues.

What do I think about the scalability of the solution?

There were no scalability issues.

How is customer service and technical support?

I would give the technical support team a rating of eight out of 10 .

How was the initial setup?

The setup was straightforward, setting up a basic API management portal is only a few clicks in the Azure Portal. Once it is set up, the APIs can directly be added by just importing the Swagger file.

What's my experience with pricing, setup cost, and licensing?

The developer and standard pricing tiers of Azure API Management are very competitive compared to other products. If a customer wants to expose their internal APIs to the Azure API Management Portal, then they would require a VPN connection which requires the Premium Pricing tier. This can be expensive and we currently recommend our customers to not use a VPN connection, i.e., if they don’t need additional Premium features; and we suggest they expose their APIs publicly through other technologies such as the relay services.

What other advice do I have?

Learn how policies work since this is where the real added value of Azure API Management is.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Learn what your peers think about Microsoft Azure API Management. Get advice and tips from experienced pros sharing their opinions. Updated: November 2021.
554,676 professionals have used our research since 2012.
ITCS user
Sr Software Architect at a tech services company with 501-1,000 employees
Consultant
It offers API gateway features and AD integration. An IaaS option should also be offered.

What is most valuable?

  • API gateway features
  • AD integration
  • Access management capabilities
  • Usage plans
  • Quotas for APIs, etc.

How has it helped my organization?

It is a simple and effective way to enable micro-services architecture. The Standard Tier is cost effective.

What needs improvement?

  • An IaaS option is needed. The SaaS option limited our requirement, as we wanted more control on our data, and integration with our virtual LAN. Integration with our VLAN was possible only with the premium version and expensive gateway controllers.
  • PCI compliance

For how long have I used the solution?

I evaluated it for one month.

What do I think about the stability of the solution?

I have not encountered any stability issues.

What do I think about the scalability of the solution?

I have not encountered any scalability issues.

How are customer service and technical support?

Technical support is 7/10.

Which solution did I use previously and why did I switch?

I did not previously use a different solution. However, I evaluated other API gateways and shortlisted ForgeRock - OpenAM/OpenIG, because it has an IaaS option.

How was the initial setup?

Initial setup was fairly straightforward; excellent documentation.

What's my experience with pricing, setup cost, and licensing?

The Standard Tier is cost effective.

Which other solutions did I evaluate?

Before choosing this product, I evaluated NGINX, Apigee, and ForgeRock (OpenAM/OpenIG).

What other advice do I have?

Code impact: Required services to import Swagger library.

Being SaaS, if you are running services on IaaS, communication between APIM and your services will be through the public internet (if that’s a cause of concern).

APIM was available in classic mode only (as of April 2016). Our infrastructure was ARM. Connectivity was complex and expensive.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
it_user208704
Senior .Net Developer at a university with 51-200 employees
Vendor
It's easy to setup and have something going within an hour but configuration exporting from the Admin portal needs work.

What is most valuable?

The ability to manage user access to given API operations.

  • Visibility on user usage analytics
  • Set policies across API operations, which control the type of access (CORS, JSONP)
  • The ability to piece together an array of services into one proxied service. Where I can create consistency to both usage and documentation

How has it helped my organization?

We were securely able to offer services to external third parties to securely consume within a relatively short amount of time.

What needs improvement?

  • Versioning of API operations (which I have heard is in the pipeline)
  • Easy exporting of configurations from the Administrator portal.

For how long have I used the solution?

I've used it for around six months or so.

What was my experience with deployment of the solution?

I did follow the prescribed steps to export our Test subscription setup to import into a production subscription environment, but I was unable to achieve the export within the short amount of time I had to achieve it. So to get around the issue, I just manually configured it in the production environment as part of the release.

What do I think about the stability of the solution?

No issues encountered.

What do I think about the scalability of the solution?

No issues encountered.

How are customer service and technical support?

Customer Service:

Didn't use them.

Technical Support:

10/10, as our Microsoft account manager arranged direct contact with members of the API Management Team.

Which solution did I use previously and why did I switch?

No previous solution used.

How was the initial setup?

Pretty easy. The online documentation is very thorough.

What about the implementation team?

In-house implementation.

What was our ROI?

The product probably saved us at least two to four sprints worth of extra work, which would not have achieved the quality, which this PAS provides us, out of the box.

What's my experience with pricing, setup cost, and licensing?

Nothing. Day to Day costs are very minimal, tens of dollars a month or so depending on peaks of usage.

Which other solutions did I evaluate?

No. I was evaluating Azure PAS offerings and producing proof of concept solutions just before the project kicked off.

What other advice do I have?

Definitely check it out. The documentation is plentiful and it is pretty easy to setup and have something going within an hour or so.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Product Categories
API Management
Buyer's Guide
Download our free Microsoft Azure API Management Report and get advice and tips from experienced pros sharing their opinions.