Microsoft Azure Application Gateway Reviews

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.

We primarily use this solution to hide all of our applications behind the firewall. The application logic and dependencies are not known to the outside world because you don't have to open your external public IP to them.

It does not particularly improve functionality but you get the benefit of the security that is offered by Azure.

The Azure Application Gateway allows us to hide all of our backend components from our clients.

This is a SaaS product, so it is always up to date.

Once the gateway is configured, you can route all of your client requests based on the relevant part. For example, if somebody is asking to upload an image then a separate part will be called, whereas if they are asking to upload a video then it will be a different repository.

The documentation is not user-friendly and it is not very easy to use. For the first-time user, it is difficult to understand so the user-interface needs to be improved.

The tutorials are something that can be improved upon.

I would like to see this more of a multitenant solution.

I have been working with the Azure Application Gateway for almost 11 months.

It is a good service that is provided by the vendor and it is stable.

It is getting more scalable as more features are being added.

We have not been in contact with technical support for this solution.

We use Microsoft products for the majority of our applications and we are completely dependent on them. We did use another service prior to this one, which was an internal tool, but we switched to Azure because everything is being controlled by the vendor.

The configuration involves defining all of the routes. This is somewhat complex and is not easily understandable by just anyone. Our deployment took about 15 minutes.

We have an internal team for deployment and maintenance.

We did not evaluate other options before selecting the Azure Application Gateway.

My advice to anybody who is considering this solution is that it is not a must-have feature, but rather, a security service. If you're ready to bear the cost for security then you should implement the application gateway. 

This is a product that is in good shape.

I would rate this solution an eight out of ten.

Application Gateway is a tool service that provides high availability, redundancy, and load balancing for deployed applications on the cloud.

Application Gateway is cost-effective and has autoscaling. We can autoscale it.

The application gateway is good, but performance improvement in the containerization environment is needed. 

The traffic that relies on HTTP for a website is being manually configured to HTTPS. This process should be automated. If the protocol is HTTP, it should automatically redirect to HTTPS.

I have been using Microsoft Azure Application Gateway for one and a half years.

The stability is acceptable, but we are encountering issues configuring the container environment. Apart from that, the performance is satisfactory.

 I rate the solution’s stability as seven out of ten, but I rate it as nine out of ten for normal applications.

We have over three hundred customers, most of whom utilize Azure Application Gateway. Some are in the government sector, while others are in the private sector.

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

Microsoft's support is lacking. Their technical expertise seems insufficient, and when issues arise, the support personnel often request screenshots and provide only minimal information. Despite numerous emails and interactions with various technical support personnel, the initial support experience is subpar. The response is very fast, but they're not technical questions, as we need.

Positive

I rate the initial setup a ten out of ten for technical users and an eight out of ten for non-technical users. It's a one-time application. However, once configured, it becomes very easy to manage. Deployment takes 20-30 minutes, depending on the number of applications and servers we are configuring.

The product is cheap.

A WAF, a robust firewall solution, has been built into the Azure portal. Two models are available. The WAF is also integrated with the Application Gateway, providing comprehensive security for your cloud applications.

This security feature applies to traditional VM applications running on VMs and extends to autoscaling nodes in containerized environments.

The Microsoft Azure Application Gateway is a highly beneficial and flexible feature for facilitating the development of our applications and obtaining necessary certifications, thus sustaining our business operations. It offers scalability and high availability, which are crucial for meeting our growing needs. The Application Gateway serves as the sole solution for providing these capabilities, eliminating the need for developing such features in-house. It's an all-in-one solution that perfectly fulfills our requirements.

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

I use Microsoft Azure Application Gateway from a security perspective.

The most valuable feature of the solution stems from the fact that it is a comprehensive product, but it doesn't have too many API integrations.

The support provided for the solution has certain shortcomings that need improvement, especially when it comes to the response time from the support team.

I have been using Microsoft Azure Application Gateway for around three years. My company has a partnership with Microsoft.

My company's clients who use the solution have never reported any stability issues.

It is a scalable solution.

There are around 50 users of the solution in my company. The actual number of users of the solution may vary because we have a lot of our company's customers who use it.

My company deals with medium and enterprise-sized businesses that use Microsoft Azure Application Gateway.

The solution's technical support is good. I rate the technical support a nine out of ten.

Positive

The installation phase of Microsoft Azure Application Gateway is very easy.

The solution can be deployed in a couple of hours.

About five people from my company are needed to install and configure the solution.

The solution is deployed on a hybrid cloud.

Microsoft Azure Application Gateway is a pretty affordable product. My company needs to make yearly payments towards the licensing costs of the solution. The additional costs apart from the licensing costs of the solution vary.

Microsoft Azure Application Gateway is easy to maintain.

I recommend the solution to those who plan to use it since it is an extremely good platform.

I rate the overall product a nine out of ten.

We use Microsoft Azure Application Gateway for web applications and APIs.

So far, so good, but there are some capabilities we would like to investigate further, such as distributed denial of service (DDoS) and other similar features.

It does an excellent job of load balancing. The Application Gateway is performing load balancing, but we must decide whether to continue using the Gateway's firewall or to use another firewall. That's what we're looking at.

The increased security that we are considering is because of some of the things that the security team has brought to our attention. They have pointed out that we would most likely require a better web application firewall than Azure Application Gateway. That's the issue, that we are looking into.

I have been using Microsoft Azure Application Gateway for two years.

We are working with version two.

We have no issues with the stability of Microsoft Azure Application Gateway, so far it has been good.

Microsoft Azure Application Gateway is a scalable solution. We have not had any issues with scalability.

It's an external customer base.

The initial setup is straightforward. We do not have any issues with that, we are completely in control of Microsoft Azure Application Gateway.

We completed the deployment ourselves.

The cost is not an issue. It's not about finding a less expensive solution. It's about the additional costs we might incur if we with Cloudflare or another similar service provider.

We are not facing any additional costs. We must consider the additional costs that will be incurred if we choose a more advanced firewall.

I'm looking into web application firewalls and comparing Cloudflare with Azure's firewall. We are currently using Microsoft Azure Application Gateway and were considering the benefits and costs of upgrading to Cloudflare.

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

Microsoft Azure Application Gateway is used mainly for data transformation from on-premise to cloud or from cloud to on-premise. We are only using this solution extensively for web applications.

The most valuable features of Microsoft Azure Application Gateway are the policies, the data store they are using, and the cloud platform it operates on.

The solution could improve security.

In the next release, the solution could improve the integration with Service Mesh and other Azure Security Services.

I have been using Microsoft Azure Application Gateway for approximately two months.

We have approximately 50 users using this solution in my organization. They are developers and VDAs.

The support that they provide could be faster.

The implementation was done by our IT team of engineers and administrators.

There is some additional cost, such as extended support.

If you are a native Azure user, I would recommend this solution as long as you don't have any other security solution options.

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

We tried to integrate Microsoft Azure Application Gateway into our technology stack, but we realized that our service solution didn't see it at all during the integration. But I was played around with it for about two weeks to one month.

We were searching for a WAF solution which we could integrate into our stack and were using the management provided by the agent. We tried to integrate a vacation gateway controller, but we realized that the integration wasn't very good.

The most valuable feature is WAF.

It could be more stable, and support could be better. It would also be better if they offered more features. For example, it lacks security features. Before we used another English solution, and we realized that some of the rules were not set up correctly and passed through the Application Gateway's English controllers. But the problem, in this case, is if you send ten rules, for example, six rules hit some issues. 

IP address blocking could be better. The rules, for example, don't work properly. If you have one issue, one rule or another rule will not work. This sounds like total madness to me.

I used Microsoft Azure Application Gateway for about two weeks to a month.

We got the feeling that this product wasn't stable or good enough for us.

Microsoft technical support could be better. For example, when some rules were disabled and other rules couldn't be disabled, I contacted Microsoft Support. But I didn't get an answer until the next day.

The initial setup was very complex. I spent a lot of time just troubleshooting the backend and figuring out how to connect it correctly. It can take just minutes or hours to sort it by hand using the agent portal. But it took me several days to realize how to set up it using Terraform.

I installed and deployed this solution by myself.

On a scale from one to ten, I would give Microsoft Azure Application Gateway a five.