The course is part of these learning pathsSee 3 more
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 email@example.com.
- 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
This course is intended for anyone who wants to learn about Azure Virtual Networks, how to create them, and how to connect them.
To get the most out of this course, you should have a basic understanding of the Azure platform and networking in general.
Hello and welcome to ExpressRoute. In this lesson, we are going to take a look at what ExpressRoute is and what it offers.
ExpressRoute is an offering you can use to extend your on-prem networks into Azure. It’s essentially a private connection from your network to Azure that’s facilitated by a third-party connectivity provider.
You can use ExpressRoute to establish connectivity from an any-to-any network, a point-to-point Ethernet network, or from a virtual cross-connection through a connectivity provider at a co-location facility. It’s important to note that connections made with ExpressRoute do NOT traverse the public internet. Because they do not traverse the internet, ExpressRoute connections are inherently more secure, more reliable, and typically faster than site-to-site connections that traverse the internet.
ExpressRoute connections offer several benefits. For example, such connections allow you to establish connectivity to Microsoft cloud services across all regions within a geopolitical region. Global connectivity across all regions to Microsoft services can be achieved trough the use of the ExpressRoute premium add-on.
ExpressRoute connections also provide for dynamic routing between your on-prem networks and Microsoft via BGP, and the built-in redundancy that ExpressRoute offers provides higher reliability. There is even a connection uptime SLA of 99.95% for ExpressRoute dedicated circuit availability.
You can use ExpressRoute connections to access Microsoft Azure services and Microsoft Office 365 services. ExpressRoute circuits come in a variety of bandwidths. You can purchase a circuit with as little as 50Mbps in bandwidth, and you can purchase a circuit with as much as 10Gbps in bandwidth. There are also several options in between.
The table on your screen shows what’s available:
- 50 Mbps
- 100 Mbps
- 200 Mbps
- 500 Mbps
- 1 Gbps
- 2 Gbps
- 5 Gbps
- 10 Gbps
You can even increase the bandwidth of your ExpressRoute circuit without having to tear down existing connections. This is a huge plus in my book.
When you deploy an ExpressRoute circuit, you’ll have to decide what billing model you wish to use. The “Unlimited Data” billing model is based on a monthly fee. It offers unlimited inbound and outbound transfer for a single fee.
“Metered Data” billing is also based on a monthly fee. However, it’s a little different from “Unlimited Data” because, while all inbound data transfer is included free of charge, outbound data transfers are charged on a “per-GB” basis.
The “Express Route Premium Add-On” that I mentioned earlier is a paid add-on to the ExpressRoute circuit. This premium add-on increases the number of route limits for Azure public and private peering from 4,000 routes to 10,000 routes. It also offers global connectivity across any region except for the national clouds. The ExpressRoute Premium Add-On also increases the number of vNet links per circuit from the default of 10 to a larger limit, which is determined by the bandwidth of the circuit that you purchase.
Be sure to check out the ExpressRoute FAQ at the URL that you see on your screen: https://docs.microsoft.com/en-us/azure/expressroute/expressroute-faqs
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.