Do all requests to Azure App Configuration subtract count towards the quota or only those requests that result in your app's configuration being updated ?

Question

The Azure App Configuration FAQ implies only requests that result in configuration values being updated in running apps count toward the request quota. https://learn.microsoft.com/en-us/azure/azure-app-configuration/faq#how-should-i-store-configurations-for-multiple-environments--test--staging--production--and-so-on-

Is this true or do all requests contribute against the quota?

Answer 1

@Ryan Taylor ,

I see that you have posted the same query in the below github thread and App config team has answered your query. Providing the answer here so that it helps others in the community

Reference : https://github.com/Azure/AppConfiguration/issues/716

1. Billing: All successful requests count towards the daily usage. 200,000 requests per day are included with the daily charge. Anything above that is overage.
2. Quota limits: That applies only to throttling. 30,000 requests per hour (read+write) is the minimum guaranteed at the moment. Note that frequent read requests (sentinel key check, burst loading/refresh, etc.) are often intentionally excluded from that limit. That in practice allows for way more than 30,000 requests per hour. The reason for that is to prevent unexpected quota depletion and subsequent persisted HTTP 429 (Too Many Requests) for application deployment, startup, restarts, refresh or monitor for changes, caused by multiple instances in a short period of time.
   The more we stay out of your way, the better.