Steps to create VNET-to-VNET VPN using Azure Portal

Steps to create VNET-to-VNET VPN using Azure Portal

Steps to create VNET-to-VNET VPN using Azure Portal

In this blog, we will show you the Steps to create VNET-to-VNET VPN using Azure portal.

 

REQUIREMENTS

  • Microsoft Azure Subscription
  • Azure VM’s for testing

 

OVERVIEW

  • In this demo, We are creating two resource group named AZ-US and AZ-India. AZ-US group location will be south central US and AZ-India group location will be South India.
  • Two virtual networks will be created under this group.
  • Create a Virtual network gateway and make the connection between US and India virtual networks.

 

CREATING RESOURCE GROUPS

  • Open the Azure portal and click on resource groups link in the services link.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Click on Add Button.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Provide the Resouce Group name, subscription and Resource Group location and click Create.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Repeat the above steps to create another resource group named AZ-India.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • New resource groups are created successfully.

Steps to create VNET-to-VNET VPN using Azure Portal

 

CREATING VIRTUAL NETWORK FOR AZ-US

  • From the Azure portal, Click on Virtual Networks.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Click on Add button.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • We use 10.0.0.0/16 network for AZ-US network. Provide the required information click Create button.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • AZ-US-VNET deployed successfully.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Click on the AZ-US-VNET and select the subnets option.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Select the Gateway subnet option.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • We need to create a Gateway subnet before creating the VPN Gateway. Verify your network requirements and assign the address range to the gateway subnet accordingly. We use the 10.0.1.0/24 address range for this demo.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • New gateway subnet is available on the list.

Steps to create VNET-to-VNET VPN using Azure Portal

 

CREATING VIRTUAL NETWORK FOR AZ-INDIA

  • From the Azure portal, Click on Virtual Networks.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Click on Add button.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • We use 192.168.0.0/16 network for AZ-India network. Provide the required information and click Create.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • After successful creation, click on the AZ-India-VNET and select subnets option.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Click on Gateway Subnet option.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • We use 192.168.1.0/24 subnet for this demo. Click Ok to create a new gateway subnet for AZ-India-VNET.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Gateway Subnet is available on the list.

Steps to create VNET-to-VNET VPN using Azure Portal

 

CREATING VIRTUAL NETWORK GATEWAY FOR AZ-US NETWORK

  • From the Azure portal, Click on More services and type virtual network gateway in the search box. Click on it.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • To create a new Virtual Network Gateway, Click the Add button.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Provide a name Name for this gateway then select the Gateway type as VPN and VPN type as Route-based. We select the SKU type as VpnGw1. To learn more about these terms, please check the URL https://www.assistanz.com/azure-vpn-overview/

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Select the AZ-US network under virtual network section.

Steps to create VNET-to-VNET VPN using Azure Portal

 

Note : The Virtual Network option will be greyed out if the Gateway Subnet was not created properly.

 

  • Create a new public IP or select the existing one for this virtual network gateway.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Select the Location and click on Create button.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • It will take 45 minutes to create a virtual network gateway.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Virtual Network Gateway for AZ-US was deployed successfully.

Steps to create VNET-to-VNET VPN using Azure Portal

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • New public IP was assigned to this gateway.

Steps to create VNET-to-VNET VPN using Azure Portal

 

CREATING VIRTUAL NETWORK GATEWAY FOR AZ-INDIA NETWORK

  • From the Virtual Network Gateway, Click on Add button and provide the required information. Also, select the AZ-India Virtual network for this new gateway.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Create a public IP address or select the existing one.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Select the location and click on create button.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • It will take 45 minutes to complete the deployment.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Deployment completed successfully.

Steps to create VNET-to-VNET VPN using Azure Portal

Steps to create VNET-to-VNET VPN using Azure Portal

 

CREATING CONNECTION BETWEEN AZ-INDIA AND AZ-US

  • From the Virtual network gateway, Click on AZ-India-Gateway and select connections option.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Click on Add button.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Provide a name for this connection and leave the default connection type (Vnet-to-Vnet).

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Choose the second network to which connection will be initiated.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Provide a shared key and this will be used later while creating the connection between AZ-US-VNET to AZ-India-VNET. We used Password01 as shared key for this demo.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Click OK to create a connection between India and US V-NET.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • The connection created successfully.

Steps to create VNET-to-VNET VPN using Azure Portal

 

CREATING CONNECTION BETWEEN AZ-US TO AZ-INDIA

  • From the virtual network gateway, Click on AZ-US-Gateway.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Click on Connections option.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Click on Add button.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Provide the required information and select the secondary gateway as AZ-India-Gateway.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • Provide the shared key which we used to create earlier connection and click OK.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • The connection created successfully.

Steps to create VNET-to-VNET VPN using Azure Portal

 

VERIFICATION

  • We have created one VM under each virtual network(AZ-India-VNET and AZ-US-VNET) named AZ-India-VM and AZ-US-VM.

Steps to create VNET-to-VNET VPN using Azure Portal

 

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • The IP Address of AZ-India-VM is 192.168.0.4

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • The IP Address of AZ-US-VM is 10.0.0.4.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • For demo purpose, we created a shared folder named Remoteshare in AZ-India-VM.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • We are able to access the shared folder from AZ-US-VM.

Steps to create VNET-to-VNET VPN using Azure Portal

 

  • You can also see the data in and data out in the virtual network gateway connection tab.

Steps to create VNET-to-VNET VPN using Azure Portal

 

Related Links:

https://www.assistanz.com/azure-vpn-overview/

https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-manage-subnet#create-subnet
https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpn-gateway-settings

 

VIDEO

Thanks for reading this blog. We hope it was useful for you to learn about VNET-to-VNET VPN using Azure Portal.

Share on facebook
Facebook
Share on twitter
Twitter
Share on pinterest
Pinterest
Share on linkedin
LinkedIn
More Interested Related Posts
zfs pool usage

ZFS Pool and Dataset Usage

ZFS Pool and Dataset Usage   I am back with another blog to provide the useful script to the Freebsd users to determine the zpool

Assistanz Networks

Installing Zabbix Agent in FreeBSD 12.0

Zabbix Agent Installation and Configuration Guide on FreeBSD 12.0   Zabbix is an open-source monitoring software tool for diverse IT components, including networks, servers, virtual

DirectAdmin Server Management Plans

Premium Support

24/7 End User Support from your Helpdesk
$ 99 Monthly / Server
  • Unlimited Support Plan
  • 24/7 Emergency Phone
  • Chat Support for Admin
  • Separate Account Manager
  • NDA & SLA
  • SLA Review Meetings
  • FREE Consultancy Services
  • Simple SignUp Process
  • Instant Account Activation
  •  

Platinum Support

24/7 Proactive Support
$ 49 Monthly / Server
  • Unlimited Support Plan
  • 24/7 Emergency Phone
  • Chat Support for Admin
  • Separate Account Manager
  • Advance Proactive Monitoring
  • Guaranteed SLA
  • SLA Review Meetings
  • 3rd Party Application Support
  • FREE Consultancy Services
  • Server Migration Support
  • Weekly Status Report
  • No End User Support
Popular

Unlimited Support

24/7 Support

$ 30 Monthly / Server
  • Unlimited Support Plan
  • 24/7 Support
  • Basic Monitoring
  • 30 Minutes Response Time
  • 4 Hours Resolution time for the Possible Issues
  • Security and Performance Optimization
  • React to Customers queries
  • Simple SignUp Process
  • Instant Account Activation
  • No Third party application support
  • No Migration and End User Support

Cpanel Server Management Plans

Premium Support

24/7 End User Support from your Helpdesk

$ 99 Monthly / Server
  • 24/7 End User White Label Support
  • Unlimited Number of Tickets
  • Chat Support for Admin
  • Separate Account Manager
  • Guaranteed SLA
  • Weekly Status Reports
  • FREE Consultancy Services
  • Simple SignUp Process
  • Instant Account Activation

Platinum Support

24/7 Proactive Server Management
$ 49 Monthly / Server
  • Unlimited Support Plan
  • 24/7 Emergency Phone
  • Chat Support for Admin
  • Separate Account Manager
  • Advance Proactive Monitoring
  • Guaranteed SLA
  • SLA Review Meetings
  • 3rd Party Application Support
  • FREE Consultancy Services
  • Server Migration Support
  • Weekly Status Report
  • No End User Support
Popular

Unlimited Support

24/7 Server Management

$ 29 Monthly / Server
  • Unlimited Admin Tasks
  • 24/7 Support
  • Basic Monitoring
  • 30 Minutes Response time
  • 4 hours Response time for possible issues
  • Security and Performance Optimization
  • React to Customers queries
  • No Third party application support
  • No Migration and End User Support

Cpanel Server Management Plans

Premium Support

24/7 End User Support from your Helpdesk

$ 99 Monthly / Server
  • 24/7 End User White Label Support
  • Unlimited Number of Tickets
  • Chat Support for Admin
  • Separate Account Manager
  • Guaranteed SLA
  • Weekly Status Reports
  • FREE Consultancy Services
  • Simple SignUp Process
  • Instant Account Activation

Platinum Support

24/7 Proactive Server Management
$ 49 Monthly / Server
  • Unlimited Support Plan
  • 24/7 Emergency Phone
  • Chat Support for Admin
  • Separate Account Manager
  • Advance Proactive Monitoring
  • Guaranteed SLA
  • SLA Review Meetings
  • 3rd Party Application Support
  • FREE Consultancy Services
  • Server Migration Support
  • Weekly Status Report
  • No End User Support
Popular

Unlimited Support

24/7 Server Management

$ 29 Monthly / Server
  • Unlimited Admin Tasks
  • 24/7 Support
  • Basic Monitoring
  • 30 Minutes Response time
  • 4 hours Response time for possible issues
  • Security and Performance Optimization
  • React to Customers queries
  • No Third party application support
  • No Migration and End User Support