Microsoft Azure Application Gateway Reviews

We are regular users of Azure Application Gateway. It is a very cost efficient option for customers and it has its own advantages. However, when there are urgent concerns regarding security I recommend utilising the web application firewall for its enhanced features and configuration options since Azure lacks functionalities and has its own limitations when handling suspicious requests. 

Usually, there is a recommendation from Microsoft about integrating Azure Application Gateway with other services like Monitor and Sentinel, so that there is seamless log forwarding and rule management. However, other options involve much more extensive configuration and scripting. In my experience, Microsoft products have a smooth integration and facilitate easy management and monitoring. Using Azure Application Gateway allows us to efficiently handle the system loads.

There is a recent feature called Application Policies which has been available. This policy allows us to enable or disable specific security signatures or features related to backend operations. According to the manual provided by Microsoft, this feature is very flexible in managing security and strategies for maintenance. However, in our experience, we have found that modifying these policies has a tremendous impact on the functionality of the application gateway. While it is necessary to adjust the settings, it should be a process of caution since these rules could potentially expose applications to security risks.

Multiple options exist to configure the number of instances and scale responses based on load increases. However, I believe that there is room for improvement in terms of additional functionality. It is an advantage to have features readily available for configuration without needing customer-defined rules. This feature is already available in products like Barracuda and would be great if they are included in the future versions of Application Gateway.

I have been working with Microsoft Azure Application Gateway for the past two years. 

I would rate the stability a six out of ten because there are some malicious requests. 

I would rate the scalability a ten out of ten.

Sometimes, technical support may require escalation to higher-level experts, particularly when dealing with complex issues. 

I would rate the initial setup a seven out of ten, since it is simple and does not take a lot of time. 

I would rate the pricing a seven out of ten.

I would rate the integration with other applications a nine out of ten. Overall, I would rate the solution a seven out of ten. 

The solution is being used from warehouse to production. In short, for everything. 

The production is a valuable feature. 

The working speed of the solution needs improvement. 

I have been using Microsoft Azure Application Gateway for quite some time. 

The solution is mostly stable. 

It is a scalable solution.

For the initial setup, I would rate it five or six. 

The deployment takes eight months. 

I would rate the overall solution an eight 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 the product in front-end and back-end applications to do the load balancing smartly. 

The product's performance should be better. 

I have been using the solution for one year. 

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

The tool's scalability is good. My company has 500 users for the solution. 

Microsoft Azure Application Gateway's support could be faster. 

Microsoft Azure Application Gateway's setup is neither complex nor easy. 

Microsoft Azure Application Gateway is expensive. 

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

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.