Assistanz
Assistanz

Steps to create V-NET Peering using Azure Portal

Steps to create V-NET Peering using Azure Portal

Steps to create V-NET Peering using Azure Portal

In this blog, we will show you the Steps to create V-NET peering using Azure Portal.

 

REQUIREMENTS

  • Azure Subscription
  • Azure VMs & Virtual Networks

 

ENVIRONMENT OVERVIEW

  • We have created two virtual networks named Virtual-Net-one and Virtual-Net-two for this demo.

Steps to create V-NET Peering using Azure Portal

 

  • Also, we set the address space range as 10.0.0.0/16 for Virtual-Net-one and 192.168.0.0/16 for Virtual-Net-two.

Steps to create V-NET Peering using Azure Portal

 

Steps to create V-NET Peering using Azure Portal

 

  • The subnet range for Virtual-Net-one is 10.0.0.0/24 and the Virtual-Net-two range is 192.168.8.0/24.

Steps to create V-NET Peering using Azure Portal

 

Steps to create V-NET Peering using Azure Portal

 

  • Also, we have configured a jump server to access the VM’s under these networks.

Steps to create V-NET Peering using Azure Portal

 

THINGS TO KEEP IN MIND

 

  • VNETs are isolation boundaries and there is no default routing is available between two virtual networks. We need to override this problem.
  • We can create a VNET-VNET VPN between two virtual networks.
  • Another way to link VNETs are through VNET Peering. It is easy to configure without VPN Gateway.
  • Make sure that your IP address ranges do not conflict with other virtual networks.
  • VNETs should be in the same Azure region.
  • This option is less secure compared to the VPN connection.

 

CONFIGURING V-NET PEERING

  • Open the Virtual-Net-one network and select peerings link.

Steps to create V-NET Peering using Azure Portal

 

  • Click on Add button.

Steps to create V-NET Peering using Azure Portal

 

  • Provide a name, Resource Manager, Subscription, and Virtual Network details. Then click OK.

Steps to create V-NET Peering using Azure Portal

 

  • New peering is available on the list.

Steps to create V-NET Peering using Azure Portal

 

  • We need to follow the same above steps for Virtual-Net-two network.

Steps to create V-NET Peering using Azure Portal

 

  • The new peering will be created and peering status is set as connected.

Steps to create V-NET Peering using Azure Portal

 

VERIFICATION

  • Login to the jump server named jumpbox and try to ping the az-vnet02-vm IP 192.168.8.4.

Steps to create V-NET Peering using Azure Portal

 

  • Also, we are able to access the test website which was hosted on az-vnet02-vm.

Steps to create V-NET Peering using Azure Portal

 

VIDEO

 

Thanks for reading this blog. We hope it was useful for you to learn about Azure VNET peering.

Most Popular:

Get The Latest Updates

Subscribe To Our Weekly Newsletter

No spam, notifications only about new products, updates.

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