PowerBI REST API throttling and 429 response - Invoke-PowerBIRestMethod for admin/dataset/datasource

[stty1244]

Hi,

we have a piece of PowerShell that until December 2024 was working quite happily retrieving dataources related to datasets via this PowerShell command :

Invoke-PowerBIRestMethod

and this url:

$URL = "https://api.powerbi.com/v1.0/myorg/admin/datasets/" + $datasetID + "/datasources"

It has been throttled after 252 requests since the end of December with the 429 'too many requests' response.

It was fine before then.

Is there anyway of getting this throttling removed i.e. set to pre December 2024 values? We are using a service principal with this - and I have tried other accounts that have the same issue. It appears to be only this request that is being affected by this.

Do I need to raise a call with Microsoft to resolve this?

I have noticed a couple of other questions about this - although they don't help me unfortunately. 

i.e.

https://community.fabric.microsoft.com/t5/Service/Power-Bi-api-throtteling-becoming-more-aggresive-h...

https://community.fabric.microsoft.com/t5/Issues/Power-BI-REST-API-new-limit-50-requests-per-hour-fo...

I note one can't do batching of json with this, I have put in a timer to slow it down but due to the huge number of datasources (8000) this request is now useless to us.

[v-pnaroju-msft]

Hi stty1244,

We are following up to check if your query has been resolved. If you have found a solution, kindly share it with the community to help others who may have the same issue.

If our response was helpful, please mark it as the accepted solution and give kudos. This will benefit the wider community.

Thank you.

[v-pnaroju-msft]

Hi stty1244,

We are following up to see if your query has been resolved. Should you have identified a solution, we kindly request you to share it with the community to assist others facing similar issues.

If our response was helpful, please mark it as the accepted solution and provide kudos, as this helps the broader community.

Thank you.

[v-pnaroju-msft]

Hi stty1244,

We wanted to check in regarding your query, as we have not heard back from you. If you have resolved the issue, sharing the solution with the community would be greatly appreciated and could help others encountering similar challenges.

If you found our response useful, kindly mark it as the accepted solution and provide kudos to guide other members.

Thank you.

[v-pnaroju-msft]

Hi stty1244,

We appreciate your response.Please continue to keep us informed about the issue.

Thank you.

[v-pnaroju-msft]

Thank you, @Deku ,for your response.

Hi @stty1244,

We would like to check if the solution provided by @Deku has resolved your issue. If you have found an alternative approach, we encourage you to share it with the community to assist others facing similar challenges.

If you found the response helpful, please mark it as the accepted solution and add kudos. This recognition benefits other members seeking solutions to similar queries.

Thank you.

[stty1244]

Thanks for the hint. I will have a look at this in the next week.

[Deku]

There is undocumented throttling. Best bet is to use the scanner API, takes a couple of mins to run and 4 API calls.

I have a example here

To get data sources you will set datasourceDetails to true

[stty1244]

Could it be a capacity issue?

https://learn.microsoft.com/en-us/fabric/enterprise/throttling