1

I'm looking at using the Azure Autoscaling Application Block, (or the site management equivalent) - it makes sense on a cloud system to scale according to demand... but there is one thing I don't understand.

The FAQ at the bottom of the Cloud Service Pricing Page warns that 

If my deployed instance is in the “stopped” state, do I still get billed?

Yes, a stopped instance still occupies the compute resource that powers the instance,
and therefore you still get billed. 
In order to stop billing, you need to delete your deployment.

So then, what benefit is there in implementing Autoscaling? I have read documentation and blogs... Am I completely misunderstanding something?

Michael Rodrigues
  • 5,057
  • 3
  • 25
  • 51
  • 1
    This is the distinction between "Stopped" and "Stopped (Deallocated)" as seen http://social.msdn.microsoft.com/Forums/en-US/f608528e-a9f8-45b3-8d23-4211168cc087/stopped-deallocated?forum=WAVirtualMachinesforWindows – Greg D Feb 25 '14 at 08:43

1 Answers1

2

At least for Cloud Services (PaaS offering from Windows Azure), when auto scaling kicks in it does not just turns off the deployed instances (Stopped state in Windows Azure terminology), it completely removes it from the pool. Since the VMs are completely removed from your application pool, you only pay for the instances which are running.

So proper utilization of auto scaling could result in not only better resource utilization but also results in cost savings.

Gaurav Mantri
  • 128,066
  • 12
  • 206
  • 241