This is the first part of the several parts of the Azure Virtual Networking session. In this session I go over what Azure Virtual Networks or VNETs are and how they are created. What is Hybrid cross- Demonstration is provided on how the VNETs are created with address space and subnets in mind. There is also a detailed demonstration of VNETs isolation and acessing services across VNET subnets.
3. Azure Virtual Networks - Part 1
Configure a virtual network
• Design subnets
• Deploy a VM into a virtual network
• Deploy a cloud service into a virtual network
• Configure static IPs
• Configure internal load balancing
Modify a network configuration
• Modify a subnet
• Import and export a network configuration
Design and implement a multi-site or hybrid network
• Choose the appropriate solution between ExpressRoute, site-to-site, and point-to-site
• Choose the appropriate gateway
• Identify supported devices and software VPN solutions
• Identify networking prerequisites
• Configure regional virtual networks and multi-site virtual networks
4. Azure Virtual Networks - Part 1
Building block of Azure IaaS
1. Compute
2. Networking
3. Storage
What is a Virtual Network (VNET)?
Customer managed secure, isolated virtual networks; it’s a network overlay that
can be configured in Azure.
5. Azure Virtual Networks - Part 1
Services and VMs that are part of the same VNET can access each other
Subscription can have as many as 100 VNETS; 10 default
Each VNET can have as many Subnets
Virtual Networks are limited to single region
No IPv6 support
All services deployed within a VNET can access
internet
Virtual Network
VM1 VM2
Subnet: 192.168.1.0/24
VM3
6. Azure Virtual Networks - Part 1
Cloud only VNETs
When a VNET is created in Azure
Clouds and VMs are accessed through endpoints
Do not have to consider on premise network addressing
No configuration of VPN devices are required
7. Azure Virtual Networks - Part 1
Cross-Premises Virtual Networks (Hybrid Networks)
Connection of On-premise network with the Cloud VNET
Requires a VPN device
On-premise
Virtual Network
VM1 VM2
Subnet: 192.168.1.0/24
8. Azure Virtual Networks - Part 1
VNET Address Space and Subnets
Specify topology during VNET creation; address space and subnet
Private Address Spaces
• This is the range VMs and Services can use
• Non-routable
• Specified in CIDR notation (Classless Inter-Domain Routing)
10.0.0.0/8 : 10.0.0.0 – 10.255.255.255
172.16.0.0/12 : 172.16.0.0 – 172.31.255.255
192.168.0.0/16 : 192.168.0.0 – 192.168.255.255
9. Azure Virtual Networks - Part 1
VNET Address Space and Subnets
Subnets
Break up the network for more manageable sections
All services can be access across subnets
Network Security groups can be utilized to implement ACLs
Subnet1: 192.168.1.0/24 – Web Servers
Subnet2: 192.168.2.0/24 – FTP Servers