Its great to get a monthly bill telling us what WE owe Microsoft, but how do we then apportion that to all our clients if we are charging them for UL/DL/Table/Blob size? Even if we use a 'fair use' policy how can you measure fair use?. The only way right now is to take all the UL/DL traffic through your web role and count the packets !!! which means many $$$'s more on more web roles to handle the extra load, not to mention the inefficiency of not hitting the storage directly.

We need a way to view your azure accounts stats in the context of billing. I want a realtime update of how much my azure account has cost me so far for the month.

Currently, when you disable the spending limit, you cannot re-enable it. It would be great if we could set a custom spending limit.

Currently a co-admin cannot view the charges a subscription is creating. Only the finance person who setup the Azure account can see the charges throughout the month. If a co-admin does something bad, i.e. create a web-role with 20 instances, they can't catch this before the end of the billing cycle.

It makes sense that only service admins can maintain the financials on the account but it would be useful to let others see the current charges. Right now co-admins have to ask service admins to log in and check the account to make sure something isn't running amok.

Send my bill to my email every month

We recently reached our "spending limit" and after allowing our account to go past the limit were very surprised to find our Virtual Machines completely wiped! We now have lost vital customer data and days of work! Why can't you hold our data and deployments for 30 days or at least give us fair warning!!!! This is a horrible experience!

The historical CSV downloads are only useful for finding line items. They don't include monthly spending limits (for that type of account), and they make it really hard to do any visualization or trend analysis over arbitrary periods of time. The ideal setup would be to add controls to enable dynamic date range selection on the subscription usage summary page. It would also be great to see some graphs showing the various usage over time...instead of having to make customers roll their own Excel solution.

Subscribers need the ability to cap monthly spend to prevent unexpected overages. When the cap is nearing, the owner should be notified with the option of temporarily increasing the cap. If the cap is not increased, the VMs or web sites should be disabled (NOT DELETED) until the beginning of the next billing cycle.