Forum Discussion
Helper IUnable to refresh Power BI admin report in services
Hi Team,
I have built a Power BI admin report for my organization that uses Power BI REST APIs to retrieve organization-wide information, including workspaces, datasets, reports, refresh schedules, and refresh history.
The solution uses Service Principal authentication for all API calls.
The report refreshes successfully on my local machine in about 30 minutes. However, when published to the Power BI Service, the refresh takes 3–4 hours and eventually fails with an authentication error.
Has anyone experienced a similar issue or found a way to improve the refresh performance in the Power BI Service? Any suggestions or best practices would be greatly appreciated.
Thank you!
AdityaPrasad
In your case i would suggest thatService Principal → Fabric Notebook / Pipeline → Power BI REST APIs → Fabric Lakehouse → Power BI Semantic Model → Admin Report
Run the extraction, for example, every 30 minutes or hourly, and maintain historical data in the Lakehouse.
Then your Power BI refresh becomes a modest query against the Lakehouse rather than execution organization-wide REST API discovery during the refresh.
This should improve both refresh performance and dependability, while also allowing you to build historical analytics around Power BI usage, refresh failures, workspace growth, and capacity utilization.
If this helps, ✓ Mark as Kudos | Help Others
4 Replies
Murtaza_GhafoorSuper User
AdityaPrasad
In your case i would suggest thatService Principal → Fabric Notebook / Pipeline → Power BI REST APIs → Fabric Lakehouse → Power BI Semantic Model → Admin Report
Run the extraction, for example, every 30 minutes or hourly, and maintain historical data in the Lakehouse.
Then your Power BI refresh becomes a modest query against the Lakehouse rather than execution organization-wide REST API discovery during the refresh.
This should improve both refresh performance and dependability, while also allowing you to build historical analytics around Power BI usage, refresh failures, workspace growth, and capacity utilization.
If this helps, ✓ Mark as Kudos | Help Others- GilbertQ
Hi AdityaPrasad
If you are using Power BI Pro, there is a 2 hour limit in terms of how long a query can run for before it will be canceled. If you are using Power BI premium per user or fabric capacity, there's a 5 hour limit in terms of how long a query can run for and that is why you're probably getting the error. What I would recommend is to separate each part into an individual query. That way the time will be reset each time the new API is called.
v-kathullacCommunity Support
Thankyou GilbertQ , Murtaza_Ghafoor for Addressing the issue.
Hi AdityaPrasad ,
Thank you for reaching out to Microsoft Fabric Community Forum,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
Regards,
Chaithanya
- v-kathullac
Thankyou @GilbertQ , @Murtaza_Ghafoor for Addressing the issue.
Hi @AdityaPrasad ,
Thank you for reaching out to Microsoft Fabric Community Forum,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
Regards,
Chaithanya
