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 backlog and also gives us insight into the potential impact of implementing the suggested feature.

Thanks for your suggestion. Currently, we don’t have anything planned in changing our billing meter from hour to minute. But will leave this request open and will include this in future planning discussions for our roadmap.

I initially thought the same, but came to the conclusion of "why not just throw an exception?"

EventGrid has a simple job and that is to keep trying to deliver the message to the subscriber until it is completed sucessfully.

EventGrid really doesn't care *why* your function failed, I assume it treats any non-200 response as a failure and will invoke retries until it completes successfully or the 24 hour retry period elapses.

My opinion but having to explicitly return a Type that defines the success is unnecessary in this particular binding, as the EventGridTrigger is abstracting you from the complications of returning success or failure state.

Being able to set defined 'amounts' when creating a subscription would be great.

A Developer might initially only pay for 10 requests a second, but then at some point in the future upgrade to 20, 30 or 40 requests a second.

Yes we could achieve this right now by having 5 different products, but this would mean the developer would have to reintegrate against the API with the new ocp-apim-subscription-key which is a bad experience for the developer.

Maybe the real answer here is to be able to migrate a subscription to a different products and preserve the ocp-apim-subscription-key?

"We actually will have something published shortly that will enable this with Logic Apps (some final testing underway on this), while the full API/policy based version of it will be shipped in CY18 per the current plan."