Microsoft Azure VPN Gateway Reviews

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.

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.

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.

Our company implements Microsoft Azure VPN Gateway for our clients to establish site-to-site connections. 

The solution must be deployed to communicate between data centers and Azure. Without Microsoft Azure VPN Gateway in our company, we cannot communicate with the servers. 

Security and communications are the most vital features of Microsoft Azure VPN Gateway. The solution is highly secure as it follows security standards such as IPSec and PLS. 

The price of the solution should be more affordable. For instance, if we need to use a VPN in a production environment, we need to use a VPN with a price of around $120 per month. The basic version of the solution is available for $25 per month, but it fails to provide the same production performance in comparison to AWS VPN which costs around $32 per month. 

I have used Microsoft Azure VPN Gateway.  

The solution exhibits impressive stability. 

Varying VPNs differ in terms of use cases and performance. The feasible VPNs for a production environment cost around $120 per month. But if I compare the solution with AWS VPN in a production environment, Microsoft Azure VPN Gateway would be a more cost-effective option.   

The performance capacity of different features of the solution is satisfying and doesn't need improvements. The vendor should release a more affordable version of the solution for the production environment. 

Satisfying tech support is provided for the solution. I would rate the tech support an eight out of ten. The response time is good enough, but it depends on the type of support requested. 

Positive

It's extremely simple to setup or deploy Microsoft Azure VPN Gateway. The solution is deployed in our organization in both, public and private clouds. I can manage the cloud-end deployment of the tool by myself, but for client-side deployment for our organization, it depends; they often have network outsourcing processes, and due to that, an additional professional might be required. 

Microsoft Azure VPN Gateway is a better product than other competitor solutions, and from that perspective, an ROI can be realized. 

It's an expensive product. 

In our company, we have witnessed Microsoft Azure VPN Gateway function properly without any fluctuations or issues with speed. Before implementing the solution, we used to define the VPN type in our organization, depending on varying services and considering them for implementation. The solution operates satisfactorily with the default configuration of the four different types of VPNs. I would rate the product an overall 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.

I use the solution in my company to build IPsec tunnels on on-prem sites with Microsoft Azure's cloud services.

The feature that can improve our company's network connectivity revolves around the tool's IPSec functionality. I like the stability, HA, and performance of the product.

The product's deployment phase is not simple, making it an area where improvements are required.

I have two years of experience with Microsoft Azure VPN Gateway.

It is a stable solution. Stability-wise, I rate the solution a ten out of ten.

It is a scalable solution.

Around 100 people use the tool in my company.

The solution can be deployed by myself.

The product's deployment phase is not straightforward.

The solution can be deployed by following the step-by-step instructions in Microsoft's guide.

The solution can be deployed in an hour.

The solution can be deployed by myself.

The measurable benefits that I have observed from the use of the product revolve around the scalability part.

I pay the licensing charges associated with the tool on an hourly basis. The tool is affordable.

Microsoft products have better scalability. The tool integrates well with other Microsoft products.

I recommend the product to others who plan to use it.

The tool is stable and cheap if used at a lower speed and with lower connections for users.

I don't use AI tools. I only work with networking solutions.

Considering the popularity of the vendor, I rate the tool a nine out of ten.

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.

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.