![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 69%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAJ%3C/text%3E%3C/svg%3E)
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 73%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERV%3C/text%3E%3C/svg%3E)
The app must either remain stopped until the exceeded F1 quota resets or be moved to a paid App Service tier to restore it immediately and prevent the same quota enforcement.
Identify the exceeded quota
In the Azure portal:
- Open App Services → valwithproof-.
- Select App Service Plan → Quotas.
- Inspect each chart’s Current value, Current limit, and Reset interval.
- Look for a quota whose current value has reached its limit.
For an F1 Free app, the relevant quotas are:
| Quota | Effect and reset behavior |
|---|---|
| CPU (Short) | F1 permits 3 CPU minutes per five-minute interval; resets every five minutes. |
| CPU (Day) | F1 permits 60 CPU minutes per day; resets at midnight UTC. |
| Bandwidth | Outgoing-bandwidth allowance; resets at midnight UTC. |
| Memory | The app is stopped temporarily when exceeded. |
| Filesystem | F1 storage is 1 GB. Exceeding it causes write failures, including logging failures, rather than the documented quota-stop behavior. |
The QuotaExceeded state and “Site Disabled” result most closely match CPU (Short), CPU (Day), Bandwidth, or Memory enforcement. App Service stops an app that exceeds CPU or bandwidth quota until reset; requests during that period receive an HTTP 403 response. A front-end or client can surface the unavailable site as HTTP 503. ^1^ F1’s documented CPU limits are 3 minutes per five minutes and 60 minutes per day. ^2^
Restarting cannot clear a consumed quota, so no further restart is needed.
Restore service
Choose one of these paths based on the Quotas chart:
- Wait for the displayed reset
- CPU (Short): up to five minutes.
- CPU (Day) or Bandwidth: until midnight UTC.
- Memory: the stop is temporary, but repeated exhaustion indicates that F1 is insufficient.
- After reset, the quota value should fall and the app should leave
QuotaExceeded.
- Upgrade the App Service plan
- Open the app’s App Service Plan and use its scale-up/pricing-tier option.
- Select an available Basic or higher Linux tier and apply the change.
- Confirm that the app returns to
Running, then test both its default URL and function endpoints.
Upgrading increases or removes the Free-tier quotas. Basic, Standard, and Premium plans use dedicated compute, and their applicable app quota is filesystem rather than the Free-tier CPU, memory, and bandwidth model. ^1^ Free and Shared tiers use shared compute and allocate CPU quotas to each app, whereas Basic and higher tiers use dedicated virtual machines. ^3^
If no quota chart is at its limit
If every quota is below its limit but the state remains QuotaExceeded after the displayed reset:
- Open App Service → Diagnose and solve problems.
- Run the Web app down or reporting errors detector and capture its results.
- Record:
- The quota charts and reset times.
- The app and plan resource IDs.
- Region and F1 Linux SKU.
- The
403.67 Site Disableddiagnostic event and its UTC timestamp.
- Create an Azure support request for the stale or unexplained quota state.
A Service and subscription limits (quotas) request is appropriate only if Azure reports that quota is unavailable for the requested resource or region; that is a deployment/capacity-quota condition, distinct from an existing F1 app consuming its runtime allowance. ^4^
References