Microsoft Azure Application Gateway Reviews

Azure Application Gateway is used on an AKS cluster. We don't want to expose the control plane to the public IP. We created a control plane with a private IP and then put an Application Gateway in front of it. Users can access the AKS cluster through the Application Gateway. The Application Gateway filters traffic to the AKS cluster.

If you don't want to use public IPs and expose your enterprise externally to the public world, and you want strict authorization, you should use Azure Application Gateway.

The login mechanism could be improved.

I have been using Microsoft Azure Application Gateway for a few months.

I rate the solution’s stability a seven out of ten.

The solution is scalable.

Microsoft Azure Application Gateway is an internal application that allows people to access it. We have 100s of different users working on it who can access it with their logins. We do not need to set up any database mechanism to add users.

Microsoft Support is good.

The initial setup of Azure Application Gateway is straightforward, provided you have a good understanding of networking concepts and have everything ready.

For deployment, the gateway is already available. It offers maximum protection and everything else.

If you want to build an application with standard authorization and a simple route within the organization instead of multiple routes, then Azure Application Gateway is a good option.

Overall, I rate the solution an eight out of ten.

The solution's most valuable feature is an HTTP solution and SSL certificate. It is also easy to use.  

Microsoft Azure Application Gateway's first deployment is complex. It needs to improve its pricing. 

Microsoft Azure Application Gateway is stable. 

The solution is scalable. My company has two projects that use it. 

The tool's deployment takes one week to complete. 

The tool's pricing model is pay-as-you-go. 

Microsoft Azure Application Gateway is a useful solution. I rate it a seven out of ten. 

We are using Microsoft Azure Application Gateway which hosted our domain as a load balancer. We have an application visible to the public and the traffic passes through this solution.

The most valuable feature of the solution is traffic management.

The solution could improve by increasing the performance when doing updates. For example, if I change the certificate it can take 30 minutes. Other vendors do not have this type of problem.

I have been using Microsoft Azure Application Gateway for approximately three years.

We have had some issues with the stability.

I rate the stability of Microsoft Azure Application Gateway a three out of ten.

We have approximately 600 requests from one balancer and a total of 3,000 requests.

I rate the scalability of Microsoft Azure Application Gateway a three out of ten.

I rate support from Microsoft Azure Application Gateway a four out of ten.

Neutral

I have used a solution prior to  Microsoft Azure Application Gateway.

The implementation of the solution was complex, it took a few hours to complete.

I rate the initial setup of  Microsoft Azure Application Gateway a three out of ten.

The solution is paid monthly. The solution is highly expensive.

I would not recommend this solution.

I rate Microsoft Azure Application Gateway a four out of ten.

We use the solution for isolation and load balancing.

The solution offers the ability to scale the bandwidth in real-time and observability.

The product should improve its cost-to-performance ratio.

I have been using Microsoft Azure Application Gateway for 18 months.

I rate the solution’s stability a ten out of ten.

I rate the solution’s scalability a ten out of ten.

All Azure services have the same support. There is no specific support. There is a similar team for all components and tickets. They need to do a much better job. The quality and speed of support should be improved.

Neutral

The initial setup takes a few minutes.

I rate the initial setup a seven out of ten, where one is difficult and ten is easy.

The product is expensive.

I advise other users to monitor their usage and not build unnecessary gateways.

Overall, I rate the solution a seven out of ten.

I like the tool's stability and performance. 

I want the solution's support to improve. The tool is also expensive. 

I don't find the solution to be stable. 

I have had issues with the customer service's responses. I want the support to be more quicker. 

The tool's setup is straightforward.  

I would rate the product an eight out of ten. 

It is for securing traffic. It provides security against OWASP Top 10 vulnerabilities, so there is a V2 WAF App gateway. 

This product works well to secure my public facing websites from things like sql injections

The health probe is pretty good for your backend health. It tells you whether it's communicating and talking to the endpoint correctly. It is quite useful.

It is a bit tricky to configure in the UI. You've got to configure front end back end ports ips and the  map the listeners & rules for single or multi sites to configure it. They should make it a little bit easier to configure a pre-defined configuration Mapping the certificates from key vault. I think this would make app-gateway much better although it is a very good secure product. Automating this end to end takes a bit of of time to work out but once its done its very secure.

I used it within the last six months. 

Its stability is pretty good. I've had it running now for about six months. 

It scales pretty well. Its availability seems pretty good. As long as you set the metrics right, it will scale efficiently.

Their support is all right. Microsoft's support has covered it pretty well. I would rate them a four out of five.

It is a bit tricky to configure, but once you do it, it is all right. Its configuration is a bit tricky in terms of getting the rules right. You got to get the rules right, and you got to get the endpoints right. The backend is easy enough to configure, but you need to get the rules right. 

The mapping of the certificate got to be done in a very specific way for it to work. Once the certificate is there, pulling that certificate is easy enough, but you've got to map it manually because the configuration settings are quite tricky to do. You've to basically do it in the UI. I've had to do that a couple of times, so I've got it perfect in automation.

I would advise going for OWASP Top 10 filtering. It is a must-have for V2 WAF security.

Overall, I'd rate it an eight out of ten. It is a good product, and once you get it configured, it does work well.

We are using it for application load balancing and scaling.

It has a filter available, although we are not currently using it because it is not part of our requirements. But it is a good option and when it becomes part of our requirements we will definitely use it. 

It takes a lot of time for a certificate to update in the system. That is a huge drawback, affecting the load-balancing side. And when there are changes to the load balancing, it affects the end-user.

I have been using Microsoft Azure Application for the last six months.

I think the scalability is okay, but I haven't tried to scale it.

Application Gateway is tied into our applications. We have about 5,000 connections into Application Gateway, on average. There are around 800 to 900 requests per minute.

I have not had to contact Microsoft tech support about Azure Application Gateway.

Previously, we were in AWS. We just migrated to Azure. 

The initial setup is straightforward. If you compare it with AWS, it's a little bit complicated, but overall, the technical aspects are very simple.

A normal Application Gateway deployment takes around 20 to 25 minutes, but again, the application of certificate changes takes around 20 to 25 minutes, so the total time involved is about one hour.

We did not use a third-party. Currently, I'm the only person handling the solution in our company. My main task in Application Gateway is configuration, as it's a service that is provided by Azure. There is not much more for me to do than configure it.

Between v1 and v2, there is a lot of change in the pricing. It is very costly compared to AWS. Our main implementation strategy is based around the pricing. If there are any technical features that we need to consider in addition, we will. If the prices for those additional features are okay then we will use them.

The features in both AWS and Azure seem to be comparable. We are enabling all the security features that were available in AWS. 

From my few months of experience with Azure, the configuration changes we are making in Application Gateway, such as a certificate change, are taking more time to apply to the service. In AWS it was very quick. It would take less than one minute, but here it takes almost 10 minutes to apply that certificate. That time difference is huge. That is the only drawback or issue that I have faced with the Azure Application Gateway. 

Other than that, the two services look the same.

There are two versions of Application Gateway. Version 2 is a seven out of 10. I would rate version 1 at three to four out of 10.

We use the solution for Internet traffic load balancing and internet traffic routing via proxies to our internal applications. It is not for user connectivity but more for the system to system integration as an application gateway.

Some of the key features of this solution are the low-level maintenance required, floating proxy service, and load balancing.

One of the challenges we faced was the solution does not support any other PCP protocols apart from HTTP and HTTPS. We had some requirement for load balancing that it did not support SAP, they should provide support for more protocols.

I have been using the solution for approximately one year.

The solution is very stable for us at the moment but I think we need more experience in the future to come to a more exact determination on the stability.

We have no problem with the scalability of the solution.

The installation is quite simple.

We have a cloud technical team that does the deployment and maintenance of the solution.

Every solution comes with a license and cost. Microsoft provides the license and the total cost is for the maintenance every year. 

We plan to keep using the solution in the future and I would recommend it to others.

I rate Microsoft Azure Application Gateway an eight out of ten.