Microsoft Azure VPN Gateway Reviews

In a specific assignment, I connected the client's existing physical network to their Azure instance, as they had no prior knowledge of how to start or conduct this. I supported them due to my previous engagement with them on other services. The task involved maintaining their existing physical network while moving everything into Azure.

The primary function of Azure VPN Gateway allows for designing subnets from existing networks, whether they are physical or virtual networks within Azure or other cloud instances. You can configure these networks using IP numbers and connect them using certificates or SaaS strings. It also requires Entra ID for privileged access groups, resulting in high security.

We deployed the Azure VPN Gateway to connect our Las Vegas office to the cloud. 

Additionally, we are migrating several offices, having completed one so far. Each area originally had its own independent infrastructure, and we are using the solution to connect ports to our data center and build new machines.

The VPN Gateway is valued for its ease of use and redundancy. It simplifies the process of deploying a VPN connection, replacing all the physical network elements with a software appliance. It's cost-effective by eliminating the need for firewall and networking equipment purchases. 

This solution also facilitates the migration by allowing connectivity between previously isolated environments and our Americas environment.

We use it for B2C. We use Azure VPN to connect on-prem networks to Azure. Doing just site-to-site.

We use it on the infrastructure side, sort of VNet, Azure Firewall, Azure Load Balancer, and Azure Front Door.

I've got a sort of peripheral understanding of Logic Apps. We do utilize them.

We just use it because it's the native tool. It performs exactly the same whether we use VPN Gateway or a third-party appliance.

Azure VPN Gateway is primarily used for high-availability connectivity between on-premises and Azure cloud networks. When customers or organizations need to connect their on-premises network to their Azure network, the Azure VPN Gateway is the appropriate tool. Setting up this connectivity requires deploying an Azure VPN Gateway within the Azure environment and a compatible VPN gateway on the on-premises side. Azure supports various VPN gateway options from manufacturers like Fortinet and Cisco.

Once both VPN gateways are in place - the Azure VPN Gateway (Azure VPN v3) and the on-premises VPN gateway - you can establish point-to-site or site-to-site connectivity. Point-to-site connectivity enables remote connections, particularly for employees working from home. In this scenario, there is no need for a VPN gateway at the on-premises location. Instead, you only need to configure the Azure VPN Gateway, generate a VPN profile, and distribute it to the relevant users. This allows remote users to connect securely to the Azure network from anywhere, as long as they have the VPN profile configured on their system.

Azure VPN Gateway has several SKUs, each with a specific capacity, bandwidth, and throughput. We currently use the Basic SKU, which Azure is working on phasing out soon. This SKU might become unavailable for customization soon. The next tier is VPN GW1, which faces the same issues as the first generation. Azure checks automation for all SKUs with a defined bandwidth and throughput.

When the VPN tunnel is created, the bandwidth impacts traffic flow within the tunnel. For organizations or corporations using the VPN, the workload will determine the amount of traffic handled. They can select the appropriate SKU to match their traffic needs.

Azure VPN Gateway is a managed service dedicated solely to allowing traffic in and out, functioning purely as a VPN gateway without additional firewall capabilities.

For our data source connections, we connect it to our on-premise data centers. Those connectivities are established by using Azure VPN Gateway.

Azure VPN Gateway has helped us in having a secure and reliable connection between our on-premise data centers and the Azure cloud. It supports various protocols, helping us to maintain secure data connections.

The ability to connect old protocols like Border Gateway Protocol is valuable. BGP is over 20 years old, but some customers still use it. Amazon, Google, IBM, and Oracle do not support BGP, but Microsoft does. It is good for the customers. If we ask the customers to change many things in their infrastructure to go to the cloud, it will put them off because it means they must spend more money to save money.

The product must provide a single sign-on. As of now, a shared secret is exchanged between both VPNs. It is quite compromisable. It will be good if a single sign-on feature is enabled in VPN Gateway or bundled with it.

I use Microsoft Azure VPN Gateway for hybrid networking. It is utilized to connect our cloud resources securely.

It has supported business growth with its scalable features, allowing us to expand our infrastructure as needed.

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.