Azure Administration

 What is an Azure Spot Virtual Machines / Spot instance?

• Azure Spot offers unused Azure capacity at a discounted rate versus pay-as-you-go prices. Azure can take capacity back whenever it needs, the Azure infrastructure will evict Azure Spot Virtual Machines.
• The amount of available capacity can vary based on size, region, time of day, and more. When deploying Azure Spot Virtual Machines, Azure will allocate the VMs if there is capacity available, 
• there is no SLA for azure spot VMs. 
• Azure Spot Virtual Machine offers no high availability guarantees. 
• At any point in time when Azure needs the capacity back, the Azure infrastructure will evict Azure Spot Virtual Machines with 30 seconds' notice.

Eviction type:

Eviction policy

What is the difference between generation 1 and generation 2 VM's

• generation 1 and generation 2 VM are now available in azure, you need to consider the generation of VM before it gets deployed, once VM is created you can't change a virtual machine's generation.
• The main difference between azure VM gen1 and gen2 is boot architecture Generation 1 VM use BIOS-based architecture whereas Generation 2 VMs use the new UEFI-based boot architecture 
• we can extend/create OS disk up to 2TB in generation 1 VM's but disk can be extended/created beyond 2TB when we use generation 2
• There is no cost difference between Gen1 and Gen2 VM's

Frequently asked questions

Happy learning

 What is a subscription?

what is a Resource group?

what is a Region?

Describe Availability Options? 

What is an Availability set?

What is an Availability zone?

What is a virtual machine scale set?

what is fault domain and update domain?

Explain about the Security type comes under VM creation? 

https://docs.microsoft.com/en-us/azure/virtual-machines/trusted-launch

Read about Availability set Overview:: 

Read about VM SLA: 

What is an availability set?

An availability set is a logical grouping of VMs that allows Azure to understand how your application is built to provide for redundancy and availability. We recommended that two or more VMs are created within an availability set to provide for a highly available application and to meet the 99.95% Azure SLA. There is no cost for the Availability Set itself, you only pay for each VM instance that you create.

What is the fault domain? 

there will be so many servers residing on data centers, all these servers will be placed on racks, each rack will have its own power supply and network switch we can call each rack a fault domain.

fault domain can fail at the same time and the root cause will same.

What is the updated domain? 

The updated domain is a group of resources that can be maintained/rebooted at the same time. only one updated domain can be rebooted at a time. there will be 30 mins maintenance time difference between the two updated domains.

SLA for Virtual Machines

 Create a virtual machine

Project details

1. Subscription 

2. Resource Group

Instance details

3. Virtual machine name

4. Region - 

5. Availability options - Azure offers a range of options for managing availability and resiliency for your applications. Architect your solution to use replicated VMs in Availability Zones or Availability Sets to protect your apps and data from datacenter outages and maintenance events.

• Availability options - 

1. Availability Zone - Physically separate your resources within an Azure region.
2. Virtual machines scale set - Distribute VM's across zones and fault domains at scale.
3. Availability Set - Automatically distribute your VM's across multiple fault domains.

• Create availability set:

1. What is fault domain? - Virtual machines in the same fault domain share a common power source and physical network switch.

2. What is update domain? - Virtual machines in the same update domain will be restarted together during planned maintenance. Azure never restarts more than one update domain at a time.

6. Inbound port rules

Select which virtual machine network ports are accessible from the public internet. You can specify more limited or granular network access on the Networking tab.

https://k21academy.com/microsoft-azure/az-303/azure-availability-zones-and-regions/

https://www.pragimtech.com/blog/azure/azure-tutorials-for-beginners/

What is Azure Resource Manager?

Azure Resource Manager is the deployment and management service for Azure. It provides a management layer that enables you to create, update, and delete resources in your Azure account. 

How resource manager plays a role?

If a user sends a request from any of the Azure tools, APIs, or SDKs, the Resource Manager receives the request. It authenticates and authorizes the request. The resource Manager sends the request to the Azure service, which takes the requested action.

what is the benefit of using Resource Manager?

You can manage your infrastructure through declarative templates rather than scripts.

All the resources for your solution can be deployed, managed, and monitored as a group rather than handling these resources individually.

you can redeploy and define the dependencies between resources.

Credit Refer: 

 What is a Resource group?

• A resource group is a collection of resources that share the same lifecycle, permissions, and policies.
• Resource group - A container that holds related resources for an Azure solution. The resource group can include all the resources for the solution, or only those resources that you want to manage as a group. You decide how you want to allocate resources to resource groups based on what makes the most sense for your organization
• Each resource can exist in only one resource group.
• When creating a resource group, you need to provide a location for that resource group. You may be wondering, "Why does a resource group need a location? And, if the resources can have different locations than the resource group, why does the resource group location matter at all?" The resource group stores metadata about the resources. When you specify a location for the resource group, you're specifying where that metadata is stored. For compliance reasons, you may need to ensure that your data is stored in a particular region. 
• If the resource group's region is temporarily unavailable, you can't update resources in the resource group because the metadata is unavailable. The resources in other regions will still function as expected, but you can't update them.
• You can deploy up to 800 instances of a resource type in each resource group.