Unable to create App Service Plan in Azure Free Tier

Question

Hi Experts,

I'm unable to create an Azure App Service Plan, it is giving 429 Error

Plan specs:

• SKU: B1 (Basic)
• OS: Linux
• Region: Central India
• Subscription Type: Free Tier

Error Details:

{
    "status": "Failed",
    "error": {
        "code": "429",
        "message": "App Service Plan Create operation is throttled for subscription 9xxxxxxxxxxxxxx. Please contact support if issue persists.",
        "details": [
            {
                "message": "App Service Plan Create operation is throttled for subscription 99d8f8e9-1b37-4b2d-b102-416a5bc55c43. Please contact support if issue persists."
            },
            {
                "code": "429"
            },
            {}
        ]
    }
}

Answer 1

Hi @Ananay Ojha

Thanks for reaching out in Microsoft Q&A forum,

HTTP 429 message indicates that the Azure App Service Plan creation operation is currently being throttled for the subscription. The error is specifically returned for the Microsoft.Web/serverfarms create operation.

This error is commonly seen when multiple App Service Plan creation attempts, including failed attempts, are made within a short period. Once the create-operation threshold is reached, Azure temporarily throttles further App Service Plan creation requests for that subscription and region. Microsoft Q&A discussions with the same error message indicate that the throttle can remain in place for up to 48 hours and is region-specific.

For this reason, we recommend the following:

• Please stop retrying the App Service Plan creation for the moment. Repeated failed attempts can continue to trigger the throttle.
• Allow the throttle window to expire, which can take up to 48 hours based on the documented Microsoft Q&A guidance.
• After the waiting period, please make one new creation attempt in Central India.
• If your workload allows, you can also test the creation in another Azure region, as the reported throttle is scoped per region.
• If the issue continues after the waiting period with no additional creation attempts, please provide the Azure Activity Log entry for Microsoft.Web/serverfarms/write, including the timestamp and correlation ID, so the provisioning failure can be investigated further.

There is also one additional point we recommend checking. The subscription is described as Free Tier, while the requested App Service Plan SKU is B1 (Basic). Basic is a dedicated App Service tier, whereas Free is a shared tier. Therefore, please confirm the current subscription offer and spending-limit status as well, since subscription eligibility or offer limitations can independently prevent provisioning.

If this is a Free Trial subscription, you can run the following command and share the output (you may redact the subscription ID):

az account show

In particular, we would like to verify the subscription state, spendingLimit, and quotaId. This will help us determine whether the failure is solely due to the temporary create throttle or whether there is also a subscription-offer limitation.

For additional reference, please see the official Microsoft documentation:

• Azure Resource Manager request limits and throttling – Microsoft Learn
• Azure subscription and service limits – Microsoft Learn

Kindly let us know if the above helps or you need further assistance on this issue.

Please do not forget to and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Answer 2

Hello Ananay Ojha,

Greetings! Thanks for raising this question in the Q&A forum.

This 429 error is a rate limiting response, not a quota or region availability problem. It happens when Azure detects too many App Service Plan create or failed create attempts on a subscription within a short time window, and it applies to Free tier and other subscription types alike. Once triggered, the throttle typically blocks further App Service Plan creation for up to 48 hours, and the limit is applied per region, which is why you may still be able to create a plan successfully in a different region on the same subscription.

Here is how to work through it.

1. Wait before retrying. If you attempted creation multiple times in a row (including failed attempts), avoid retrying immediately. Retrying repeatedly resets or extends the throttling window rather than clearing it. Give it at least 24 to 48 hours since the last failed attempt in Central India before trying again.
2. Try a different region as a temporary workaround. Since the throttle is applied per region rather than subscription wide, you can attempt the App Service Plan creation in another nearby region such as South India, Central US, or East US to confirm your subscription itself is not blocked entirely, and to unblock your work while the Central India throttle clears.
3. Avoid recreating or deleting resources repeatedly. Do not delete and recreate resource groups or plans while troubleshooting this, since each additional failed attempt can extend the throttle window further.
4. Check Free tier specific limits. Azure Free tier accounts have a documented cap on the number of App Service Plans permitted per region on the Free SKU. Confirm you are not also running into that separate limit by reviewing the App Service Plan limits documented here: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#app-service-limits
5. If the throttle does not clear after 48 hours, raise a support request. Since this is a subscription level, platform side restriction and not something you can resolve through the portal UI or CLI, file a support ticket rather than continuing to retry:
   • Go to Azure Portal > Help + support > New support request
   • Issue type: Service and subscription limits (quotas)
   • Include your subscription ID 99d8f8e9-1b37-4b2d-b102-416a5bc55c43, the region (Central India), and the exact error message
   • Note that Free tier subscriptions have limited support plan coverage, so you may only be able to submit billing or subscription management requests rather than a technical support ticket. Subscription and quota requests are typically accepted even on Free tier.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix.