Blog

Hands-on – Creating VM

 

1. Search for a virtual machine and open it.

 

 

 

2. It’s the UI of the VM of Azure.

 

 

 

3. Now we will try to create the VM, by clicking on “Create” and Selecting the Azure virtual machine.

 

 

4. Select it and create the virtual machine

1. In this, we need to select the subscription, as I’m using student I have selected the “Azure for students” subscription.
2. Create a new resource group, as I have created Vm1_group.
3. Name the VM – Vm1.
4. Selecting the nearby region – central India.
5. Select the available option and zone.

 

 

 

 

5. Now, we need to select the security type – standard.

1. Image – which is known as the operating system, as I have selected Ubuntu
2. In VM architecture -X64
3. In size, I have selected free service eligible.

 

 

 

1. Now, In the administrator account We will create the SSH Public key or password.
2. We need to give the Username, SSH public key source, and Key pair name.
3. In Inbound port rules,
4. Select public inbound ports- allow selected ports and in ports select SSH.

 

 

 

6. Now, In Disk Session Try to select the free tier eligible in OS disk and in OS disk type we can select anything And the rest will be the default.

 

 

 

7. Now, in the network session, we will try to give inbound and outbound rules In this default Virtual network and subnets are created.

               1. Rest all will be the default.

 

 

8. We can create our virtual network, based on our requirements.

9. As of now, I’ll be selecting the default, which is created by itself.

 

 

 

10. In management, it will be default no need to change anything.

 

 

 

11. In monitoring also, it will be the default.

 

 

12. In advance also it will be the default, no need to modify it.

 

 

 

13. In tags also it will be default, if we want we can add tags.

 

 

14. At last, you can review all the details which we have entered and click on Create.

 

 

 

15. While creating you will get the pop-up for downloading the key pair, which we have created before, for login to the VM.

 

 

 

16. Here you can see the VM that is created. 

 

 

 

 

 

17. Here you can see the details of the VM that we have created.

 

 

 

18. Here in disk settings, we can able to create and attach a new disk, or else we can attach an existing disk based on our requirement. 

 

 

 

19. Click on Connect to open the VM.

 

 

 

 

20. Here you can choose the local machine through which you want to launch the Virtual machine. I’ll try to select the Native SSH.              

 

 

 

21. Here in the 3^rd step we need to paste the keypair that we have downloaded, and we need to copy the link which is shown as “SSH to Vm specified private key” and we need to paste it in CMD.

 

 

 

22. Here you can see I have copy-pasted the link.

 

 

 

1. Now I’ll try to paste the link cmd.
2. Here we need to authenticate by typing yes.

 

 

 

1. Here you see the VM has been launched.

 

 

 

1. Now we will try to run some basic commands to check.

 

 

 

1. If we want to delete the VM, we can delete the resource gap, as it will have all the contents connected to it, as you can see below.

 

 

 

1. So, we will try to delete the resource grp so that VM will also be deleted automatically.
2. So, click on delete resource group.

 

 

 

1. Now we need to write the VM name that we are going to delete and click on delete.

 

 

 

1. Here we need to confirm the deletion

 

 

 

1. Here you can see there is a No VM. 

 

 

 

Compute services types

 

1. Azure Virtual Machines
2. Azure App Service
3. Azure Container Instances
4. Azure Kubernetes Service
5. Azure Functions
6. Azure Virtual Desktop

 

Azure Virtual Machine

Provides highly flexible/scalable, cost-effective, and quick computing capacity in the Azure Cloud.

1. With Azure Virtual Machine service, you can create and use VMS in the cloud.
2. Infrastructure-as-a-Service (IaaS)
3. Full control over the machine just like your physical computer
   1. Operating System (OS): Linux or Windows
   2. Size of VM – CPU, RAM, disk/storage, and so on
   3. Network configurations: Virtual network, Subsets
   4. Firewall rules: security group
   5. The ability to run custom software.
   6. To use custom hosting configurations.
4. Must maintain and patch VM
   1. Need to configure, update, and maintain the software that runs on the VEA.

 

Imp options to choose from while creating a VM:

1. Type of image – OS and software
2. Size of VM – CPU/RAB4/Storage
3. Availability options

Use Cases:

1. During testing and development.
2. The application might need to handle fluctuations in demand
3. shutting down VMS when you don’t need them
4. During disaster recovery.
5. Move to the cloud with VMS

 

Subscriptions

 

1. Using Azure requires an Azure subscription.
2. An Azure subscription is a logical unit of Azure services that links to an Azure account. It also allows you to provision resources.
3. A subscription provides you with authenticated and authorized access to Azure products and services.
4. Azure generates separate billing reports and invoices for each subscription
5. Two types of subscription boundaries
   1. Billing boundary
   2. Access control boundary
6. You can create separate subscriptions based on:
   1. Environment: development and testing, security, or isolating data for compliance reasons
   2. Organizational structures: IT, HR, Admin, and so on
   3. Billing: manage and track costs based on your needs, for example, Production, Test, and Dev.

 

 

Different types of Subscription:

 

1. FREE: An email address and a credit card are required to sign up for a free trial subscription that provides $200 credit for the first 30 days and 12 months of restricted access.
2. Pay-Per-Use: Charges monthly based on Cloud resource use.
3. Enterprise: A single Enterprise agreement is established for large subscription purchases, including savings for new licenses and Software Assurance.
4. Student: This membership includes $100 for 12 months and may be activated without a credit card.

 

Management groups

 

1. Management groups let you organize multiple subscriptions as a single management entity to facilitate easier management.
2. You can create management groups in a hierarchical structure with the top level of the hierarchy at the tenant level and containing all subscriptions in that tenant.
3. Any conditions applied to a management group apply to all subscriptions contained in that management group object.
4. Each management group and subscription can support only one parent.
5. Each management group can have many children.
6. The root management group can’t be moved or deleted, unlike other management groups.

 

 

Azure Resource Groups & Resource Manager

 

Organizing structure for resources

 

1. Resources: Resources are instances of services that you create, like virtual machines, storage, or SQL databases.
2. Resource groups: Resources are combined into resource groups, which act as a logical container into which Azure resources like web apps, databases, and storage accounts are deployed and managed.
3. Subscriptions: A subscription groups together user accounts and the resources created by those user accounts. For each subscription, there are limits or quotas on the amount of resources that you can create and use. Organizations can use subscriptions to manage costs and the resources created by users, teams, or projects.
4. Management groups: These groups help you manage access, policy, and compliance for multiple subscriptions. All subscriptions in a management group automatically inherit the conditions applied to the management group.

 

Resource Groups

 

1. Resources: are anything you create in an Azure subscription like VMs, Azure Application Gateway instances, and Azure Cosmos DB instances.
2. A resource group is a logical container that helps manage and organize your Azure resources.
3. For example similar usage, type, or location
4. Each resource can exist in only one resource group.
5. You can move a resource from one resource group to another group.
6. Resource groups can’t be nested.
7. The resources in a resource group can be located in different regions than the resource group.
8. Resource group created at location – to store metadata.
9. A resource group can be used to scope access control for administrative actions. To manage a resource group, you can assign Azure Policies, Azure roles, or resource locks.
10. You can apply locks to a resource group or subscription to prevent deletion or make contained resources read-only. You can also apply locks directly to a resource.
11. You can apply tags to a resource group. The resources in the resource group don’t inherit those tags.
12. Life cycle: When you delete a resource group, all resources in the resource group are also deleted.
13. To create a resource group, you can use the portal, PowerShell, Azure CLI, or an ARM template.

 

 

Azure Resource Manager (ARM)

 

1. Automate resource deployments (create, update, and delete) using templates.
2. ARM template is a JSON file that defines what you want to deploy to Azure.
3. Integrates with Azure portal, PowerShell, CLI, and REST API to perform deployment
4. and management tasks.
5. Easy way to deploy multiple resource instances or reliably redeploy resources.
6. ARM template can be used to deploy the resources consistently and repeatedly.
7. Define the dependencies between resources so they’re deployed in the correct order.

 

 

 

Data Centers, Regions, Region pairs

 

⮚Region, which is a physical location around the world where we cluster data centers.

⮚Azure has more global regions than any other cloud provider.

⮚Better scalability and redundancy

⮚Preserve data residency

⮚Low Latency

⮚Global Footprint

⮚High Availability

⮚How to choose region?

⮚Compliance

⮚Proximity

⮚Available services

⮚Pricing

 

 

  Azure region pairs 

 

⮚Each Azure region is always paired with another region within the same geography

⮚Data centers are usually 300+ miles apart

⮚Automatic replication and failover for some azure services.

⮚Additional advantages of region pairs:

⮚If an extensive Azure outage occurs, one region out of every pair is prioritized to make sure at least one is restored as quickly as possible for applications hosted in that region pair.

⮚Planned Azure updates are rolled out to paired regions one

region at a time to minimize downtime and risk of application outage.

⮚Data continues to reside within the same geography as its pair.

 

  Availability Zones 

 

 

1. The region represents a separate geographic area.
2. An availability zone is a set of discrete data centers.
3. The availability zone is set up to be an isolation boundary. If one zone goes down, the other continues working.
4. Each availability zone has independent power, cooling, and networking.
5. Availability zones are connected via high bandwidth, ultra-low latency networking
6. AZS is physically separated by several kilometers while within 100 km (60 miles) of one each.
7. All AZ traffic is encrypted.
8. Not every region has support for availability zones.