Probably this will be the last part of the series. In this part I will be creating Virtual Machine on Azure and try to ping On-premises VM and vice-versa. Creating Azure VM is very easy. Select the Resource Group and in Add search for Microsoft Server 2012 R2 Datacenter (You can choose any OS of your choice here). Once it appears on the list, click on it to create, This will be standard Resource Manager deployment. Currently this image includes patch number KB2919355 as shown in the right.

At the heart of the Microsoft cloud os vision, Windows server 2012 R2 brings Microsoft's experience delivering global-scale services into your infrastructure. The virtual machine (VM) offers enterprise-class performance, flexibility for your applications and excellent economics for your datacenter and hybrid cloud environment.

Virtual Machine created in 4 step process, First is basic options, It is asking for name, next is VM disk type, If you need best I/O you can select SSD, but for this lab demo I will select normal HDD. Make note of user name and password, as this will require in the end while logging, All other options (Subscription, resource group and location) are self explaintary as discussed in earlier blogs. Click Ok for next screen.

Second option is Size, here you need to choose a size, it is very crutial stage. The higher the size the higher the costing. So choose it appropriately, I will be chossing A1 Standard for this lab, which best suit right now for demo. There are more options and complete catalog under view all button.

There is caution, Prices presented below are estimates in your local currency that include only Azure infrastructure costs and any discounts for the subscription and location. The prices don't include any applicable software costs. Recommended sizes are determined by the publisher of the selected image based on hardware and software requirements.

3rd option is selecting settings (Here I can configure optional feature), I am choosing the Storage account, Virtual Network and Subnets created in earlier parts. Public IP address and NSG (Network Security Group firewall), are created automatically, and I am keeping them default. I am keeping Extentions none (They are extension softwares and installed while deploying VM ie, antivirus agent or chef agent). I don't require monitoring diagnostics, In case if I enable it it will require seperate storage account to store the data.

This is last step of the summary, here I can see option validation is passed and VM is good to deploy, click OK.

Once I click ok I can see the status on dashboard (Deploying windows server 2012 R2 Datacenter) as well as on notification area, it will take less than 10 -15 min.

Once process is completed Resource group is refreshed I can see new VIrtual machine and in the Overview there is a configuration I see selected for deployment, I can use Public Ip address right away to initiate remote desktop, but I want to test it from my In-house machine.

As IPs are assigned through azure dhcp server, To view the VM IP click on Network interfaces, I can see here 2 IPs present one is public and another is Private. I need private IP address to test from my on-premises environement.

Here just to show from On-premises you won't be able to ping Azure VM immediately but able to RDP, for this ICMP need to be open in VM firewall, for this open RDP session to Azure VM. in the control panel open Windows Firewall, advanced settings, In the inbound rules search for File and print sharing (Echo-request - ICMP v4-in) and enable it by right clicking. I can check the ping results vice-versa and they are successful. In the next part I will be showing same steps using Azure Powershell.