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)Anonymous commented
I would really want to have this feature as well. I don't see a problem when this is an opt-in feature and this cap is not enabled by default?
It's the user that gets to decide whether or not to activate this and he must accept the consequences of his decision. At least he will not be ruined when something goes wrong.
Stijn ClaeysAnonymous supported this idea ·