1. Home
  2. Training Library
  3. Microsoft Azure
  4. Courses
  5. Getting Started with Azure Virtual Networks

vNet Peering

The course is part of these learning paths

Microsoft Azure for Solution Architects
course-steps
27
certification
10
lab-steps
14
AZ-303 Exam Preparation: Technologies for Microsoft Azure Architects
course-steps
28
certification
7
lab-steps
13
description
1
AZ-104 Exam Preparation: Microsoft Azure Administrator
course-steps
21
certification
7
lab-steps
16
3 Pillars of the Azure Cloud
course-steps
4
certification
1
lab-steps
1
more_horizSee 2 more
play-arrow
Start course
Overview
Difficulty
Intermediate
Duration
1h 5m
Students
793
Ratings
4.6/5
starstarstarstarstar-half
Description

This course explores Azure Virtual Networks, how to create them, and how to connect them. It begins with a vNet overview and you'll learn about basic Azure Virtual Network concepts and about some key best practices. We'll cover communications topics, filtering, routing, and integration, before working through a demo that shows you how to deploy a virtual network in Microsoft Azure.

After covering the basics of Azure Virtual Networks in the first half of this course, we'll use the second half to dive into VPNs, where you'll learn about site-to-site VPNs, point-to-site VPNs, ExpressRoute, and vNet peering. You'll also watch a demonstration from the Azure platform that shows you how to peer two vNets in Azure. 

If you have any feedback relating to this course, feel free to contact us at support@cloudacademy.com.

Learning Objectives

  • Obtain a foundational understanding of Azure Virtual Networks including key concepts, best practices, communications, filtering, routing, and integration
  • Provision a virtual network
  • Understand what the Azure VPN Gateway is and what it does
  • Build a site-to-site VPN
  • Learn how to connect a single client computer to a virtual network using a point-to-site VPN gateway
  • Learn how to connect your on-premise network to Azure using ExpressRoute
  • Learn how to peer two Azure Virtual Networks

Intended Audience

This course is intended for anyone who wants to learn about Azure Virtual Networks, how to create them, and how to connect them.

Prerequisites

To get the most out of this course, you should have a basic understanding of the Azure platform and networking in general.

Transcript

Hello and welcome to vNet Peering. 

If you find yourself in a spot where you need to establish connectivity between two different Azure virtual networks, you can leverage virtual network peering, or vNet Peering. What vNet Peering does is allow you to seamlessly connect different Azure virtual networks. As far as connectivity goes, both virtual networks appear as one. Any traffic that flows between peered networks will use the Microsoft backbone infrastructure. 

There are two types of peering that Azure supports. They include Virtual Network Peering and Global Virtual Network Peering. Virtual Network Peering allows you to connect virtual networks that are located within the same Azure region as one another, while Global Virtual Network Peering allows you to connect virtual networks deployed in different Azure regions.

Whether its local or global peering that you leverage, both options offer low-latency, high-bandwidth connectivity between Azure resources that are connected to different virtual networks. This connectivity facilitates data transfer across different virtual networks, even when they are in different Azure subscriptions, Azure Active Directory tenants, and Azure regions.

Peering offers you the ability to connect virtual networks that were created through the Azure Resource Manager and it also provides you the ability to connect virtual networks that were created through Resource Manager to those that were created through the classic deployment model. 

I should also mention that creating a peering causes no downtime to resources during the peering process nor after the peering is completed.

Since the traffic between peered virtual networks remains on the Microsoft backbone network, it remains private without the need for the public Internet, gateways, or even encryption.

Network latency between VMs on separate peered virtual networks in the same region is no different than the latency you would see between two VMs within a single virtual network. You can even apply network security groups to either virtual network in the peering if you wish to block access to other virtual networks or subnets. 

Join me in the next lesson, where I’ll show you how to peer two existing virtual networks.

About the Author
Avatar
Thomas Mitchell
Instructor
Students
33642
Courses
42
Learning Paths
15

Tom is a 25+ year veteran of the IT industry, having worked in environments as large as 40k seats and as small as 50 seats. Throughout the course of a long an interesting career, he has built an in-depth skillset that spans numerous IT disciplines. Tom has designed and architected small, large, and global IT solutions.

In addition to the Cloud Platform and Infrastructure MCSE certification, Tom also carries several other Microsoft certifications. His ability to see things from a strategic perspective allows Tom to architect solutions that closely align with business needs.

In his spare time, Tom enjoys camping, fishing, and playing poker.