Azue-VMs-OS

Which OS run on Azure VMS

  • Windows - You can run various server workload.
  • Linux.  You can run various flavors of Linux

As soon as you start your VM, Azure charges an hourly price that is based on the VM’s size and operating system. You are charged when the VM status is Running or Stopped, but you are not charged when the VM status is Stopped (Deallocated). For partial hours, Azure charges only for the minutes of use. If you create the VM with a VM image containing certain preinstalled software, additional hourly software charges may apply. Azure charges separately for storage for the VM’s operating system and data disks (temporary disk storage is free).

When you shut down (deallocate) or delete the VM from the Management Portal or by using Azure PowerShell, the VM is no longer charged.

To log on to the virtual machine, use Remote Desktop Connection for a Windows VM or a Secure Shell (SSH) for a Linux VM.

You can also use Windows PowerShell Remoting to connect to the VM, or create additional endpoints for other resources to connect to the VM.

If you’re familiar with Hyper-V, you might be looking for a tool similar to Virtual Machine Connection. Azure doesn’t offer a similar tool because console access to a virtual machine isn’t supported.

The images provided by Azure don’t have a pre-configured user name and password. When you create virtual machine using one of those images, you’ll need to provide a user name and password, which you’ll use to log on to the virtual machine.

For Windows virtual machines, one option is to use Azure Backup to back up files and folders from within the guest operating system.

An option that applies to both Linux and Windows virtual machines is to use the snapshot capabilities of blob storage. If you use this option, you’ll need to shut down the VM before doing any operation that relies on a blob snapshot. This saves pending data writes and puts the file system in a consistent state.

You can use Azure Virtual Network to extend your existing infrastructure. The approach you’ll use is like setting up a branch office. You can provision and manage virtual private networks (VPNs) in Azure as well as securely link these with on-premises IT infrastructure

 

Generally, you can start, stop, or restart your VM whenever you need to. However, Azure sometimes will restart your VM as part of regular, planned maintenance updates in the Azure datacenters. Unplanned maintenance events can also occur when Azure detects a serious hardware problem that affects your VM. In that case Azure automatically migrates the VM to a healthy physical machine, and will restart the VM. For information

If you have one or more VMs that are deployed as single instances (not grouped in an availability set), Azure proactively emails the subscription’s Service Administrator at least 1 week before planned maintenance because the VMs could be restarted at the same time during the update. Applications running on the VMs could experience downtime.

If you group two or more similar VMs in an availability set to provide redundancy, you ensure that during planned or unplanned maintenance, at least one VM can stay available. Azure also guarantees certain levels of VM availability for this configuration.

 





Articles in

Azue-VMs-OS    Azure-features    Azure-Storage    Big-data    Blob-storage    Cloud-Service    EventHubs    File-Storage    Hadoop-in-HDInsight    Queue-Storage