Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
Hi Daniel Palowski,
Welcome to Microsoft Q&A,
The quota meter you're seeing in the Portal resets after the quota breach period expires. So by the time you look at it, the counter has already reset to zero, but the app is still in a stopped/exceeded state from the previous window. Under each quota you will see "RESETS IN X HOURS X MINUTES." If the quota is reached in the first hour of the measurement period, your site will be offline for the rest of that period until the quota resets.
The subscription-level quota view is the wrong place to look. You need the App Service Plan quota, which is different. To review the status of quotas and metrics that affect an app, go to the Azure portal, navigate to your app, and in the left menu select App Service Plan > Quotas. On each chart you can review the quota name, its reset interval, its current limit, and its current value.
Even though only you access the app occasionally, several background processes silently consume CPU time on the Free plan:
WebJobs or background tasks — Check WebJobs in your App Service and stop or disable any running jobs.
Application Insights/telemetry — If you have Application Insights configured, it sends telemetry continuously in the background, consuming CPU and bandwidth quota.
Health check probes or deployment slots — Any configured health check endpoints count against your quota.
Disable "Always On" Go to Azure Portal → Your Web App → Configuration → General Settings and set Always On to Off. This stops background keep-alive pings that waste CPU quota.
Please Upvote and accept the answer if it helps!!