App Service Plan Create operation is throttled

Question

App Service Plan Create operation is throttled

Liu, Yansong 11

I'm trying to create a web app on azure today. However, the creation was failed with error code 429. I tried three times and the problem persists.

I read several other posts about this error code. All the answers suggest that this throttling is for the free SKU. However, I got the same error message when I deploy a paid SKU (B1). I know there is another limit for reads and writes per day. I have only tried four times today to create web app services (all failed). There should be no read/write restrictions. Also, there is no 'retry after ' value in the error message. I have no idea how long this is gonna last (already last more than 24 hours).

the error message asks me to contact support. However, the support is paid and I don't want to pay 29 dollars just to get this problem fixed. What do I need to do guys?

Error message:
{
    "status": "Failed",
    "error": {
        "code": "429",
        "message": "App Service Plan Create operation is throttled for subscription **********. Please contact support if issue persists.",
        "details": [
            {
                "message": "App Service Plan Create operation is throttled for subscription **********. Please contact support if issue persists."
            },
            {
                "code": "429"
            },
            {}
        ]
    }
}

Liu, Yansong 11 Reputation points

2022-01-12T10:28:00.157+00:00

Just tried to deploy a more expensive paid instance SKU P3V3 and got the same error code and message. SKU P3V3 costs over 400 pounds per month, which apparently is not a free tier machine. I have no idea why I'm throttled.
Ryan Hill 30,336 Reputation points Microsoft Employee Moderator

2022-01-12T20:20:13.737+00:00

What region are you deploying to @Liu, Yansong .? Do you have the same issue if you deploy to different regions?
Liu, Yansong 11 Reputation points

2022-01-13T02:17:39.767+00:00

Yes, you are right. The problem appears to be region and subscription-related. When I was using my pay-as-you-go subscription, I couldn't create new services in East Asia (regardless of the tier), but I could in Korea South. But when I switch to my student starter subscription, I can create new free services in East Asia.
Mark Chidlow 1 Reputation point

2022-05-16T09:53:01.88+00:00

I am getting this same issue. I have raised a ticket with support but have not received a response in the last 3 days. I cannot wait 48 hours every time I get this error. I am setting up 2 new environments each with 8 service plans. Please advise.
Ryan Hill 30,336 Reputation points Microsoft Employee Moderator

2022-05-16T12:45:53.003+00:00

@Mark Chidlow email us your support request number to AzCommunity[at]microsoft[dot]com ATTN: Ryan so we can follow up with your support case. Having said that, when deploying a large number of resources, it's best to do it chucks and have a short period in between deployments. The 429 error response will include a Retry-After value in seconds on when you can retry the deployment. Please see Throttling Resource Manager requests for more details.

2 answers

Your answer

Liu, Yansong 11 Reputation points

2022-01-12T10:28:00.157+00:00

Just tried to deploy a more expensive paid instance SKU P3V3 and got the same error code and message. SKU P3V3 costs over 400 pounds per month, which apparently is not a free tier machine. I have no idea why I'm throttled.
Ryan Hill 30,336 Reputation points Microsoft Employee Moderator

2022-01-12T20:20:13.737+00:00

What region are you deploying to @Liu, Yansong .? Do you have the same issue if you deploy to different regions?
Liu, Yansong 11 Reputation points

2022-01-13T02:17:39.767+00:00

Yes, you are right. The problem appears to be region and subscription-related. When I was using my pay-as-you-go subscription, I couldn't create new services in East Asia (regardless of the tier), but I could in Korea South. But when I switch to my student starter subscription, I can create new free services in East Asia.
Mark Chidlow 1 Reputation point

2022-05-16T09:53:01.88+00:00

I am getting this same issue. I have raised a ticket with support but have not received a response in the last 3 days. I cannot wait 48 hours every time I get this error. I am setting up 2 new environments each with 8 service plans. Please advise.
Ryan Hill 30,336 Reputation points Microsoft Employee Moderator

2022-05-16T12:45:53.003+00:00

@Mark Chidlow email us your support request number to AzCommunity[at]microsoft[dot]com ATTN: Ryan so we can follow up with your support case. Having said that, when deploying a large number of resources, it's best to do it chucks and have a short period in between deployments. The 429 error response will include a Retry-After value in seconds on when you can retry the deployment. Please see Throttling Resource Manager requests for more details.

Answer 1

Bryan Trach 17,842 Microsoft Employee Moderator

@Liu, Yansong I wanted to follow up and verify that the 429 error occurs when you have too many deployments/failed deployments of an app service plan within a short period of time. This causes the system to throttle any additional deployments for the next 48 hours. This limit is per region, which is why you were able to use other regions or subscriptions.

If this occurs, you will need to wait 48 hours to complete a deployment in that region or contact support to see if they will remove the throttle.

Please let us know if there are further questions or concerns.

DiggityDog 15 Reputation points

2024-01-29T02:26:02.4+00:00

NOT helpful. If your services aren't working, and I have to delete them and start over, and you block me for 48 hours, that makes me want to go use some other company's software.
Vasko Boshkov 15 Reputation points

2024-05-16T14:53:41.6+00:00

This is a complete nonsense. Why should I wait 48 hours? I can not deploy my Azure Functions because of this. How to explain to the client this kind of nonsense? Azure MUST find a way to fix this!
Muhammad Rehan 15 Reputation points

2024-05-23T01:54:02.6766667+00:00

Besides the fact that this is absolute non-sense, why don't you guys at least mention this as a notice? I can keep seeing upselling offers but why miss this important point?

Also, ASP are being created again and again because the "Wordpress for Azure" template keeps failing again and again.

In essence I have to wait for 48 hours to deploy in the region my client needs because Azure is throttling my requests due to failures of template azure provides for deploying wordpress for azure?

by the way what is the the limit / region ?

what is "too many requests", how many are too many?
What is "short period of time", 1 hour, 2 hours. I am pretty sure my requests didn't go over 10 in last 12 hours.
Nicholas Johnson 10 Reputation points

2024-05-28T20:10:09.6+00:00

Wow, so I had a couple of issues with my function app pipeline script not generating correctly, deleted and recreated four times over a 12 hour period, and now the account is throttled for 48 hours? What the hell am I supposed to do now? What am I supposed to tell my clients?
Michaela Zimmer 5 Reputation points

2024-11-04T13:48:06.0366667+00:00

I have just tried to create 8 (eight, not eighty!) App Service Plans via a Terraform script in Germany West Central.

After completing five, I received the described error.

Re-running the script for the remaining three received the same response.

Does this mean that we now need to manually check, retry and possibly delay our IaC-based deployments by two days for each batch of 5 ?!

Especially as this was no development test instance, this is a release redeployment of a major customer's production system!

How are we supposed to tell that to our customer?!

"Things like this just happen with Azure"?
Anh thi DINH 0 Reputation points

2024-12-05T22:38:32.0333333+00:00

Same, why we need to wait for upto 2 days just because we created a few app services? I removed all previous ones.

Answer 2

Simon Jacob 0

The same thing occured for me at a first time deployment. 48h throttle with no understandable reasoning? I have to say, that is not exactly customer friendly.

0 comments