Module 1 · Configure Virtual Networks

MS Learn: Configure Virtual Networks · learn.wwl.configure-virtual-networks Module note for Path MOC

Overview

This is the foundation module of the networking path. It covers designing and implementing the IP address space (CIDR/IP addressing) and creating a Virtual Network segmented into subnet, then assigning IP addresses to resources. Everything else in the path (peering, routing, security, DNS) builds on these core objects.

Learning objectives (from Microsoft Learn)

In this module, you learn how to:

  • Describe Azure virtual network features and components.
  • Identify features and use cases for subnets and subnetting.
  • Identify use cases for private and public IP addresses.
  • Create a virtual network and assign IP addresses.

Units

  1. Introduction
  2. Plan virtual networks
  3. Create subnets
  4. Create a virtual network
  5. Plan IP addressing
  6. Create public IP addressing
  7. Associate public IP addresses
  8. Associate private IP addresses
  9. Lab: Configure and design Azure Virtual Networks
  10. Knowledge check
  11. Summary and resources

Concepts introduced

Key terms & commands (Azure CLI)

# Plan: private range (e.g. 10.0.0.0/16), subnets within it
az vnet create -g <rg> -n <vnet> --address-prefixes 10.0.0.0/16     --subnet-name snet-frontend --subnet-prefixes 10.0.1.0/24
az vnet subnet create -g <rg> --vnet-name <vnet> -n snet-app     --address-prefixes 10.0.2.0/24
az network public-ip create -g <rg> -n <pip> --allocation-method static     --sku Standard

Hands-on

  • Create a VNet + subnets in the portal and confirm reserved addresses.
  • Assign a static public IP and note private vs public address widths for a VM NIC.

Exam focus

  • VNet is regional; subnets must lie within and not overlap.
  • Reserved addresses in each subnet (~5 per subnet).
  • Private RFC1918 vs public IP; dynamic vs static allocation.
  • One NIC = one private IP; NIC in one subnet/VNet.

Path MOC · vnet · subnet · cidr-ip-addressing · configure-vnet-peering · control-network-traffic-flow-with-routes