Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Hi,
We are trying to refresh a PowerBI dataset from a background service that runs without a signed-in user.
We have registered a PowerBI App in the Azure portal and assign it with the Tenant.ReadWrite.All Application permission.
In PowerBI we have added the app as the Service Principal for the workspace and enabled all the Admin API settings in the admin page.
The following C# code is throwing a throw 403 Forbidden error. Note that we are using the Microsoft Authentication lib for .NET (MSAL.NET) to generate an access token and the Microsoft.PowerBI.Api lib to interact with the PowerBI API.
IConfidentialClientApplication confidentialClientApplication = ConfidentialClientApplicationBuilder
.Create(clientId)
.WithClientSecret(secret)
.WithTenantId(tenantId)
.WithAuthority(AzureCloudInstance.AzurePublic, tenantId)
.Build();
AuthenticationResult authResult = await confidentialClientApplication.AcquireTokenForClient(
new string[] {https://analysis.windows.net/powerbi/api/.default}).ExecuteAsync();
TokenCredentials tokenCredentials = new(authResult.AccessToken, "Bearer");
PowerBIClient pbClient = new(tokenCredentials);
await pbClient.Datasets.RefreshDatasetAsync(datasetId); // throw 403 - Forbidden
What are we missing?
Hi @erandavid ,
Does this blog post help you? 🙂
Let me know! 🙂
/Tom
https://www.tackytech.blog/
https://www.instagram.com/tackytechtom/
Did I answer your question❓➡️ Please, mark my post as a solution ✔️ |
Also happily accepting Kudos 🙂 |
Feel free to connect with me on LinkedIn! | |
#proudtobeasuperuser | |
Thanks Tom for your reply.
It didn't help but I made some progress - I manged to refresh the dataset by creating a token via the UsernamePasswordCredential class and enabling the "Allow public client flows" for the registerd app in the Azure portal.
This is still not good enough since this solution require to provide the username and password of an actual user...
What I would like is to use the app secret instead to create a token (like this: var tokenCredential = new ClientSecretCredential(tenantId, clientId, secret);) , but when I do that I get the 403 Forbidden error.