Azure App Service Free F1 returns HTTP 403 and shows Quota exceeded with zero usage

Hossam Khedr 0 Reputation points
2026-11-14T19:06:36.06+00:00

A Linux Python 3.12 web app on Azure App Service Free (F1) in West US 3 returns HTTP 403 with the Azure message ‘This web app is stopped.’ Overview shows Quota exceeded. Start reports success, but the app returns to Quota exceeded and the default hostname still returns 403. The Quotas blade shows zero usage for CPU Time (Day), CPU Time (Short), Memory Usage, and Data Out. An earlier HTTP 503 had a startup shell quoting error, which was corrected in Stack settings before the latest Start attempts.

How can I identify which quota Azure is enforcing when the usage counters are zero? Is there a diagnostic view or log that shows the reason and reset time for this specific quota stop on F1?

Azure App Service
Azure App Service

Azure App Service is a service used to create and deploy scalable, mission-critical web apps.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Rukshan edirisinghe 2,930 Reputation points
    2026-11-15T03:39:38.9466667+00:00

    Hi @Hossam Khedr

    The Quotas blade only shows the current window. Once a counter resets it reads zero again, even though the app stays in the Quota exceeded state. There's no separate log that names the breached quota, but Metrics keeps the history, so that's the easiest place to see what tripped it.

    1. Open the App Service Plan (not the web app) and go to Metrics.
    2. Set the time range to the last 24 to 48 hours and add CPU Percentage, Memory Percentage and Data Out.
    3. Look for a spike around the time of your earlier 503 errors. A startup command that keeps failing makes the container restart in a loop, and on F1 that can burn through the daily CPU quota quickly.
    4. In the web app, go to Diagnose and solve problems > Availability and Performance and check for container restarts in the same window.
    5. If it was the daily CPU quota, it resets at midnight UTC. Start the app after that, now that the startup command is fixed.

    Do you see a spike in Metrics around the time the 503s were happening?

    If my response resolved your issue, please consider accepting it as the answer. If the issue persists, let me know and I'll be happy to continue helping.

    Reference:

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-14T19:07:41.7333333+00:00

    The authoritative view is Web App → App Service Plan → Quotas; if every chart now reads zero, Azure does not expose a separate documented F1 “quota-stop history” log that reliably names the previously breached counter, so use App Service diagnostics and Activity Log to capture the platform event before escalating.

    Identify the enforced quota

    1. Open the affected web app in the Azure portal.
    2. Select App Service Plan → Quotas.
    3. Expand and record every chart’s:
      • quota name
      • current limit
      • current value
      • Resets in value

    For Free and Shared plans, the relevant enforcement behavior is: ^1^

    Quota Enforcement and reset
    CPU (Short) Stops the app; resets every five minutes
    CPU (Day) Stops the app; resets at midnight UTC
    Bandwidth/Data Out Stops the app; resets at midnight UTC
    Memory Stops the app temporarily
    Filesystem Writes fail, including log writes; it does not match the documented quota-stop 403 behavior

    Exceeding CPU Short, CPU Day, or Bandwidth causes App Service to stop the app until reset, with incoming requests returning HTTP 403. The portal’s Resets in value is the documented indicator of the remaining enforcement period. ^2^

    A zero current value does not identify which counter caused an earlier stop. A closely matching F1 case reports that the displayed meter can reset to zero while the app remains in the exceeded/stopped state from the preceding measurement window. ^3^

    Capture platform diagnostics

    Because the corrected startup command concerns the earlier 503, application startup logs are not the primary evidence for this current platform-generated 403.

    1. Go to Web App → Diagnose and solve problems.
    2. Open Availability and Performance.
    3. Run:
      • App Down Workflow
      • Web App Down
      • CPU Usage
      • Memory Usage
      • Linux - Number of Running Containers
    4. Set the examined interval to include the first transition to Quota exceeded.
    5. Save screenshots or export the report, including timestamps and any detector finding.

    App Service diagnostics requires no prior logging configuration and is most useful for events from the previous 24 hours. ^4^

    Then open Web App → Activity log and filter around the same time for:

    • Restart Web App
    • Stop Web App
    • other administrative or resource-health events

    Activity Log is the monitoring surface for web-app resource operations; application logs and Log Stream are intended primarily for code/runtime output. ^5^

    Do not expect Python application logs to contain the quota rejection: requests blocked by the App Service front end do not reach the worker, and front-end failures are not recorded as back-end HTTP server errors. ^1^

    If the app remains stopped after the reset

    If CPU (Short) remains blocked beyond five minutes, or CPU (Day)/Bandwidth remains blocked after midnight UTC, capture:

    • subscription and resource identifiers
    • App Service plan name, F1 SKU, Linux, and West US 3
    • time the state first changed to QuotaExceeded
    • quota-chart screenshots showing zero usage, limits, and reset values
    • Activity Log events and correlation IDs
    • App Service diagnostic report
    • the successful Start operation followed by the immediate return to QuotaExceeded

    Open Help + support → Create a support request and select Web app down or reporting errors under Function or Web App (Windows and Linux). Ask support to identify the internal quota dimension and clear or explain the stale enforcement state. A regional SKU quota-increase request applies to failed plan creation or scaling, not to an already-created F1 app stopped by runtime CPU, bandwidth, or memory enforcement.

    If immediate recovery is required, scale the App Service plan above Free/Shared; Microsoft documents upgrading as the way to increase or remove these runtime quotas. ^1^


    References

    1. Azure App Service Quotas and Metrics - Azure App Service
    2. Error 403 - This web app is stopped message - Azure
    3. Web app free plan - Quota exceeded even tho quotas shows 0 usage - Microsoft Q&A
    4. Diagnostics in Azure App Service
    5. Monitor Azure App Service
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.