Jesper Ravnsgaard
My feedback
-
544 votes
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
Jesper Ravnsgaard
supported this idea
·
-
3 votes1 comment · Azure Monitor-Application Insights » Metrics & charting · Flag idea as inappropriate… · Admin →Jesper Ravnsgaard
supported this idea
·
-
10 votes1 comment · Azure Monitor-Application Insights » Metrics & charting · Flag idea as inappropriate… · Admin →Jesper Ravnsgaard
supported this idea
·
-
100 votesplanned · 2 comments · Networking » Azure Front Door Service · Flag idea as inappropriate… · Admin →Jesper Ravnsgaard
supported this idea
·
-
2 votes0 comments · Azure Monitor-Application Insights » Availability Testing · Flag idea as inappropriate… · Admin →Jesper Ravnsgaard
supported this idea
·
-
9 votesJesper Ravnsgaard
shared this idea
·
-
10 votesJesper Ravnsgaard
supported this idea
·
-
1 vote0 comments · Azure Monitor-Application Insights » Metrics & charting · Flag idea as inappropriate… · Admin →
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
Jesper Ravnsgaard
shared this idea
·
-
2 votes0 comments · Azure Monitor-Application Insights » Metrics & charting · Flag idea as inappropriate… · Admin →
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
Jesper Ravnsgaard
shared this idea
·
-
3,251 votes
Quick update,
We have been considering all of the risks and investigating the steps required to ensure we implement this feature with high positive impact and low to no negative impact.
After this investigation we have decided we will enable Pay-As-You-Go customers the option to configure a spending limit on a Pay-As-You-Go subscription, with appropriate safeguards and measures to prevent both service abuse and production service failure.
We have not yet finished determining the details of what this feature will look like, nor do we have a timeline for release, but we have heard your voices and have added this feature to our backlog.
Thanks for your continued feedback,
-Adam (Azure Billing Team)
An error occurred while saving the comment
Hi Nick
Hard limits are absolutely required. Not having that option makes customers worried to the point of blocking adoption. I have seen this several times.
Valid production use cases for this very much exist, and it should be high on your teams list.
Feel free to reach out to me via the billing advisors group for more detail.