Billing: do not charge for stopped (suspended) deployments.
Users do not have the expectation that once the deployment is suspended, it is somehow still on and running. Therefore, there should be no charge. No service is provided by Microsoft when deployments are in the suspended state.
Eugene Shustef
shared this idea
6 comments
-
Mark
commented
There should be two options (1) Suspended deployment where customer still pays full price as today and (2) Stopped deployment where the customer pays minimum charge for storage so that compute instance (CPU, memory, etc.) is freed up for others. With this option, it could take longer for to restart the instance as the worker/web role data would be copied back from storage to to an instance but it would be cheaper.
-
Anonymous
commented
Just lost $150 because of this...
-
JohnHadj
commented
Mike - You say that a compute instance is allocated to a stopped deployment. Why? Shouldn't it be swapped out to stop using resources?
-
David Zipkin
commented
Ryan Dunn, a Technical Evangelist on the Windows Azure team, has a blog post today that gives a bit more detail plus a helpful commandlet.
http://dunnry.com/blog/HowDoIStopTheBillingMeterInWindowsAzure.aspx
-
Here's what I found out Eugene. Even in a suspended state, the compute instance is still allocated to the customer. Therefore, it cannot be allocated to someone else. As such, compute time accrues to the customer. We are in the process of making the FAQ on this clearer in addition to what appears to the developer on the Dev portal.
-
Thanks for raising this Eugene, I'll raise it with the team and come back to you.
Mike
