Operation throttled for subscription

Brett M 1 Reputation point

I am building an azure devops release pipeline to deploy infrastructure with ARM files. Being an agile person, I am iteratively building the ARM file and not adding everything in one go and praying that it works. I started with creating a resource group, then app service only to realise I needed a service plan. I had some mistakes in my arm file and attempted it a few times. Possibly about 20 redeploys over a few hours.

"Now I get errors of XYZ update operation is throttled for subscription <guid>. Please contact support if the issue persists." e.g. App Service Plan Update operation throttled, but I do get it for others as well. I have waited 24 hours but still, get the error.

I lodged a ticket, but responded with an "its a severity 3 and take 3 business days". EXCUSE ME!! My business development is halted and I cannot buy and pay for azure services because I made approximately 20 changes over a few hours

How do I get this revolved as a PAYING CUSTOMER and small business!! This kind of thing just destroys small startup businesses.

Azure Monitor
Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
2,787 questions
{count} votes

2 answers

Sort by: Most helpful
  1. AnuragSingh-MSFT 19,686 Reputation points

    Hi @Brett M and @Ciprian Pintilei ,

    Welcome to Microsoft Q&A! Apologies for the delayed response.

    I see that you are running into throttling issue for operations in Azure subscription. Please note that Throttling happens at two levels. Azure Resource Manager throttles requests for the subscription and tenant. If the request is under the throttling limits for the subscription and tenant, Resource Manager routes the request to the resource provider. The resource provider applies throttling limits that are tailored to its operations. For more details, please refer to: Throttling Resource Manager requests

    Also, you may please refer to this link to understand the behavior and error returned when you reach limit. The response header values (especially the Retry-After) will be of immense help to analyze such situation. The link mentioned above, also contains a section on returned header values and how to retrieve them, to be able to make decisions accordingly.

    In case you frequently run into this issue with understandably simple operations, I would request reaching out to our support team so that the operation may be analyzed for assistance.

    Please let me know if you have any questions.

    Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.

    0 comments No comments

  2. Brett M 1 Reputation point

    Your answer only mentions that requests may be throttled and indicates when throttling is removed. It however does not address the problem.

    In my case, the throttling is not because of high volumes which is not the case. There were approximately 10-20 in total.

    Here is what really happens, when you create a new subscription you can only create a few resources. This restriction stays in effect for 48 hours.

    The correct answer is "NEW SUBSCRIPTIONS ARE THROTTLED IN THE FIRST 48 HOURS". The only thing one can do is wait it out.

    Perhaps this policy should be reviewed, especially for loyal customers. Treating every new subscription as potentially fraudulent is not a good start to building relationships.

    Gooday from a good customer that was treated like a criminal!