Azure VM bills based on the amount of time the VM is active. This time is measured in minutes, hours, days, or weeks.
The billing cycle for Azure VM starts on the first day of the month and ends on the last day of the month. If the last day of the month falls on a weekend or holiday, the billing cycle ends on the following business day.
Azure VM billing is prorated on a daily basis.
A VM is billed for the amount of time that it has been active during the billing cycle. The amount of time the VM has been active is measured in minutes, hours, days, or weeks.
If a VM is inactive for more than 30 minutes during a billing cycle, it is suspended and is not billed. If the VM is inactive for more than 7 days during a billing cycle, it is suspended and is not billed.
If a VM is moved from one subscription to another, the time that the VM is active is counted from the date that the VM is moved.
If a VM is deleted, the time that the VM is active is counted from the date that the VM is deleted.
If a VM is restarted, the time that the VM is active is counted from the time that the VM is started.
If a VM is deleted and then restored, the time that the VM is active is counted from the time that the VM is restored.
If a VM is migrated to Azure Resource Manager, the time that the VM is active is counted from the time that the VM is migrated.
If a VM is moved to a different subscription, the time that the VM is active is counted from the date that the VM is moved.
A VM is not billed for the following periods:
– Days that a VM is suspended for inactivity
– Days that a VM is in hibernation
– Days that a VM is in a state where it is not running or accessible
– Days that a VM is in a state where it is running but is not accessible
– Days that a VM is in a state where it is not running or accessible and it is not in use by any applications
– Days that a VM is in a state where it is not running or accessible and it is in use by a single application
– Days that a VM is in a state where it is running or accessible and it is in use by multiple applications
A VM is not billed for the following periods:
– Days that a VM is suspended for inactivity
– Days that a VM is in hibernation
– Days that a VM is in a state where it is not running or accessible
– Days that a VM is in a state where it is running but is not accessible
– Days that a VM is in a state where it is running but is not accessible and it is not in use by any applications
– Days that a VM is in a state where it is not running or accessible and it is in use by a single application
– Days that a VM is in a state where it is running or accessible and it is in use by multiple applications
– Days that a VM is in a state where it is running or accessible and it is in use by a single application and the VM is not in the same subscription as the applications that are using it
– Azure Active Directory Domain Services (AD DS) hours
A VM is not billed for the following periods:
– Azure Active Directory Domain Services (AD DS) hours
– Days that a VM is in a state where it is not running or accessible and it is in use by a single application and the VM is not in the same subscription as the applications that are using it.
