Microsoft Azure VPN Gateway Reviews

The solution is cloud-based on Azure and primarily used for VPN side-to-side connection. We don't care about the point set solution because we use another solution for that.

The side-to-side connections are valuable.

The solution can be improved by including a config map to separate some traffic from different bases on similar on-premise equipment that can offer this functionality.

We have been using the solution for approximately six years.

The solution is stable.

The solution is scalable, and approximately 500 users are currently utilizing the solution.

I rate my experience with customer service and support a seven out of ten.

Neutral

The initial setup and the documentation part are simple to use. But if we try to have a design for redundancy, it's a bit complicated to set up because we have some dependencies if we use on-premises to cloud interconnection. Deployment took approximately forty-five minutes.

I rate the solution a seven out of ten. The solution is good, but documentation and configuration settings can be improved. Nevertheless, I recommend the solution to users considering it.

The solution provides access to multiple applications and data. I use it for management, mainly to access platforms or as a bastion or management server. We are integrating the MFA into the VPN through Defender.

The solution is very quick to connect.

Microsoft could work on having micro VPNs to integrate with mobile devices.

I've used the solution for four or five years now and use the latest version.

The solution is very stable, and the performance is great. I've never had to complain about it. I rate the solution's stability a ten out of ten.

Microsoft Azure VPN Gateway is very scalable. Hundreds of users in my organization use the solution.

The initial setup is very straightforward. We don't need a lot of technical staff to deploy the solution.

We implemented the solution in-house.

The solution is subscription-based and very cheap.

I rate Microsoft Azure VPN Gateway a ten out of ten. Users should only use the solution for its main use case and other solutions for user access.

Microsoft Azure VPN Gateway is used to connect our data center to our cloud deployments, or at least some of them.

API Management, Stream Analytics, and Azure Analytics are tools in the toolkit that help to make Azure more transparent. I mostly work with virtual machines, enterprise applications, and Azure DevOps.

VPN Gateway, among many others we use. We deploy our own enterprise apps, of course, we use them.

The interoperability with various firewall and access gateway vendors is one of this solution's most valuable features.

In the past, reliability has not been great. Deployment has not been simple. Getting it to run is a difficult process.

With one being the easiest experience and five being the most difficult, I would give the deployment process a three and a half out of five.

Make it completely routable, for example, if I have a gateway, I should be able to connect to whatever network I want on either side of the gateway, and the gateway should figure out which packet goes where. 

This is a traditional firewall or network gateway administration that has been removed from the Azure VPN and Gateway functionality, which should just put it back where it belongs, because as it is now if you have three networks, three different networks on either side of Azure, you have to configure one gateway per network.

As a principal cloud architect, I am working with Azure.

We first deployed Microsoft Azure VPN Gateway in July 2019. We have been working with it for three years.

We are working with the most current version.

The stability of the Microsoft Azure VPN Gateway could be improved.

It could be better than it is right now.

I have been using open-source VPN appliances for the same purpose and they have fared quite a bit better than the Azure solution.

I'm not sure how many people are using this solution in our organization, because we don't keep track of individual users accessing our Azure cloud infrastructure. It is used as an extension to our data center in this case. I'm not sure if every user on our network is using it, or if they are not.

It's similar to a cable. You have no idea how many people send traffic over a cable.

We have no plans to increase our usage in the future.

There is technical support available, but the response time could be improved.

If one is the worst and five is the best, I would rate the technical support a three out of five.

Previously, we did not use another solution.

The deployment is not straightforward. It is a lot more complicated than you would expect it to be.

Because of the communication with the service provider, they needed to get their firewall management in order. The deployment took four hours over two days.

It is overly complicated, in my opinion. The networking restrictions make it difficult to use it for everything in Azure. You can only have one gateway active at a time, which is an annoyance.

For our firewall and VPN gateway infrastructure, we use a managed service provider. I installed the Azure component myself and had the service provider install the component on our firewalls.

I am not aware of the licensing fees.

My advice is to only use it if absolutely necessary. If you have the option, don't.

I would rate Microsoft Azure VPN Gateway a four out of ten. It works, but it's not fun to use, and it's not universally usable, contrary to what they claim on the website.

We use 365 accounts for Outlook and Azure. We use it for data protection.

It sends us a lot of detections when we have any anti-virus updates. It provides the extended time needed to update a set of time needs and notifications. 

The marketing material in the portal is not very user-friendly. We faced some issues when trying to run a campaign. It was not opening. Some campaigns open directly on Outlook and others in Word documents. There should be one single framework, either Outlook or Word.

I have been using Microsoft Azure for the past ten to twelve years. 

It is a highly scalable solution. More than twenty people use this solution.

The technical support team is simple and helpful. 

Microsoft's portal is vast and the initial setup is straightforward. 

I rate the overall solution a nine out of ten. 

I am using Microsoft Azure VPN Gateway to connect to my client. We use it to securely connect to other systems.

I have been using Microsoft Azure VPN Gateway for more than three years.

All of our offices are using Microsoft Azure VPN Gateway. The solution is scalable.

We have a Microsoft partner that gives us support for the solution.

I did not use other solutions previously.

Microsoft Azure VPN Gateway is already configured on my laptop, I only need to double click a button, enter my login information, and it connects.

There is a monthly license and the price depends on how many users are using Microsoft Azure VPN Gateway. The price could be less expensive.

I would recommend this solution to others.

I rate Microsoft Azure VPN Gateway a nine out of ten.

The best feature is the ability to connect from anywhere.

The cost could be lower. In the next release, Microsoft should add an option to schedule upgrades.

I've been working with this solution for nearly six years.

Azure VPN Gateway is stable.

Azure VPN Gateway is a simple VPN, and it works. I would rate it as eight out of ten.

The most valuable feature is the networking. I didn't have a good experience with the networking that Sophos has.

I would like for them to improve the troubleshooting features. We have some problems with traffic and I can't identify where the problem is coming from. I have to open a ticket with support until it gets resolved. Microsoft doesn't offer enough tools to resolve the issue. 

I have been using Microsoft Azure VPN Gateway for three to four years. 

Stability depends. Sometimes I need to change the VPN Gateway for another tool like Palo Alto or Checkpoint because Microsoft isn't always so consistent. 

It is scalable. 

I don't have any problems with technical support. They're very good. The problem is the platform doesn't have enough tools to resolve problems but if you contact support, they have the ability to resolve anything. 

On-premise, I worked with other tools but my principal work is with Azure. I worked with Cisco ASA and Fortinet. I studied Cisco but I didn't work with it in an actual environment.

The initial setup is very easy. It's not difficult. 

I would rate it a seven out of ten. 

It's simple to deploy, it's faster than other platforms, and it's scalable which is an important advantage. 

In the next release, I would like to see more troubleshooting tools. I would also like to see the connection to remain consistent. 

We have servers in Azure, and we use it to connect the on-premises users to the cloud servers.

It is a site-to-site VPN deployed on our premise.

I'm using the high availability of the VPN. We are using the VPN Gateway with two different internet service providers on-premises. We are using high availability so that in case one of the internet services fails, we can get Azure to assist using the other service.

It works perfectly for me. It is very user-friendly in terms of the configuration and the setup process.

Their technical support could be better. If you don't have a support contract, it takes longer.

I have been using this solution for three years.

It is very stable.

It is easy to scale. We started with a basic plan, and we can move to another plan that has more bandwidth and more features. It is possible to do that.

It depends. If you have a technical support contract with Microsoft, it is very easy. If you don't have it, it takes longer.

It is easy to set up. The deployment process is very quick. It takes 20 to 30 minutes to set up a site-to-site VPN.

I would definitely recommend this solution because it is very easy to deploy and very stable. It is very simple. It is only a VPN connection. It works for what it is made.

I would rate Microsoft Azure VPN Gateway a 10 out of 10.