Create Multiple Subnets in Azure
Pluralsight Hands-On Lab — Networking
At a Glance
| Platform | Pluralsight |
|---|
| Category | Azure Networking |
|---|
| Lab Type | Guided + Challenge Mode |
|---|
| Environment | Azure Portal, Windows VM via Remote Desktop |
|---|
| Completed | 2026 |
|---|
Overview
Subnets and Network Security Groups together provide network-level isolation between workloads within the same virtual network. In this lab, two VMs resided on the same subnet with unrestricted communication. I was tasked with separating them into different subnets and blocking traffic between them using NSG rules. I created a second subnet, added inbound and outbound deny rules to the NSG, moved the Linux VM to the new subnet, and validated that ping traffic from the Windows VM to the Linux VM was blocked.
What I Did
- Navigated to the pre-deployed virtual network and created a new subnet (subnet2) with a /24 CIDR range alongside the existing default subnet
- Created an inbound NSG rule at priority 100 denying all traffic from the subnet2 CIDR (10.0.1.0/24) to the default subnet CIDR (10.0.0.0/24) on any port
- Created an outbound NSG rule at priority 100 denying all traffic from the default subnet (10.0.0.0/24) to subnet2 (10.0.1.0/24) on any port
- Navigated to linVM, opened Network Settings, clicked through to the NIC's IP configurations, and changed the subnet assignment from default to subnet2, then clicked Apply
- Waited for the NIC update to complete and the VM to restart, then connected to winVM via RDP
- Opened a command prompt on winVM and ran ping 10.0.1.4 — confirmed the ping failed, validating that the NSG rules successfully blocked inter-subnet communication
← Back to Pluralsight Labs