Linux Virtual Machines Pricing

No. All new virtual machines have an operating system disk and a local disk (or “resource disk”). We don’t charge for local disk storage. The operating system disk is charged at the regular rate for disks. See all virtual machines configurations.

Read our Azure Reserved Virtual Machine Instances FAQ.

You can find more information about spot virtual machines on our website.

A temporary disk is storage that’s attached directly to the deployed VM. Data on a temporary disk is lost once the VM is shut down. If you need persistent storage, there are a number of types and sizes of persistent data disks available that are charged separately. Please see storage pricing for information. For persistent VM storage, we recommend that you use Managed Disks to take advantage of better management features, scalability, availability, and security.

Maybe. If the status says “Stopped (Deallocated),” you’re not being billed. If it says, “Stopped Allocated,” you’re still being billed for allocated virtual cores (not the software license itself). Full details on virtual machine states are available on the documentation page.

Virtual machine prices include local disk storage only. You can see the cost to attach Premium (SSD based) and Standard (HDD based) disks to your virtual machines on the Managed Disks pricing page.

Previously, all usage for A0, A2, A3, and A4 Standard and Basic virtual machines was emitted as fractions (for A0) or multiples (for A2, A3, and A4) of A1 virtual machines meter minutes. We heard this caused some confusion for our customers, so we’ve implemented a change to assign per-second usage to dedicated A0, A2, A3, and A4 meters. Because of this transition, the resource GUIDs for A0, A2, A3, and A4 virtual machines will change. If any of your billing routines rely on the resource GUIDs, they’ll need to be modified to take these new billing meters into consideration.

We charge for the number of full minutes your virtual machine is running, so you are not billed for any extra seconds. In this example you would be billed for 6 minutes.

It’s a new preview feature for Azure Virtual Machines with private IP addresses. The internally load-balanced endpoint is only accessible within a virtual network (for virtual machines within a virtual network) or cloud service (for virtual machines outside a virtual network). Internal load balancing is useful for multi-tier applications where some of the application tiers aren’t public facing yet require load balancing functionality.

You can check the status of your virtual machines in the Virtual Machines tab, and also in the virtual machine Dashboard. If virtual machine status says "Stopped," you’re still being billed. Only "Stopped (Deallocated)" indicates you’re not being billed.

To ensure you’re not being billed, always stop virtual machines from the management portal. You can also stop the virtual machine through Powershell by calling ShutdownRoleOperation with "PostShutdownAction" equal to "StoppedDeallocated".

Each instance is charged for its data egress across regions.

No. Tax will be added separately.

As you transition your workloads to Azure, take advantage of Azure Hybrid Benefit to reuse your existing Windows Server licenses with Software Assurance or Windows Server subscriptions for significant savings. For each license, Azure covers the cost of the OS, while you pay for just the VM compute costs. Additionally, through Azure Hybrid Benefit for Linux, you can use your pre-existing on-premises Red Hat and SUSE software subscriptions on Azure. Learn more.

The H series and NC series promos are no longer available and normal H series and NC series instances will we decommissioned soon. The promo virtual machines already deployed will continue to run until the associated H series and NC series decommission dates. Please read the H series migration guide and NC series migration guide for additional information and next steps.