How to use this page

Work through Tasks 1–6 and tick each step as you complete it. Your progress and answers are saved in this browser automatically.
Wherever you see Screenshot, capture your lab progress and attach the screenshot right on this page. Add a short explanation for each.
Answer the Task 7 questions, then use Print / Save as PDF to export your answers and screenshots as one submission file.
Remember to delete your lab resources after capturing everything.

Lab Objectives and Architecture reference

Lab scenario: Your organization separates core IT services from other departments, like manufacturing. However, sometimes these segmented areas need to communicate. In this lab, you'll set up connectivity between these isolated networks. This approach is commonly used to separate production from development environments or to isolate different subsidiaries.

In this lab, you will:

Task 1 — Create a core services virtual machine and virtual network 15 pts
Task 2 — Create a virtual machine in a different virtual network 15 pts
Task 3 — Use Network Watcher to test the connection between virtual machines 10 pts
Task 4 — Configure virtual network peerings between virtual networks 15 pts
Task 5 — Use Azure PowerShell to test the connection between virtual machines 10 pts
Task 6 — Create a custom route 15 pts
Task 7 — Summary Questions & Review 20 pts

You will build this topology across Tasks 1–6.

Task 1: Create a core services virtual machine and virtual network 15 pts

In this task, you create a core services virtual network with a virtual machine.

Sign in to the Azure portal.
Search for and select Virtual Machines.
From the virtual machines page, select Create then select Azure Virtual Machine.

On the Basics tab, use the following information to complete the form, and then select Next: Disks >. For any setting not specified, leave the default value.

Setting	Value
Subscription	your subscription
Resource group	`<yourName>-clo800-f67-rg`
Virtual machine name	`<yourName>-CoreServicesVM`
Region	(US) East US
Availability options	No infrastructure redundancy required
Security type	Standard
Image	Windows Server 2019 Datacenter: x64 Gen2
Size	`Standard_D2s_v3`
Username	`localadmin`
Password	Provide a complex password
Public inbound ports	None

On the Disks tab, change the OS disk type to Standard HDD and then select the Networking tab.
On the Networking tab, for Virtual network, select Create new.
Use the following information to configure the virtual network, and then select Ok. If necessary, remove or replace the existing information.

Setting Value

Name CoreServicesVnet (Create new)

Address range 10.0.0.0/16

Subnet Name Core

Subnet address range 10.0.0.0/24
Select the Monitoring tab. For Boot Diagnostics, select Disable.
Select Review + Create, and then select Create. Screenshot must show your Odl_user account, the CoreServicesVM virtual machine overview showing the resource group, region, and Running status

Setting	Value
Name	`CoreServicesVnet` (Create new)
Address range	`10.0.0.0/16`
Subnet Name	`Core`
Subnet address range	`10.0.0.0/24`

Note: Did you notice in this task you created the virtual network as you created the virtual machine? You could also create the virtual network infrastructure then add the virtual machines.

Task 2: Create a virtual machine in a different virtual network 15 pts

In this task, you create a manufacturing services virtual network with a virtual machine.

From the Azure portal, search for and navigate to Virtual Machines.
From the virtual machines page, select Create then select Azure Virtual Machine.

On the Basics tab, use the following information to complete the form, and then select Next: Disks >. For any setting not specified, leave the default value.

Setting	Value
Subscription	your subscription
Resource group	`<yourName>-clo800-f67-rg`
Virtual machine name	`<yourName>-ManufacturingVM`
Region	(US) East US
Security type	Standard
Availability options	No infrastructure redundancy required
Image	Windows Server 2019 Datacenter: x64 Gen2
Size	`Standard_D2s_v3`
Username	`localadmin`
Password	Provide a complex password
Public inbound ports	None

On the Disks tab, for the OS disk type select Standard HDD and then click on the Networking tab.
On the Networking tab, for Virtual network, select Create new.
Use the following information to configure the virtual network, and then select Ok. If necessary, remove or replace the existing address range.

Setting Value

Name ManufacturingVnet

Address range 172.16.0.0/16

Subnet Name Manufacturing

Subnet address range 172.16.0.0/24
Select the Monitoring tab. For Boot Diagnostics, select Disable.
Select Review + Create, and then select Create. Screenshot must show your Odl_user account, the ManufacturingVM virtual machine overview showing the resource group, region, and Running status

Setting	Value
Name	`ManufacturingVnet`
Address range	`172.16.0.0/16`
Subnet Name	`Manufacturing`
Subnet address range	`172.16.0.0/24`

Task 3: Use Network Watcher to test the connection between virtual machines 10 pts

In this task, you verify that resources in peered virtual networks can communicate with each other. Network Watcher will be used to test the connection. Before continuing, ensure both virtual machines have been deployed and are running.

From the Azure portal, search for and select Network Watcher.
From Network Watcher, in the Network diagnostic tools menu, select Connection troubleshoot.

Use the following information to complete the fields on the Connection troubleshoot page.

Field	Value
Source type	Virtual machine
Virtual machine	`<yourName>-CoreServicesVM`
Destination type	Virtual machine
Virtual machine	`<yourName>-ManufacturingVM`
Preferred IP Version	Both
Protocol	TCP
Destination port	3389
Source port	Blank
Diagnostic tests	Defaults

Select Run diagnostic tests.
It may take a couple of minutes for the results to be returned. The screen selections will be greyed out while the results are being collected. Notice the Connectivity test shows UnReachable. This makes sense because the virtual machines are in different virtual networks. Screenshot must show your Odl_user account, the Network Watcher Connection troubleshoot results showing the Connectivity test (Unreachable) between CoreServicesVM and ManufacturingVM

Task 4: Configure virtual network peerings between virtual networks 15 pts

In this task, you create a virtual network peering to enable communications between resources in the virtual networks.

In the Azure portal, select the CoreServicesVnet virtual network.
In CoreServicesVnet, under Settings, select Peerings.

On CoreServicesVnet | Peerings, select + Add. If not specified, take the default.

Parameter	Value
Peering link name	`CoreServicesVnet-to-ManufacturingVnet`
Virtual network	`ManufacturingVM-net` (`<yourName>-clo800-f67-rg`)
Allow ManufacturingVnet to access CoreServicesVnet	selected (default)
Allow ManufacturingVnet to receive forwarded traffic from CoreServicesVnet	selected
Peering link name	`ManufacturingVnet-to-CoreServicesVnet`
Allow CoreServicesVnet to access the peered virtual network	selected (default)
Allow CoreServicesVnet to receive forwarded traffic from the peered virtual network	selected

When finished select Add.
In CoreServicesVnet | Peerings, verify that the CoreServicesVnet-to-ManufacturingVnet peering is listed. Refresh the page to ensure the Peering status is Connected.
Switch to the ManufacturingVnet and verify the ManufacturingVnet-to-CoreServicesVnet peering is listed. Ensure the Peering status is Connected. You may need to Refresh the page. Screenshot must show your Odl_user account, the ManufacturingVnet peerings page showing the ManufacturingVnet-to-CoreServicesVnet peering with Peering status Connected

Task 5: Use Azure PowerShell to test the connection between virtual machines 10 pts

In this task, you retest the connection between the virtual machines in different virtual networks.

Verify the private IP address of the <yourName>-CoreServicesVM — from the Azure portal, search for and select the <yourName>-CoreServicesVM virtual machine.
On the Overview blade, in the Networking section, record the Private IP address of the machine. You need this information to test the connection.
Switch to the <yourName>-ManufacturingVM virtual machine.
In the Operations blade, select the Run command blade.
Select RunPowerShellScript and run the Test-NetConnection command. Be sure to use the private IP address of the <yourName>-CoreServicesVM: Test-NetConnection <yourName>-CoreServicesVM private IP address> -port 3389
It may take a couple of minutes for the script to time out. The top of the page shows an informational message Script execution in progress. The test connection should succeed because peering has been configured. Screenshot must show your Odl_user account, the Run command output showing the Test-NetConnection result (TcpTestSucceeded: True) to the CoreServicesVM private IP on port 3389

Did you know? There are many ways to check connections. In this task, you use Run command.

Task 6: Create a custom route 15 pts

In this task, you want to control network traffic between the perimeter subnet and the internal core services subnet. A virtual network appliance will be installed in the Perimeter subnet and all inbound traffic should be routed there.

Search for select the CoreServicesVnet.
Select Subnets and then + Create. Be sure to Save your changes.

Setting Value

Name perimeter

Subnet address range 10.0.1.0/24

Setting	Value
Name	`perimeter`
Subnet address range	`10.0.1.0/24`

In the Azure portal, search for and select Route tables, and then select Create.

Setting	Value
Subscription	your subscription
Resource group	`<yourName>-clo800-f67-rg`
Region	East US
Name	`rt-CoreServices`
Propagate gateway routes	No

After the route table deploys, select Go to resource.

From Settings, select Routes and then + Add. Create a route from the future NVA to the CoreServices virtual network.

Setting	Value
Route name	`PerimetertoCore`
Destination type	IP Addresses
Destination IP addresses	`10.0.0.0/24` (Core subnet)
Next hop type	Virtual appliance (notice your other choices)
Next hop address	`10.0.1.7` (future NVA)

Select + Add when the route is completed. The last thing to do is associate the route with the subnet.
Select Subnets and then Associate. Complete the configuration.

Setting Value

Virtual network CoreServicesVnet

Subnet Perimeter
Note: You have created a user-defined route to direct inbound traffic from the DMZ to the new NVA. Screenshot must show your Odl_user account, the rt-CoreServices route table showing the PerimetertoCore route and the subnet association

Setting	Value
Virtual network	`CoreServicesVnet`
Subnet	Perimeter

Task 7: Summary Questions & Review 20 pts

Minimum 2-3 sentences each — original thinking, your own words!

Describe the main focus of this lab and outline the new skills or concepts you learned during this Azure lab session.
What challenges did you encounter during this lab, and how did you overcome them?
How do the tasks performed in this lab enhance your understanding of Azure networking?
In what ways can you apply the knowledge gained from this lab to real-world scenarios? Please provide specific examples.

Sample screenshots reference

These screenshots are just samples. Your screenshots may vary, but they should include similar details underlined.

Clean up your resources

Remember to delete any Azure resources created for this lab after capturing all your information and screenshots. Removing unused resources ensures you will not have unexpected charges and helps you manage your Azure credit for the course. Delete all resource groups except the Odl-Seneca-lab default resource group.

Your submission preview

Screenshots you attach above and your Task 7 answers appear here. This is exactly what prints/exported as your PDF.

CLO800 Lab 02 - Hybrid Network Connectivity

Name: . Account: ·

Professor: Dr. Kazemi

Submit compile & export

All screenshots attached in task order, each with your Odl_user account visible (underlined or highlighted).
A brief explanation added for each screenshot.
Export the PDF with Print / Save as PDF and upload it to the Blackboard assignment.