Microsoft Azure AZ-103 Tips,Hints and Notes Part 3

Today in this Part i will list some important notes related to Deploy and Manage Virtual Machine and the previous parts check it here ➡️ Part 1 Manage Azure Subscription ➡️ Part 2 Implement and Manage Storage

For more information about other Azure posts and articles, all of them are collected in one link ➡️ HERE ✅

Manage Azure VM Articles

Deploy and Manage Virtual Machine Tips

When you redeploy a VM it Moves the VM to a new node within the Azure Subscription and then powers it back on, retaining all your configuration options and associated resource, the VM will be deployed by new resource ID. And After you redeploy a VM, the temporary disk is lost and dynamic IP addresses associated with virtual network interface are updated https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/redeploy-to-new-node-windows
You can use a template that allows you to deploy a simple Windows VM by retrieving the password that is stored in a key vault, therefore, the password is never put in plain text in the template parameter file https://azure.microsoft.com/en-us/resources/templates/101-vm-secure-password/
Virtual Machine Scale Sets can be used with the Azure Desired State Configuration (DSC) extension handler. Virtual machine scale sets provide a way to deploy and manage large numbers of virtual machines, and can elastically scale in and out in response to load. DSC is used to configure the VMs as they come online so they are running the production software https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-dsc
A DNS server listens for requests on port 53 (both UDP and TCP)
While resizing the VM it must be in a stopped state. https://azure.microsoft.com/en-us/blog/resize-virtual-machines/
Deleting the VM does not delete the backup. Azure will still attempt to backup the deleted VM but the backup will fail as the target will be missing and is still registered to the recovery vault. The backup needs to be stopped and then after that, the already backed up material can be removed/deleted from the vault before the vault itself can be deleted https://azure.microsoft.com/en-in/updates/azure-vm-backup-policy-management/
You can’t delete a Recovery Services vault if it is registered to a server and holds backup data. If you try to delete a vault, but can’t, the vault is still configured to receive backup data. https://azure.microsoft.com/en-in/updates/azure-vm-backup-policy-management/
IF you need to monitor the metrics and the logs of a Linux virtual machine you Should use Linux Diagnostic Extension (LAD) 3.0 https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/diagnostics-linux
To Find and delete unattached Azure managed and unmanaged disks Use Microsoft Azure Storage Explorer You can find unused disks in the Azure Storage Explorer console. Once you drill down to the Blob containers under a storage account, you can see the lease state of the residing VHD (the lease state determines if the VHD is being used by any resource) and the VM to which it is leased out. If you find that the lease state and the VM fields are blank, it means that the VHD in question is unused. The screenshot below shows two active VHDs being used by VMs as data and OS disks.The name of the VM and lease state are shown in the “VM Name” and “Lease State” columns, respectively https://cloud.netapp.com/blog/reduce-azure-storage-costs
Azure Monitor can collect data directly from your Azure virtual machines into a Log Analytics workspace for detailed analysis and correlation. Installing the Log
Analytics VM extension for Windows and Linux allows Azure Monitor to collect data from your Azure VMs. And Azure Log Analytics workspace is used for on-premises computers monitored by System Center Operations Manager https://docs.microsoft.com/en-us/azure/azure-monitor/learn/quick-collect-azurevm
IF You have 3 VM are hosted in the same availability set and you need to resize one VM from the 3 VMs you need to stop the 3 VM first to do this action (The reason all VMs in the availability set must be stopped before performing the resize operation to a size that requires different hardware is that all running VMs in the availability set must be using the same physical hardware cluster. Therefore, if a change of physical hardware cluster is required to change the VM size then all VMs must be first stopped and then restarted one-by-one to a different physical hardware cluster.) https://azure.microsoft.com/es-es/blog/resize-virtual-machines/
IF you have a VM and you need to Configure a backup on it and You discover that the Backup Pre-Check status displays a status of Warning at this time probably VM does not have the latest version of WaAppAgent.exe installed. (Warning: This state indicates one or more issues in VM’s configuration that might lead to backup failures and provides recommended steps to ensure successful backups. Not having the latest VM Agent installed, for example, can cause backups to fail intermittently and falls in this class of issues) https://azure.microsoft.com/en-gb/blog/azure-vm-backup-pre-checks/
IF you have VM connected to VNET1 and you need to connect the VM to another VNET2 in another region >> you should delete VM. then recreate VM again, and then you add the network interface VNET2 for VM https://docs.microsoft.com/en-us/azure/virtual-machines/windows/network-overview
When you create an Azure virtual machine (VM), you must create a virtual network (VNET) or use an existing VNET. You can change the subnet a VM is connected to after it’s created, but you cannot change the VNET https://docs.microsoft.com/en-us/azure/virtual-machines/windows/network-overview
IF you have two VMs VM1 and VM2 both VM connected to VNET1 and the 3 resources hosted in the same region and you need to inspect all the traffic from VM1 to VM2 for some time at this time we can use Connection time monitor feature of Azure network watcher https://azure.microsoft.com/en-us/updates/general-availability-azure-network-watcher-connection-monitor-in-all-public-regions/
To create a vault to protect virtual machine the vault must be in the same region as the virtual machine
VNET Virtual network is required when you create NIC Network interface, and you can only assign NIC to VNET that exists in a same subscription and location as the Network interface, add in your note once the NIC created you cannot change the VNET it is assigned to also the VM you add the NIC to it should be in the same location and subscription of the NIC. https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface