Increase the limit for Webhooks in ACR
The Webhook limits for both Basic and Standard service tiers are way too low, and also do not scale well with the increase in price.
Most solutions are composed of multiple images, we are forced to purchase "Standard" even for small apps.
I mean, what is the computational cost of an actual Webhook call? It should have a high limit and charge by actual function calls.
Basic $5 = 2 Webhooks
Standard $20 = 10 Webhooks
Premium $50 = 500 Webhooks
I would suggest at minimum that it should scale down based on the Premium, 5, 20 and 500 webhooks. But still seems low.
Webhooks should have "no limit" (or a high one) just as there is no limit for the number of images that we can create.
Can we have a discussion about why the Basic and Standard limits for Webhooks are so low? I would like to understand why the amount of webhooks, and not the actual calls, have influence in the price.
Evandro Pomatti commented
I would love to help test and validate a consumption plan for ACR.
About the current tiers, is it not possible to increase the webhook limits within those tiers? How much of a difference in cost would that imply?
I tried the email address but got no response.
Reshmi Mangalore [MSFT] commented
Thank you for your feedback. We have received similar comments from customers lately and are thinking about a consumption tier where customers will be billed proportional to their registry usage. The new consumption tier will have unlimited Web hooks and will scale per customer’s needs.
Today, the webhook limits that you are seeing in the pricing page were set as part of the three-tier pricing model. We acknowledge that the current model is not ideal for webhooks, and customers must switch to Premium tier for higher counts. The team is looking at consumption pricing to improve the experience. If you wish to talk further regarding consumption tier needs, please reach out to reshmim at microsoft.com.