Microsoft Azure Application Gateway Review

Secures our internal applications and hides them from outside connections

What is our primary use case?

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.

How has it helped my organization?

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

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

How are customer service and technical support?

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

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

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.

How was the initial setup?

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.

What about the implementation team?

We have an internal team for deployment and maintenance.

Which other solutions did I evaluate?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
**Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
More Microsoft Azure Application Gateway reviews from users
Add a Comment