Azure App Service stuck in QuotaExceeded — HTTP 503 and Site Disabled

Question

Azure App Service stuck in QuotaExceeded — HTTP 503 and Site Disabled

Abhishek Jyothi 0

My Azure Web App valwithproof- in resource group ValWithProof-RG is unavailable. The app state remains QuotaExceeded, and the website returns HTTP 503. Diagnostics show HTTP 403 with substatus 67: “Site Disabled (quota enforcement or stopped).”

Restarting the app did not resolve the issue. The App Service plan is F1 Free on Linux in India South Central. Please help identify the quota causing this state and the steps to restore service.

REDDIMALLA VENKATESH 0 Reputation points Microsoft External Staff

2026-10-21T14:21:10.0166667+00:00

Hello @Abhishek Jyothi ,
Thank you for reaching out to Microsoft Q&A.

Based on the information provided, the application is hosted on the Free (F1) App Service plan and is currently showing a QuotaExceeded state. The Free tier has resource quotas such as CPU, memory, bandwidth, and filesystem limits.

Could you please check the Quotas section for the App Service and confirm which quota has reached its limit, along with the current usage?

If the applicable quota has been exhausted, depending on the quota, you may need to wait for it to reset or consider upgrading the App Service plan to increase or remove the applicable quota restrictions.

Please share the quota details or a screenshot of the Quotas section (with any sensitive information removed), and we can assist you further.

Hope this helps. Please let us know if you have any further questions.

Please "Upvote the Answer" if this information helped you. This will help us and others in the community as well.
REDDIMALLA VENKATESH 0 Reputation points Microsoft External Staff

2026-10-22T12:10:03.3766667+00:00

Hello @Abhishek Jyothi ,
I hope you are doing well!

I’m following up on your issue and wanted to check whether you had a chance to review the provided answer. Please let us know if it was helpful or not so we can assist you further with your query

2 answers

Your answer

REDDIMALLA VENKATESH 0 Reputation points Microsoft External Staff

2026-10-21T14:21:10.0166667+00:00

Hello @Abhishek Jyothi ,
Thank you for reaching out to Microsoft Q&A.

Based on the information provided, the application is hosted on the Free (F1) App Service plan and is currently showing a QuotaExceeded state. The Free tier has resource quotas such as CPU, memory, bandwidth, and filesystem limits.

Could you please check the Quotas section for the App Service and confirm which quota has reached its limit, along with the current usage?

If the applicable quota has been exhausted, depending on the quota, you may need to wait for it to reset or consider upgrading the App Service plan to increase or remove the applicable quota restrictions.

Please share the quota details or a screenshot of the Quotas section (with any sensitive information removed), and we can assist you further.

Hope this helps. Please let us know if you have any further questions.

Please "Upvote the Answer" if this information helped you. This will help us and others in the community as well.
REDDIMALLA VENKATESH 0 Reputation points Microsoft External Staff

2026-10-22T12:10:03.3766667+00:00

Hello @Abhishek Jyothi ,
I hope you are doing well!

I’m following up on your issue and wanted to check whether you had a chance to review the provided answer. Please let us know if it was helpful or not so we can assist you further with your query

Answer 1

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 2

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 Disabled diagnostic 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