Microsoft Azure Application Gateway Reviews

The solution has a variety of different features that are all excellent.

The simplicity of the solution and its ability to integrate easily with others are its most valuable aspects.

The pricing of the solution could be improved. Right now, it's a bit expensive.

Although the integration is quite good, it could still be improved upon.

The implementation should be further simplified to make it easier to use right from the onset.

I believe I have been using the solution for about a year and a half now.

The solution is quite stable. We didn't run into any bugs. There haven't been glitches or crashes. We find it to be quite reliable.

The solution is scalable. If a company needs to expand it out, they can do so quite easily.

Currently, our company has about 100 employees on it regularly. They are both users and developers. It's a mix of people.

We've been in touch with technical support and have been satisfied with the level of assistance they have been able to provide to our team so far.

We didn't previously use a different platform. This is the first solution we have implemented.

The solution has a quite simple initial setup. We didn't find it to be overly complex.

The solution is expensive.

We don't have a business relationship with the solution. We are only customers.

I'm not sure which version of the solution we're currently using.

I would recommend to other companies considering the solution to run through a proof of concept first. Everyone's needs are different, so it's important to make sure the solutions you choose are able to meet them effectively. That way, you'll be able to know if the solution will work for your company and if it makes sense to implement it or not.

I'd rate the solution nine out of ten.

The gateway is used to make the application connect to the internet and apply some firewall rules on Layer 7. We primarily use Azure Gateway for printers, some requests, and to apply some security rules to all the traffic that is coming from inside the Azure network. 

We chose this solution in the first place because it has access to Layer 7. I can control the requests and the content, which I can access on my network if I want to even if it's forbidden access to other external resources. If I want to monitor, for example, traffic, and apply this rule on Layer 7, I can do so. This was our main goal when implementing this application. We wanted to take advantage of the Gateway capabilities.

The pricing of the solution is a bit high. The solution should offer different pricing systems.

The solution is stable. We've never faced any stability problems while using it.

While I believe the option to scale exists on Azure, we have never needed to scale. I can't speak to how scalable it actually is. We've had two projects on Azure and we have had as many as 5,000 users on the solution with no problem.

We've never had to deal with technical support, as I don't really use any deep technical items on the solution.

Compared to other public clouds, the price is fairly high. I'm not sure if the pricing model has changed, but I recall it being slightly more expensive.

We are using the public cloud deployment model. We are both a customer and a reseller, but I myself have worked with Azure mainly as a customer.

I would rate the solution eight out of ten.