QandA: When do I get charged for compute hours on Windows Azure?

January 19, 2010 · 1 min read

This question keeps coming up. Hence I will have a stab at explaining it.

Nothing deployed = no charge

First I think we can all happily agree that the following service on Windows Azure won’t be costing me anything :)

image

Deployed and running and being used = charge

If we have code deployed and being used then you will be charged. Seems reasonable. Note that Staging and Production cost the same.

image

Deployed and running but no one is using it = charge

You will be charged even if no one is using your service. Presumably because they have something better to do :-)

image

Deployed but Stopped/Suspended = ?

In this case I have suspended Production and Staging. Staging is Stopped and Production is Stopping.

Will you be charged? The answer is Yes. This will be charged exactly the same as Deployed and running.

It is not sufficient to suspend a service – you need to actually delete it to avoid being charged.

image

I hope that helps. I am definitely keen to hear your feedback on any of the above.

This article is part of the GWB Archives. Original Author: Eric Nelson

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.