This is a lab I built and practiced to strengthen my understanding of Azure networking fundamentals. I created a custom Virtual Network (vNet) and segmented it with subnets to simulate real-world infrastructure scenarios. I configured address spaces, applied encryption for secure traffic flow, and used tags to organize resources by environment and department—making the setup easier to manage and audit.
This lab helped me explore how vNets support scalable, secure communication between Azure services. Every step is documented with screenshots and narration, showing exactly how I approached the design, configuration, and governance of cloud networks.
In this hands-on lab, I practiced building and securing an Azure Virtual Network from the ground up.
✅ Practiced creating a Virtual Network in Azure using the portal interface
✅ Configured custom address spaces and IP ranges to match realistic deployment scenarios
✅ Set up multiple subnets to logically segment resources within the vNet for better control and isolation
✅ Applied encryption settings to secure internal traffic and reinforce network security
✅ Used resource tags to organize the vNet by environment type—clearly labeling production vs. development
✅ Reviewed and validated all vNet and subnet configurations before deployment to ensure accuracy and alignment with best practices
Screenshot shows the dropdown menus for selecting a vNet and its associated subnet during resource configuration.
Selected the “+ Create” button in the Virtual networks section to begin provisioning a new vNet. This step initiates the setup of custom address spaces, subnets, and region-specific connectivity for secure Azure infrastructure.
Selected the Resource group dropdown to associate the virtual network with a logical container for related resources. This step simplifies Azure resource organization, access control, and cost tracking.
Assigned the virtual network to the ProdRG resource group to group the vNet with relevant production assets. This enhances resource management, access control, and billing.
Selected the Virtual network name field to define a clear and descriptive label for the vNet. Naming the network helps with resource identification, automation scripts, and long-term infrastructure clarity.
Entered “vNet-App” as the virtual network name to clearly define and segment the network in Azure. Naming conventions aid in resource identification, automation, and governance.
Advanced to the Security tab during virtual network creation to configure protection settings such as encryption. This step ensures secure access and traffic control for your vNet.
Checked the Virtual network encryption box to enable encryption for traffic within the vNet. This enhances data confidentiality and aligns with compliance requirements for secure cloud environments.
to proceed with configuring your IP address range and defining subnets for logical resource segmentation within the virtual network.
Double-clicked the default IPv4 address space 10.0.0.0/16 to edit or confirm the virtual network’s address range. This CIDR block defines the scope of IP allocation for subnets and connected resources.
Entered the custom IPv4 address space 192.168.0.0/16 to define the private IP range for the virtual network. This CIDR block sets the foundation for subnetting and internal resource communication.
Selected the “+ Add a subnet” button to define a custom subnet within the virtual network. This step enables segmentation of the address space, allowing isolated resource groups and service-specific routing.
Selected the Subnet purpose dropdown to define the role of the subnet within the virtual network. This setting helps Azure optimize routing, security, and service behavior based on workload type.
Selected “Default” as the subnet name to designate the primary segment within the virtual network. This naming convention simplifies routing, policy assignment, and resource grouping.
Double-clicked the subnet name “defaultv2” to edit its properties, including address range, security group, and delegation settings. This step ensures the subnet is correctly configured before deployment.
Entered “apps” as the subnet name to designate a dedicated segment for application workloads. Clear naming conventions help organize resources, apply targeted policies, and simplify future scaling.
Scrolled down the subnet configuration panel to access advanced options like NAT gateway, route table, service endpoints, and delegation. This step ensures full visibility before finalizing subnet setup.
Selected the “Add” button to finalize subnet configuration and attach it to the virtual network. This step commits the subnet’s address range, security settings, and routing policies for deployment.
Advanced to the next configuration blade after defining IP address space and adding subnets like default and apps. This step transitions from network layout to tagging.
Selected the tag Name dropdown to choose a predefined label for the virtual network. Tags help organize resources by environment, department, or cost center — making management and billing more efficient.
Selected “Environment” from the tag name dropdown to classify the virtual network by its deployment context — such as Development, Testing, or Production. Tagging improves cost tracking, automation, and resource visibility.
Selected the tag Value dropdown to assign a specific environment label — such as Development, Staging, or Production — to the virtual network. This enhances resource tracking, automation, and cost attribution.
Chose “Production” from the tag Value dropdown to indicate the virtual network’s operational environment. This tag helps distinguish mission-critical workloads from development or staging, improving governance and cost tracking.
Click to review the configured settings—this step confirms your vNet name, resource group, and prepares for IP range and subnet definition._
Selected the "Create" button to deploy the virtual network AzureVNet with its configured subnets, IP ranges, security settings, and tags. This action provisions the network infrastructure, enabling connectivity for dependent Azure services.
Triggered deployment for Web-App-17268972413, initiating resource provisioning and configuration. This step monitors the deployment lifecycle and ensures successful setup of the web application environment.
Selected the “Go to resource” button after successful deployment of vNet-App-17268972413. This step opens the resource overview for post-deployment validation, configuration, and integration with other Azure services.
Clicked the “Settings” section in the left sidebar to access advanced configuration options for the virtual network vNet-App. This includes diagnostics, access control, tagging, and integration with security services.
Selected the “Address space” field to review or modify the IP range assigned to VNetApp. This CIDR block defines the scope for subnetting and internal resource communication across the virtual network.
Opened the Subnets blade to view and manage subnet configurations within the virtual network vNet-App. This includes subnet names, address ranges, service endpoints, NAT gateways, and security group assignments.
🔚 This marks the end of the virtual network setup steps. From here, you’ll see a detailed table of existing subnets and can begin provisioning workloads, applying policies, or integrating services like Azure Firewall or Bastion.
