Feedback on azure costs
Your feedback is very important for us and we really appreciate your help to make our service better. Please submit new ideas, comment or vote existing ones. As soon your idea becomes real we set the record to implemented and the result is visible in the Azure Costs Monitor.
If you want to submit a support call or if you have trouble with the system please use the contact form on this page or send an e-mail to tickets@azurecostsmonitor.uservoice.com.
26 results found
-
Quota management per subscription
being able to set a dollar spend threshold per subscription and then be able to view usage and consumption to date vs. the yearly threshold per subscription
1 vote -
Notify or enforce tag values not allowed to contain common metadata strings
We ran in to an issue pulling and parsing our Azure billing data where values in our tags contained strings that matched other billing field names. And that cause our parsing to get confused and fail. A warning about the strings matching other metadata field names in the tag documentation or upon deployment would be great. Enforcement to not allow matching strings would be even better.
1 vote -
Allow for grouping on multiple levels
When displaying the list grouped by subscriptions it would be helpfull if information on a lower level could also be grouped by another level (for example subscription) so things would like like :
Cost Center1
Subscription1
Services
Subscription2
Services
Cost Center21 vote -
Possibility to track cost between specific dates
Please make it possible to track cost between two specific dates rather than the monthly billing cycle or MOnth-to-Date only.
1 vote -
Alerts on cost deviations from a 'baseline'
Cost monitor is able to see the daily expenditure of a subscription, so it should be able to automatically calculate some kind of baseline. With this information it should be possible to send out an email alert if a subscription is spending a lot more money all of a sudden (because somebody left 10 big test VMs running for example).
1 voteThe base line makes totally sense and should be coupled with our prediction.
-
Allow to archive & merge EA contracts
During the renewal process around an EA contract it could happen that customers get a new EA number. Azure Costs should offer two the option to archive and merge an EA contract into a new one.
The archived EA will not synced any more and no daily e-mail reports will send out. The merged one contains all the historic information so a seamless spending management of the migrated subscriptions is possible.
1 vote
- Don't see your idea?