Microsoft Azure VPN Gateway Reviews

We use the solution to develop systems for financial institutions.

The Azure tool is useful and powerful and availability for clients. The updates are very good and reliable.

The connectivity should be faster.

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

The solution’s stability is good.

The solution’s scalability is good. I have used it for two to three months, but that is insufficient time to decide.

Our team did the setup. There were 50+ technical staff for the deployment.

Overall, I rate the solution an eight out of ten.

We have some regions for our virtual machines. Instead of using the tiering in some regions, we are using the VPN gateways to connect these things. We can have an express gateway between that and one of the regions that we are using our virtual machines.

There are 10 to 15 people using this solution in my organization.

The solution is cloud-based. We're using the latest version.

The performance is good.

The stability could be improved. The setup is a little bit complex. In the next release, I would like to see a new setup process.

I would like the solution to be more simple. If it were simple, we could remove other solutions, like tiering, and move to VPN for all of our requirements. VPN is much better to use because tiering is non-reciprocal, so we have to make a connection between the two endpoints.

I have been using this solution for more than six months.

We had some issues with the stability. 

It's easy to scale out the virtual machines. There are scale sets.

The setup isn't difficult, but sometimes it's complicated to bridge between the connection and the end points that you want to connect. We have VPN gateways. Sometimes it's better to use the tiering because it's more simple than VPN gateways.

The price is good. I would rate it five out of five.

We also evaluated AWS. It's a more straightforward solution and the networking is better, but the price policy in Azure is much better. 

AWS has more pricing policies, but Azure provides them freely.

I would rate this solution six out of ten.

I would recommend this solution to another user.

The product has valuable virtual machines, viability options, and enhanced VPN services, enabling the option to use it in different zones.

More configuration options could be included in Microsoft Azure VPN Gateway.

We have been using Microsoft Azure VPN Gateway for four years.

I rate the platform's stability an eight out of ten.

We have 100 Microsoft Azure VPN Gateway users in our organization. I rate the scalability a nine out of ten.

The technical support team is responsive and helpful.

Positive

I was working with AWS before. I decided to switch to Azure for easy configuration and good documentation services.

The initial setup is easy for me as I have been working with the product for a long time. I can conduct the troubleshooting myself. However, I reach out to the Microsoft support team in case of difficult scenarios.

I rate the process an eight out of ten.

The software has good pricing compared to other vendors. We have to pay extra to buy additional services.

The platform has good stability and an easy configuration process. I rate it a nine out of ten.

We are currently utilizing the solution in our organization to establish connectivity with our on-premise network to manage and monitor the traffic flow. However, we have plans to replace this solution with the XPLUS Routing System soon.

I appreciate that the solution is accessible via the cloud and offers scalable services as a platform. Additionally, any work we do in the cloud is automatically integrated with Microsoft's monitoring capabilities, which is a great feature.

Considering my use cases, I can fulfill my requirements using the product. The existing requirements of my company are pretty simple, and I think this product can meet those requirements.

The solution's pricing will always remain a challenge since anyone would want to get the solution at the lowest possible price.

I would like Microsoft to improve the pricing of the solution. Also, the technical support team could be more knowledgeable.

I have been using Microsoft Azure VPN Gateway in my organization for a year and a half. Also, I am using the solution's latest version.

It is a stable solution in our company, and we monitor critical health and performance parameters daily and weekly. Once we have more workload in the coming years, we will know if there are any additional challenges.

It is a scalable solution. From a scalability perspective, it meets the requirements of our organization. So, we use this VPN as a site-to-site rather than a point-to-site VPN. The site-to-site VPN is set up in almost five locations at this point in time.

My organization has contacted the technical support team of Microsoft. Considering my past interactions with Microsoft's support team, it is difficult to get the right support unless you find the right person to speak with from the customer support team. So finding that person may take some time more than you expect. The technical support person is reachable. There is no problem with reaching out to the support team. But that doesn't mean that the person you are talking to may be the most knowledgeable or the one with the right knowledge to resolve your issues. From technical support, getting the right person to resolve your issues can be tricky.

The solution's initial setup process was easy. Also, at the same time, one can consider provisioning the resources using the code, which makes the solution even better since, otherwise, it would not have been possible using an on-premise tool.

Regarding the deployment process, our Azure architect team designed it, first of all, including a part of the networking design. Then, with our engineering team, we got the coding done for that using Azure Bicep. After this step, we tested it in the sandbox environment. After successfully testing the sandbox environment, we could deploy the solution using Azure Pipelines and DevOps Pipelines for actual provisioning in production.

I wouldn't say that there is a dedicated team for the deployment and maintenance of the solution since this solution is a part of the overall project. So, the network architect designed everything from the firewall to the subnets. Also, the network architect was responsible for designing the overall networking structure. Moreover, the network architect was also involved in the design of the VPN. Then, there's the engineering team with only one engineer working on the infrastructure of the code, and he did the coding from a design perspective. Since some testing and other activities were done along with the part managed by the engineer, two more resources probably contributed to helping the engineer.

Considering the solution functioning on the cloud, it is absolutely worth the money. In our company, we are in the beginning phase of moving the solution to the cloud, so many things need to be migrated. I got the opportunity to use the VPN device, probably when we initially experimented with Azure. We are going live with Azure, and it has only been six months now. We expect that in the next three years, a lot of workloads will move to the cloud. On the cloud, testing and other activities become much easier, especially considering the new technologies and functions that Microsoft is introducing.

Payment for licensing the solution is part of the operating model. So, one needs to keep on paying while consuming the solution. In short, the payment is based on the solution's capacity.

The Azure platform is a very good service in general. However, certain challenges need to be considered, particularly regarding pricing.

I would say that with a traditional mindset where we are used to having complete control on-premise, it can be a little difficult to digest at first that someone else is managing your infrastructure, and you don't know where it is located. However, once you start treating it as a consumption service like electricity, I believe it is a great service. I rate the overall solution an eight or nine out of ten.

The solution is used for site-to-site and point-to-site connectivity.

The solution is user-friendly. We need not worry about the connections once we deploy the tool. We just enter the public IP and make the connection.

The solution should provide metrics to monitor the inbound and outbound traffic easily. The point-to-site connections must be improved.

The product is pretty stable.

Traditional network tools that we have on-premises handle all our needs. However, Microsoft Azure VPN Gateway handles only site-to-site and point-to-site connectivity. For additional needs, we must use Azure Firewall.

We must have a premium support contract with Microsoft if we need a proper team to assist us. If we open a ticket without premium support, we might get support from an outsourced support team. It will not be helpful. Support depends on the contract we purchase. Azure’s support must improve a lot. When we raise a ticket with other vendors, they see our device and configuration, verify it, and tell us what to do.

Azure’s support is quite delayed. After the ticket is opened, the engineer takes the screenshots and the logs and returns after three days. It is not feasible in a production environment. Microsoft recommends taking premium support to get on-the-spot help. Customers can choose the support according to their needs. I rate the premium support a ten out of ten, but I rate the basic outsourced support team a three out of ten. Overall, I rate the support a six to seven out of ten.

Neutral

The deployment takes 45 minutes. The setup is straightforward. We can find detailed articles on Azure. I rate the ease of setup a nine out of ten.

The product costs us $140 to $180 per month.

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

I use Microsoft Azure VPN Gateway to connect the remote site via the local network to the front-end site or any other cloud or network.

What I like best about Microsoft Azure VPN Gateway is that it's a managed VPN, so it's one of the most powerful VPNs I've ever found. You can run the solution within thirty to forty-five minutes, and then, once data is configured, you can easily configure multiple tenants.

Microsoft Azure VPN Gateway also provides point-to-site VPNs configurable within a few minutes. The solution also offers multiple encryption methods for you to utilize.

Connectivity could be improved in Microsoft Azure VPN Gateway because it's not as stable, particularly when connecting a device tunnel. It's a good practice to connect up to twenty-five device tunnels to the solution, but that requires more stability, and the tunnels should remain connected whenever you're logged into your machine.

I've been using Microsoft Azure VPN Gateway for two years.

Microsoft Azure VPN Gateway is a stable product.

Microsoft Azure VPN Gateway is scalable, and I'd give it a nine out of ten in terms of its scalability because there's always room for improvement.

I contacted the technical support for Microsoft Azure VPN Gateway. Still, it wasn't good because my company faced many issues and device troubles, but the support team couldn't resolve the problems. Two months passed, yet the issues remained unsolved. For this reason, I'd give Microsoft Azure VPN Gateway support two out of ten.

Negative

The initial setup for Microsoft Azure VPN Gateway was pretty easy. I'd rate its setup a nine on a scale of one to ten.

Configuring and deploying Microsoft Azure VPN Gateway took about thirty to forty-five minutes. After that, you can configure different tunnels and run the solution. For the initial setup, it's thirty to forty-five minutes.

I've been using Microsoft Azure solutions, such as Microsoft Azure VPN Gateway, including storage and networking solutions.

I'm using generation 1 (G1) of Microsoft Azure VPN Gateway.

I deployed the solution for an organization with three hundred to four hundred users.

Anyone who wants the Azure environment connected to an on-premise or remote user's machine should go for the VPN, the managed native VPN of Azure because the setup is pretty straightforward. You can configure that within half an hour, and the communication will be on the local network.

I'd tell anyone planning to use Microsoft Azure VPN Gateway for the first time that it has multiple advanced features and public IP addresses, so I recommend you go through the entire fields required. If anyone commits a single mistake for any of the IP addresses or subnet level, the communication could break, which means having to wait for hours up to a day to rectify that issue. Anyone starting to use Microsoft Azure VPN Gateway should know what IP addresses should be utilized there, for example, the CIDR block for the addresses space. If you're going for advanced Microsoft Azure VPN Gateway features, for example, the BGP, you should also know the correct information you need to fill in each block.

My Microsoft Azure VPN Gateway rating is nine out of ten because it's a managed VPN that allows you to utilize multiple point-to-site connections. You can utilize Azure AD as well for authenticating point-to-site users. Microsoft Azure VPN Gateway is easy to use, so even a non-technical person can easily understand and configure the solution.

I'm a customer of Microsoft.

We use this solution for site-to-site and on our eCommerce channels.

We have been using this solution for about three years. It is deployed on Microsoft Cloud.

VPN gateway works based on how you stabilize and work with it. It isn't stabilized on the first day, and you need to set up the channels properly and understand what bandwidths you're using.

It is scalable and depends on your chosen network bandwidth and the payments made.

We used Novell and Netware in the past before switching to Microsoft. Novell was great because it was more secure. The Novell network is the foundation of every network system that has ever been created. Microsoft solutions are also best on Novell NDS, and active domain services or domain directories have been traded from the Novell directory system.

The setup is easy if you understand the solution and difficult if you don't. We have a support team that assists us with setup.

I rate this solution an eight out of ten. Regarding advice to others, it is essential to understand your needs before using the solution.

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.