Each VM will be charged as a different VM. It does not matter if is in the same availability zone or not.
The only thing not charged is the communication traffic between them if they are all in the same zone.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
One VM is deployed with 2 different Availability Zones (Zone1 & 2) which has created 2 instances.
Each VM will be charged as a different VM. It does not matter if is in the same availability zone or not.
The only thing not charged is the communication traffic between them if they are all in the same zone.
Hello, @Senthilnath TM !
Is it possible to add multiple VMs to a single Availability Zone? If yes, How many VMs can share same Availability Zone?
You can continue to add VMs to the Availability Zone of your choice as long as there are resources available however Availability Zones have a round trip latency of 2ms or less so there are few situations where you would want to give up the high availability in favor of even lower latency. Proximity placement groups provide lower latency if you have latency sensitive requirements.
Am I charged for additional compute resources when using Availability Zones?
When you create your VM resources, you will see that multiple VMs are created if you deploy to multiple Availability Zones. On the confirmation screen, your compute total will be updated to reflect the cost of the additional VMs:
Single VM deployment:
Multiple Availability Zone/VM deployment: