Freeze (archive) resources by group
For developer scenarios, it would be useful to have the ability to "freeze" a resource group -- retain the configuration information and any file/data storage, but eliminate all runtime/processing overhead (and access). I realize this implies adding this capability all the way down the resource stack.
Storage charges are often fairly minimal, so this would allow us to avoid lengthy or complex export/store/upload/restore scenarios for archiving experiments, POCs, or even when we just need to switch gears and focus on some other resource group.
Not to turn this into a rant, but I preface this with "for developer scenarios" because that $150 MSDN credit doesn't go very far. I can't imagine trying to evaluate Azure for more than tinkering-curiosity on the more restricted dev plans. I'm pushing an $1 billion division of a Fortune 50 company for Azure adoption, but having to micro-manage my credit-spend (or suffer a freeze-out every couple weeks) during my evaluation phase is getting tedious.