exception 429 too many requests for Azure Cost Management API

Question

exception 429 too many requests for Azure Cost Management API

Anil Guliyaan 55

While fetching cost details using Azure Cost Management API

I am getting error “429 too many requests”

I have also implemented the following solution suggested by Azure community:

“retry after waiting for the time specified in the x-ms-ratelimit-microsoft.consumption-retry-after header”

I have implemented the logic to try 3 times with waiting and retry after time (given in subsequent response header)

But still post retry getting following exception logs from different tenant/subscriptions :

Error:Too Many Requests || Statuscode 429

HeadersPragma: no-cache session-id: e39f5aab-651d-4116-8e27-a2459f3565c5

x-ms-request-id: 5e3707a8-405c-416e-9173-61df08ce45b0

x-ms-ratelimit-remaining-microsoft.costmanagement-entity-requests: DefaultQuota:3

x-ms-ratelimit-remaining-microsoft.costmanagement-tenant-requests: DefaultQuota:19

x-ms-ratelimit-microsoft.costmanagement-clienttype-retry-after: 58

x-ms-ratelimit-remaining-microsoft.costmanagement-clienttype-requests: DefaultQuota:0

Error:Too Many Requests || Statuscode 429

HeadersPragma: no-cache session-id: d482db0f-72e9-4c68-888e-dd80cbffdd8f

x-ms-request-id: ac3fc7c8-f922-46fd-8d22-5cfb44cd2449

x-ms-ratelimit-remaining-microsoft.costmanagement-entity-requests: DefaultQuota:2

x-ms-ratelimit-remaining-microsoft.costmanagement-tenant-requests: DefaultQuota:18

x-ms-ratelimit-microsoft.costmanagement-clienttype-retry-after: 58

x-ms-ratelimit-remaining-microsoft.costmanagement-clienttype-requests: DefaultQuota:0

Error:Too Many Requests || Statuscode 429

HeadersPragma: no-cache session-id: c56fa2d3-3260-4828-bcde-6e0ca514bddb

x-ms-request-id: df13ad6f-e6c8-4376-a5c7-a911f0c622ff

x-ms-ratelimit-microsoft.costmanagement-entity-retry-after: 46

x-ms-ratelimit-remaining-microsoft.costmanagement-entity-requests: DefaultQuota:0

x-ms-ratelimit-remaining-microsoft.costmanagement-tenant-requests: DefaultQuota:14

x-ms-ratelimit-microsoft.costmanagement-clienttype-retry-after: 58

x-ms-ratelimit-remaining-microsoft.costmanagement-clienttype-requests: DefaultQuota:0

Please suggest a solution

Gérald Döserich 765 Reputation points

2023-08-03T12:07:56.73+00:00

It's just rate limiting from Microsoft. There is nothing else you can do other than wait and retry again.

Make sure no other service is accessing the API other than you as that may rate limit your service as well.
Anil Guliyaan 55 Reputation points

2023-08-03T17:20:29.3433333+00:00

Thanks @SadiqhAhmed-MSFT ,

I am using following APIs

https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.CostManagement/query?api-version=2021-10-01
https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.CostManagement/forecast?api-version=2021-10-01

as I mentioned I am requesting in following scenario
first I call cost query API I get the response header (429 and get the retry after time)

again hit the same query post wait the retry time

this I repeat recursively 3 times

in third time also same response with increased retry after time as I given the snap in above open thread

so, I want to know it there any other way we can increase the rate limit?
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-08T07:57:22.8266667+00:00

@Anil Guliyaan The rate limits are not specific to a user – and limits are shared with other callers/users in the tenant/account. We can recommend the right APIs if we understand what you are trying to achieve.

Receiving a 429 usually means that we had to protect our service from the caller. Of course, every case can have some recommendations (different calling patterns, different API to use, etc).

If you provide me with your tenant id and/or billing account and I can figure out your pattern and what you are trying to do and help accordingly.

For sending "tenant id and/or billing account" details, please send us an email at AzCommunity @ Microsoft dot com with subject: Attn: Sadiqh Ahmed with a link to this forum thread for context.
Anil Guliyaan 55 Reputation points

2023-08-10T06:40:22.4066667+00:00

Hi @SadiqhAhmed-MSFT ,

I have shared you an email

Please reply on that
MONICA RUIZ ROSARIO 0 Reputation points Microsoft Employee

2023-08-10T18:40:30.7733333+00:00

Hello, @SadiqhAhmed-MSFT I am facing the same problem posted here I am trying to submit a query to: "https://management.azure.com/subscriptions/subscriptionId/providers/Microsoft.CostManagement/query?api-version=2023-03-01" for only one subscription. However, since the first call, I get the "TooManyRequests" messages. Can you please help me figure out if I am doing something wrong?
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-14T07:35:35.64+00:00

@Anil Guliyaan I looked at the calling pattern for the tenant id “02cf-f8-48-20-a**b20****5b”, you are not making a lot of calls. You are being rate limited by our ClientType filter (which allows 2000 calls per minute per ClientType). And since you are not providing a ClientType in the request headers, you will share the number with ALL customers that don’t provide a ClientType.

In short, can you please provide a clientType value when making an api call.

Example:

“ClientType” : “AwesomeType”

PS: Please choose one type value for all your calls, that will help us investigate any issue you face in the future.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-16T05:22:37.33+00:00

@Anil Guliyaan Have you had a chance to see the previous response? If the suggestions were helpful, click “Accept Answer” and Up-Vote. Feel free to reach out to us if you've additional questions in this regard.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-17T07:29:22.19+00:00

@Anil Guliyaan We haven't heard back from you. Please reply if you have any questions in this matter and we will gladly continue the discussion.
Anil Guliyaan 55 Reputation points

2023-08-17T09:19:50.4766667+00:00

Hi @SadiqhAhmed-MSFT ,

sorry for delay reply,

this works for me , adding “ClientType” : “AwesomeType” in request header solved the issue.

thanks @SadiqhAhmed-MSFT

Awesome!!!,

Actually I have setup the daily polling and want to check for 2-3 days polling result and now no 429 error. Thanks for your support & prompt reply.
Dillon Silzer 57,831 Reputation points Volunteer Moderator

2023-08-18T04:08:48.7766667+00:00

As Gerald stated, you will have to wait. I have seen this error before and it usually clears after a couple of days.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-18T06:14:54.5066667+00:00

@Anil Guliyaan Thanks for the update! Glad to hear it is resolved :)

FYI: I have updated my post with more details and enabled the options to "Accept Answer" and "Up-Vote" the post. If my response helped answer your question, then I would request you to "Accept Answer and Upvote" so that the relevancy of this post will improve when anyone in the community search for a similar query.

@Anil Guliyaan We noticed your recent experience on the Q&A community platform was rated "Low". Thank you for taking time to share your feedback.

We are eager to know what could have been done better to evolve your experience to a "High" rating.

Your candid feedback is very important to us.

Looking forward to your reply.
BOURHISYvesGwenaelOBSCTIO-1234 0 Reputation points

2025-01-23T08:27:16.3966667+00:00

I have the same issue with azure-mgmt-subscription==3.1.1 in python.

The sdk ought to handle rate limiting otherwise it's clearly a bug in the sdk.

Accepted answer

1 additional answer

Your answer

Gérald Döserich 765 Reputation points

2023-08-03T12:07:56.73+00:00

It's just rate limiting from Microsoft. There is nothing else you can do other than wait and retry again.

Make sure no other service is accessing the API other than you as that may rate limit your service as well.
Anil Guliyaan 55 Reputation points

2023-08-03T17:20:29.3433333+00:00

Thanks @SadiqhAhmed-MSFT ,

I am using following APIs

https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.CostManagement/query?api-version=2021-10-01
https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.CostManagement/forecast?api-version=2021-10-01

as I mentioned I am requesting in following scenario
first I call cost query API I get the response header (429 and get the retry after time)

again hit the same query post wait the retry time

this I repeat recursively 3 times

in third time also same response with increased retry after time as I given the snap in above open thread

so, I want to know it there any other way we can increase the rate limit?
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-08T07:57:22.8266667+00:00

@Anil Guliyaan The rate limits are not specific to a user – and limits are shared with other callers/users in the tenant/account. We can recommend the right APIs if we understand what you are trying to achieve.

Receiving a 429 usually means that we had to protect our service from the caller. Of course, every case can have some recommendations (different calling patterns, different API to use, etc).

If you provide me with your tenant id and/or billing account and I can figure out your pattern and what you are trying to do and help accordingly.

For sending "tenant id and/or billing account" details, please send us an email at AzCommunity @ Microsoft dot com with subject: Attn: Sadiqh Ahmed with a link to this forum thread for context.
Anil Guliyaan 55 Reputation points

2023-08-10T06:40:22.4066667+00:00

Hi @SadiqhAhmed-MSFT ,

I have shared you an email

Please reply on that
MONICA RUIZ ROSARIO 0 Reputation points Microsoft Employee

2023-08-10T18:40:30.7733333+00:00

Hello, @SadiqhAhmed-MSFT I am facing the same problem posted here I am trying to submit a query to: "https://management.azure.com/subscriptions/subscriptionId/providers/Microsoft.CostManagement/query?api-version=2023-03-01" for only one subscription. However, since the first call, I get the "TooManyRequests" messages. Can you please help me figure out if I am doing something wrong?
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-14T07:35:35.64+00:00

@Anil Guliyaan I looked at the calling pattern for the tenant id “02cf-f8-48-20-a**b20****5b”, you are not making a lot of calls. You are being rate limited by our ClientType filter (which allows 2000 calls per minute per ClientType). And since you are not providing a ClientType in the request headers, you will share the number with ALL customers that don’t provide a ClientType.

In short, can you please provide a clientType value when making an api call.

Example:

“ClientType” : “AwesomeType”

PS: Please choose one type value for all your calls, that will help us investigate any issue you face in the future.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-16T05:22:37.33+00:00

@Anil Guliyaan Have you had a chance to see the previous response? If the suggestions were helpful, click “Accept Answer” and Up-Vote. Feel free to reach out to us if you've additional questions in this regard.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-17T07:29:22.19+00:00

@Anil Guliyaan We haven't heard back from you. Please reply if you have any questions in this matter and we will gladly continue the discussion.
Anil Guliyaan 55 Reputation points

2023-08-17T09:19:50.4766667+00:00

Hi @SadiqhAhmed-MSFT ,

sorry for delay reply,

this works for me , adding “ClientType” : “AwesomeType” in request header solved the issue.

thanks @SadiqhAhmed-MSFT

Awesome!!!,

Actually I have setup the daily polling and want to check for 2-3 days polling result and now no 429 error. Thanks for your support & prompt reply.
Dillon Silzer 57,831 Reputation points Volunteer Moderator

2023-08-18T04:08:48.7766667+00:00

As Gerald stated, you will have to wait. I have seen this error before and it usually clears after a couple of days.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-18T06:14:54.5066667+00:00

@Anil Guliyaan Thanks for the update! Glad to hear it is resolved :)

FYI: I have updated my post with more details and enabled the options to "Accept Answer" and "Up-Vote" the post. If my response helped answer your question, then I would request you to "Accept Answer and Upvote" so that the relevancy of this post will improve when anyone in the community search for a similar query.

@Anil Guliyaan We noticed your recent experience on the Q&A community platform was rated "Low". Thank you for taking time to share your feedback.

We are eager to know what could have been done better to evolve your experience to a "High" rating.

Your candid feedback is very important to us.

Looking forward to your reply.
BOURHISYvesGwenaelOBSCTIO-1234 0 Reputation points

2025-01-23T08:27:16.3966667+00:00

I have the same issue with azure-mgmt-subscription==3.1.1 in python.

The sdk ought to handle rate limiting otherwise it's clearly a bug in the sdk.

Answer 1

SadiqhAhmed-MSFT 49,331 Microsoft Employee Moderator

Hello @Anil Guliyaan Thank you for contacting us on Microsoft Q&A platform. Happy to help!

If the APIs in the below discussion are Query or Forecast, we have been seeing an increase in customers abusing the shared capacity and by that impacting the experience of other customers. Due to that, we revisited our rate limiting.

Here are the response headers that you should look for in case of a 429 response. They will tell you how long to wait before making the next call.

x-ms-ratelimit-microsoft.costmanagement-qpu-retry-after

x-ms-ratelimit-microsoft.costmanagement-entity-retry-after

x-ms-ratelimit-microsoft.costmanagement-tenant-retry-after

x-ms-ratelimit-microsoft.costmanagement-client-retry-after

The rate limits are not specific to a user – and limits are shared with other callers/users in the tenant/account. We can recommend the right APIs if we understand what you are trying to achieve.

Receiving a 429 usually means that we had to protect our service from the caller. Of course, every case can have some recommendations (different calling patterns, different API to use, etc).

I looked at the calling pattern for the tenant id “02cf-f8-48-20-a**b20****5b”, you are not making a lot of calls. You are being rate limited by our ClientType filter (which allows 2000 calls per minute per ClientType). And since you are not providing a ClientType in the request headers, you will share the number with ALL customers that don’t provide a ClientType.

In short, can you please provide a clientType value when making an api call.

Example:

“ClientType” : “AwesomeType”

PS: Please choose one type value for all your calls, that will help us investigate any issue you face in the future.

Hope this helps. Please write back if you need any further assistance!

If the response helped, do "Accept Answer" and up-vote it

magnus jakobsen 0 Reputation points

2023-10-17T12:44:45.1633333+00:00

Hi @SadiqhAhmed-MSFT

Could you also link to the documentation showing the use of the 'ClientType' header? I can't seem to find it.

Regards,
Magnus
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-10-17T13:41:35.29+00:00

@magnus jakobsen Thanks for the feedback. I request you to kindly leverage the feedback section from the document link to share your feedback. This would help us triage the request to the content team and get it updated appropriately.
magnus jakobsen 0 Reputation points

2023-10-18T07:21:30.05+00:00

Uuhm, so, are you confirming that there's no documentation that explains the use of the 'ClientType' header?
I'm not even sure which documentation page this should be placed in
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-10-18T12:17:00.4866667+00:00

@magnus jakobsen You can leave feedback on this document - https://learn.microsoft.com/en-us/rest/api/cost-management/
Sahaj Khandelwal 25 Reputation points

2023-11-21T15:46:28.14+00:00

Hi,
From Postman, I noticed if I pass x-ms-command-name header, it doesn't throw 429 after a lot of requests as well, but as soon as I remove that, it starts throwing 429 after 5 requests. (for some time).

How do I pass this header when using Azure Java SDK for cost management API?
Sahaj Khandelwal 25 Reputation points

2023-11-22T03:15:59.0166667+00:00

Hi, when making call to azure cost management API, after exactly 5 API calls in quick succession, I start getting 429.
But if I add the header x-ms-command-name with any value, it gives 200 all the time.

My question is, if I am using azure cost management API from azure SDK for java, how can I do this?
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-11-23T09:30:08.18+00:00

@Sahaj Khandelwal May I know which API are you calling?

Also, provide us at least the URL endpoint that you are calling.
Sahaj Khandelwal 25 Reputation points

2023-11-24T03:08:13.37+00:00

I am using
https://management.azure.com/subscriptions/xxxxx/providers/Microsoft.CostManagement/query?api-version=2023-03-01&$top=5000

If for some reason, adding the x-ms-command-name makes it work, is it possible that this can be added to azure java SDK here?
https://github.com/Azure/azure-sdk-for-java/blob/azure-resourcemanager-costmanagement_1.0.0-beta.6/sdk/costmanagement/azure-resourcemanager-costmanagement/SAMPLE.md#benefitrecommendations_list
Sahaj Khandelwal 25 Reputation points

2023-11-24T03:17:56.1733333+00:00

If you want, we can connect over teams. I can share screen recording with you
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-11-24T10:32:29.5733333+00:00
@Sahaj Khandelwal Please share the detailed information about the call:

The tenant Id.

The SPN object id or application id that you used to call the API.

According to my knowledge, there is no way this request header could fix the 429 error, so we need to take a look at your calling pattern recently and see if there is some fix in your calling pattern other than this request header.

If this x-ms-command-name can help in Query API’s rate limit, which I don’t think so. We only require you to use ClientType request header to avoid ClientType rate limit.
Sahaj Khandelwal 25 Reputation points

2023-11-24T14:00:58.0033333+00:00

Is this the right forum to share these details? If not, we can connect over email or teams.

And I can share the recording in case you want, where I have precisely captured this.

I triggered the API without this header, and exactly the 5th time it fails with 429 (I do have clienttype header for all my tests).

When done with x-ms-command-name, it works all the way. I tried 25 calls in 30 seconds.

Though I do understand where you are coming from, maybe that's the way it is supposed to be, I found a similar doc elsewhere mentioning the same as you.

Internal limits
o 4 calls per minute per scope
o 20 calls per minute per tenant
o 2000 calls per minute per ClientType
Anil Guliyaan 55 Reputation points

2023-11-24T14:25:20.7466667+00:00

@Sahaj Khandelwal

you just need to append request header with “ClientType” as key and value as random string like “awesome123” for each different client Id and you are done.
Sahaj Khandelwal 25 Reputation points

2023-11-24T14:29:47.2333333+00:00

I tried it many times in last 3 days, this header does not work for me.

Tried random string as value to clienttype, ClientType etc etc
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-11-28T07:12:43.9033333+00:00

@Sahaj Khandelwal Please send us an email at AzCommunity @ Microsoft dot com with subject: Attn: Sadiqh Ahmed with your subscription ID and a link to this forum thread for context.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-11-29T07:31:21.61+00:00

@Sahaj Khandelwal We haven't heard back from you. Please reply if you have any questions in this matter and we will gladly continue the discussion.
Anil Guliyaan 55 Reputation points

2023-11-29T17:00:11.21+00:00

@Sahaj Khandelwal

okay , you should retry to hit the api post waiting the time(in seconds) given in response header(x-ms-ratelimit-microsoft.costmanagement-clienttype-retry-after or x-ms-ratelimit-microsoft.costmanagement-entity-retry-after ) when you will get 429 error.

e.g. when you get the error 429 first time then you find the response header

x-ms-ratelimit-microsoft.costmanagement-clienttype-retry-after=5

or

x-ms-ratelimit-microsoft.costmanagement-entity-retry-after=5

then just wait for 5 seconds and hit again

Thread.Sleep(5 * 1000);

this solution was provided by MS community it self.

.
Sahaj Khandelwal 25 Reputation points

2023-11-30T04:49:31.57+00:00

Got in touch with MSFT premium support.

I was using the token that I got from the Azure portal (by trapping from network call). With that token and this header, it was working without any limits.

But with the one we generate programmatically, it doesn't work since there is a limit of 4 calls per scope per minute. It was confusing because this limit is not there in Azure portal token, but that's understandable considering Azure won't keep a limit for its own portal.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-11-30T13:39:13.8666667+00:00

@Sahaj Khandelwal Glad to know that the issue is resolved. Thanks for sharing the solution with the community.
Broeder, drs. N. den (Nico) DOMC 5 Reputation points

2024-02-23T10:38:35.5066667+00:00

@Sahaj Khandelwal Same result: Adding header X-Ms-Command-Name: CostAnalysis solved the issue. Adding ClientType header does not change anything.
Muralidharan Selvaraj 15 Reputation points

2024-02-26T05:57:11.9333333+00:00
How to get this done for Azure SDK ?

client = CostManagementClient(credentials) result = client.query.usage(scope=scope, parameters=query)
Muralidharan Selvaraj 15 Reputation points

2024-02-26T05:58:36.35+00:00
How to get this done for Azure SDK ?

client = CostManagementClient(credentials) result = client.query.usage(scope=scope, parameters=query)

@SadiqhAhmed-MSFT

Answer 2

Broeder, drs. N. den (Nico) DOMC 5

Same result as @Sahaj Khandelwal Adding this header solved the issue: X-Ms-Command-Name: CostAnalysis Adding the ClientType header does not make any difference.

Muralidharan Selvaraj 15 Reputation points

2024-02-26T05:56:48.59+00:00
How to get this done for Azure SDK ?

client = CostManagementClient(credentials) result = client.query.usage(scope=scope, parameters=query)
Sergey Khomyuk 0 Reputation points

2025-05-30T09:44:47.7566667+00:00

Did you use the X-Ms-Command-Name and ClientType with Azure Portal token or your own? It seems, that it works for Azure Portal token only, but does not work for another token.

Share via

exception 429 too many requests for Azure Cost Management API

1 additional answer

Your answer