API Partition Refresh - Power Automate 403 Error

[cassidy]

Hello,

I'm starting to leverage Partition refreshing through the API and Power Automate, but getting a weird result:

The Flow shows as "Failed" with a 403 Error, yet it actually does kick off the Refresh of the Parition in Power BI Service as expected.

I'm doing it as Microsoft as documented with this call (those are not by groups/datasets)

POST https://api.powerbi.com/v1.0/myorg/groups/f089354e-8366-4e18-aea3-4cb4a3a50b48/datasets/cfafbeb1-8037-4d0c-896e-a46fb27ff229/refreshes

Any advice on avoiding the Failed result?

[Anonymous]

Hi @cassidy,

Have you tried to directly use the current account to invoke the API? AFAIK, 403 error normally means the server understands the request but refuses to authorize it. 

Please double-check the correlation credentials and scope settings to confirm you have permission to use these API.

Power BI REST APIs for embedded analytics and automation - Power BI REST API | Microsoft Learn

Datasets - Refresh Dataset - REST API (Power BI Power BI REST APIs) | Microsoft Learn

Regards,

Xiaoxin Sheng

[cassidy]

I've added all permissions I can find for Power BI Service under Azure API Permissions.

Since it did kick off the Refresh as intended, it's almost as if it Understands, Executes it, but then does not Authorize it after the fact.  Never seen this before.

I think I could literally use the Flow with the expected result on the Power BI Service side, and just live with a Failed state of the Flow itself.