Implementing Azure IaaS

(Azure AZ : 104 Level)

Business Scenario

The OSS Corporation is a globally distributed firm. They have their headquarters in East US with another branch office in SouthEast 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 headquarter’s 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. 

My Solution

1.a
1.a
Selecting ‘Virtual Networks’ from the Azure Portal
1.b
1.b
Clicking on ‘Create’ in Virtual Networks Page
1.c
1.c
Creating ‘EastUS_VirtualNetwork’ in a New Resource Group ‘RG01’
1.d
1.d
Creating ‘SouthEastAsia_VirtualNetwork’ in the Resource Group ‘RG01’
1.e
1.e
Reviewing Virtual Networks Page

Step 1 = Creating Virtual Networks

  • 1.a – Selecting ‘Virtual Networks’ from the Azure Portal
  • 1.b – Clicking on ‘Create’ in Virtual Networks Page
  • 1.c – Creating ‘EastUS_VirtualNetwork’ in a New Resource Group ‘RG01’
  • 1.d – Creating ‘SouthEastAsia_VirtualNetwork’ in the Resource Group ‘RG01’
  • 1.e – Reviewing Virtual Networks Page
2.a
2.a
Peering EastUS_VirtualNetwork and SouthEastAsia_VirtualNetwork (Part 1)
2.b
2.b
Peering EastUS_VirtualNetwork and SouthEastAsia_VirtualNetwork (Part 2)
2.c
2.c
Peering EastUS_VirtualNetwork and SouthEastAsia_VirtualNetwork (Part 3)

Step 2 = Peering The Virtual Networks

  • 2.a – Peering EastUS_VirtualNetwork and SouthEastAsia_VirtualNetwork (Part 1)
  • 2.b – Peering EastUS_VirtualNetwork and SouthEastAsia_VirtualNetwork (Part 2)
  • 2.c – Peering EastUS_VirtualNetwork and SouthEastAsia_VirtualNetwork (Part 3)
3.a
3.a
Selecting ‘Virtual Machines’ from the Azure Portal
3.b
3.b
Selecting ‘Create Virtual Machine’ from Azure Portal
3.c
3.c
Creating First Virtual Machine in EastUS (Part 1)
3.d
3.d
Creating First Virtual Machine in EastUS (Part 2)
3.e
3.e
Creating Second Virtual Machine in SouthEastAsia (Part 1)
3.f
3.f
Creating Second Virtual Machine in SouthEastAsia (Part 2)
3.g
3.g
Reviewing Virtual Machine Page After Creating Both The VMs

Step 3 = Creating VMs In the Virtual Networks

  • 3.a – Selecting ‘Virtual Machines’ from the Azure Portal
  • 3.b – Selecting ‘Create Virtual Machine’ from Azure Portal
  • 3.c – Creating First Virtual Machine in EastUS (Part 1)
  • 3.d – Creating First Virtual Machine in EastUS (Part 2)
  • 3.e – Creating Second Virtual Machine in SouthEastAsia (Part 1)
  • 3.f – Creating Second Virtual Machine in SouthEastAsia (Part 2)
  • 3.g – Reviewing Virtual Machine Page After Creating Both The VMs
4.a
4.a
Downloading RDP File of EastUS-VM
4.b
4.b
Downloading RDP File of SouthEastAsia-VM
4.c
4.c
Connecting to EastUS-VM
4.d
4.d
Connecting to SouthEastAsia-VM
4.e
4.e
Pinging SouthEastAsia_VM from EastUS_VM
4.f
4.f
Pinging EastUS_VM from SouthEastAsia_VM

Step 4 = Connecting to the VMs

  • 4.a – Downloading RDP File of EastUS-VM
  • 4.b – Downloading RDP File of SouthEastAsia-VM
  • 4.c – Connecting to EastUS-VM
  • 4.d – Connecting to SouthEastAsia-VM
  • 4.e – Pinging SouthEastAsia_VM from EastUS_VM
  • 4.f – Pinging EastUS_VM from SouthEastAsia_VM