Microsoft Azure Project [AZ-104]
by Sunil Dutt
Implement Azure IaaS
Course-end Project 1
Description
Business Scenario
The OSS Corporation is a globally distributed firm. They have their headquarters in East US with another branch office in South East Asia. Currently, they are working on a project and decided that the application tier of this project will reside in one of its branch regions. For security reasons, OSS Corporation management is adamant on keeping their data tier in the headquarter region.
As an organization, they are open to suggestions and are currently evaluating Azure as a deployment platform. To prepare for deployment of IaaS Standard DS1 v2, OSS Corporation must deploy an IaaS v2 virtual network in the headquarter region for its database. But for the application, it should create another IaaS v2 virtual network in the branch region. In addition, because the communication between App and data should happen over a private channel, one needs to prepare their branch office virtual network for establishing connectivity to the headquarters’ IaaS v2 virtual network by creating a virtual network gateway and deploy a test IaaS Standard DS1 v2 VM to the virtual networks for verifying the connection.
After the deployment team ensures the connectivity between both the networks, you can validate the same using Ping.
Following requirements should be met:
Creating virtual networks in the aforementioned region
Create test virtual machines in both the virtual networks
Establish the connectivity between both the networks via VNet peering
Ensure connectivity is established properly
It sounds like the OSS Corporation is planning to deploy a project using Azure's infrastructure-as-a-service (IaaS) platform while ensuring data security and network connectivity between their headquarters and branch offices. Here's a step-by-step breakdown of the process:
Creating Virtual Networks in the aforementioned region
Create Virtual Networks: Create an IaaS v2 virtual network in the headquarters region (East US) for the data tier. Create another IaaS v2 virtual network in the branch office region (South East Asia) for the application tier.
Create First Virtual Network in Headquarters (East US) Region
Basics:
Resource Group Name: OSS_Corporation
Virtual Network Name: OSS_Headquarters
Location: East US
Security:
Not applicable
IP Addresss: (Default)
Address Prefixes (CIDR VNET): 10.0.0.0/16
Subnets (CIDR Subnet): 10.0.0.0/24
Tags:
IF required otherwise not applicable
Review + Create:
Hit the Create Button.
Virtual Network with Subnet is created in Headquarters (East US) Region.
Create Second Virtual Network in Branch Office (South East Asia) Region
Basics:
Resource Group Name: OSS_Corporation_Branch
Virtual Network Name: OSS_Branch_SE_Asia
Location: South East Asia
Security:
Not applicable
IP Addresss: (Default)
Address Prefixes (CIDR VNET): 192.168.0.0/16
Subnets (CIDR Subnet): 192.168.0.0/24
Tags:
IF required otherwise not applicable
Review + Create:
Hit the Create Button.
Virtual Network with Subnet is created in Headquarters (South East Asia) Region.
Creating test Virtual Machines (VM) in both the virtual networks
Create First Virtual Machine in Headquarter (East US) Region
Basics:
Resource Group Name: OSS_Corporation
Virtual Machine Name: VM-OSS-Headquarters
Location (Region): (US) East US
Image (OS Type): Windows Server 2019 Datacenter – x64 Gen2
Size (Instance Size): Standard_DS1_v2 – 1 vcpu, 3.5 GiB Memory
Select Inbound Port: RDP (3389) (as per the requirement)
Disks:
OS Disk Type: Standard HDD (as per the Requirement)
Networking:
Virtual Network: OSS_Headquarters
Subnet: 10.0.0.0/24
Management:
Monitoring:
Advanced:
Tags:
IF required otherwise not applicable
Review + Create:
Hit the Create Button.
Virtual Machine is created in Headquarters (East US) Region Virtual Network.
Create Second Virtual Machine in Headquarters (South East Asia) Region
Basics:
Resource Group Name: OSS_Corporation_Branch
Virtual Machine Name: VM-OSS-SE-Asia-Branch
Location (Region): (Asia Pacific) Southeast Asia
Image (OS Type): Windows Server 2019 Datacenter – x64 Gen2
Size (Instance Size): Standard_DS1_v2 – 1 vcpu, 3.5 GiB Memory
Select Inbound Port: RDP (3389) (as per the requirement)
Disks:
OS Disk Type: Standard HDD (as per the Requirement)
Networking:
Virtual Network: VM-OSS-SE-Asia-Branch
Subnet: 192.168.0.0/24
Management:
Monitoring:
Advanced:
Tags:
IF required otherwise not applicable
Review + Create:
Hit the Create Button.
Virtual Machine is created in Branch (South East Asia) Region Virtual Network.
Establishing the connectivity between both networks via VNet peering
First of all, go to the virtual Networks Tab
Then, Select Main Network i.e., OSS_Headquarters
And then, go to Peering Tab in OSS_Headquarters
Now, Click on Add and do the setting shown in the snapshots below
Then, Click on ADD button.
Ensuring connectivity is established properly
Connect First Virtual Machine i.e., VM-OSS-Headquarters (East US) by Native RDP as shown below screenshot.
Connect Second Virtual Machine i.e., VM-OSS-SE-Asia-Branch (South East Asia) by Native RDP as shown below screenshot.
After the login both Virtual Machines, run firewall.cpl or Open Windows Defender Firewall in both VMs and then in Advanced Settings allow ICMP traffic in Inbound Rules
Now, Go to Command prompt on both the VMs by typing cmd
Then type ipconfig to check the IP’s of both VMs and then try to ping both VMs with each other by the
Command: Ping <IP of other VM>
For Example: Ping 192.168.0.4
In the Main VM i.e. VM-OSS-Headquarters (East US),
Pinging to Branch VM Successfully with 0% Loss
Both VMs are able to ping each other and Hence the project is completed successfully
