Skip to main content

How to create Azure Virtual Machine

Hi,

Welcome to Our Blog.
Before Creating Azure Virtual Machine, Lets understand few important terms.



Azure Virtual Machine:
Virtual machines are based on computer architectures and provide functionality of a physical computer. Their implementations may involve specialized hardware, software, or a combination.
Azure Virtual Machines gives you the flexibility of virtualisation for a wide range of computing solutions—development and testing, running applications and extending your datacenter. It is the freedom of open-source software configured the way you need it. It is as if it was another rack in your datacenter, giving you the power to deploy an application in seconds instead of weeks.

Azure Virtual Network:
Azure Virtual Network enables many types of Azure resources, such as Azure Virtual Machines (VM), to securely communicate with each other, the internet, and on-premises networks. A virtual network is scoped to a single region; however, multiple virtual networks from different regions can be connected together using Virtual Network Peering.

Subnet:
An Azure Virtual Network (VNet) is a representation of your own network in the cloud. It is a logical isolation of the Azure cloud dedicated to your subscription. Now, Subnet is further division of the IP address range inside your VNet.

Creating Virtual Machine on Microsoft Azure
Creating the Azure Virtual Network:
  1. Sign in to Azure Portal
  2. Then select Create a resource > Networking > Virtual network on the top left of the screen.



3.  In create Virtual Network enter Virtual Network name as MyVirtualNetwork.
4. Address Space that you want to use for your network, here we have selected ‘class B’ IP address range – 10.1.0.0/16
5. Create a resource as MyVM then select ok.
6. Select the location as South India.
7. Select Subnet as default, IP address range – 10.1.0.0/24
8. Leave the rest of the defaults and select create.  




Creating the Virtual Machine:
  1. Select Create a resource > Compute > Windows Server 2016 Datacenter on the top left of the screen. 
1. 
  1. In select Virtual Machine select the following information.
  2. For resource group, select MyVM that you have created in the last session.
  3. Give the Virtual Machine name as MyVM1.
  4. Select the region South India.
  5. Under administrator give the user name and password for your choice.
  6. One can open inbound ports as per the requirement, for now we have only selected RDP.



8. 

    8. Click on Next: Disk > to update disk parameters (If any).
9. For our sake of convenience for now to save the storage cost we are going to select Standard HDD, else there are two more options (Premium SSD & Standard SSD).

10. Also we will be selecting in advanced settings, use managed disk – No (By default it would be – Yes).




11. Click on Next: Networking > to update Networking parameters (If any).
12. Check that the Virtual Network is the same that we have created in our resource group at start, else select the same from the dropdown list as MyVirtualNetwork. Else if required you can also create a new Virtual Network.
13. Then you can also manage subnet configuration if required, for now we are using the same as we have created while configuring VNET.
14. Public IP needs to be attached to the VM if and only if you want to access this VM publically, else you can select None instead. For now we will be accessing the VM from my local machine so we will require public IP.


15. And select Review+Create



16. Once your validation is done then select Create.
17. Now press ‘Windows key + R’ in your keyboard to open Run, now type MSTSC (for Remote Desktop Connection).



18. Copy the public IP of the VM, from the VM blade, once the VM is created.



19. Paste the Public IP in Remote Connection Manager, then input the Admin Username and password as defined during creation of VM and then click on Connect. 


20. Then Click on Yes and you will be able to access your Virtual Machine.


And here we go Machine is accessible now.

Click here for azure online, classroom trainings and workshops

Below are some awesome azure books you can buy online from Amazon



Comments

Popular posts from this blog

SAN - STORAGE AREA NETWORK - where to start (for beginner)

Hi, Welcome to our blog. This article focuses on basics of SAN which will help you to understand role of SAN in Data Centers and in cloud environment. SAN (Storage Area Network) Definition - It is a network which provides faster input output of data with redundancy and also provides space to store data Advantages - 1. Faster IO ....(Min. 1Gbps - Max 32 Gbps speed) Note- Gbps (Giga Bit Per Second) it is unit to major speed of SAN infrastructure. 2. Redundancy 3. Security 4. Centralized Management of data 5. Serverless Backup 6. LAN Free Backup 7. Scalability 8. N. number of server connection 9. Heterogeneous data Storage 10. BLOCK Level Access 11. High Availability Disadvantage - Costly - compared any other IT technologies this technology is costly SAN it is heart of data center. For any customer data is very important and SAN meets all requirements of the customer. Without SAN we can not imagine Data center even cloud also. Now a Days Cloud Technolo...

Azure Load balancer

Important Terms: Azure load balancer overview Load balancing provides a higher level of availability by spreading incoming requests across multiple virtual machines. An Azure load balancer is a Layer-4 (TCP, UDP) load balancer that provides high availability by distributing incoming traffic among healthy VMs. A load balancer health probe monitors a given port on each VM and only distributes traffic to an operational VM. You define a front-end IP configuration that contains one or more public IP addresses. This front-end IP configuration allows your load balancer and applications to be accessible over the Internet. Virtual machines connect to a load balancer using their virtual network interface card (NIC). To distribute traffic to the VMs, a back-end address pool contains the IP addresses of the virtual (NICs) connected to the load balancer. To control the flow of traffic, you define load balancer rules for specific ports and protocols that map to your VMs. ...