Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hello all,
My local solution is a Power BI ASP.NET web app registered in Azure AD using a client secret and client id (Azure service principal with a App Owns Data model). It preforms the Power BI REST API call "export=client.Reports.ExportToFileInGroup(workspaceid, reportid, exportRequest)" but it is catching a 400 Bad Request error.
When I tried testing https://docs.microsoft.com/en-us/rest/api/power-bi/reports/exporttofileingroup TryIt workspace it executed the request with a 200 response using the same groupid and reportid in our Azure account.
When I tried testing https://api.powerbi.com/v1.0/myorg/groups/:groupid/reports/:reportid/ExportTo from Postman with the Bearer token retrieved from https://login.microsoftonline.com/:tenant/oauth2/token for our Registered App (used in the local solution) within that Azure workspace, the error remains the same --Bad Request.
I have my header set to "Authorization: Bearer #######" and "Content-Type: application/json" to match TryIt, with the body set as "{"format": "PDF"}".
When I have taken the Bearer token from the TryIt workspace, and used it in the Postman call, the error persists.
Why is this error persisting? Has anyone delt with this call before and recieved a similar issue?
@PowerBI @ExportTo
Solved! Go to Solution.
Hi @Anonymous,
I had to use Fiddler to get more information on the error. It has to do with effective identities that needed to be provided in the body for RLS.
The links were helpful when determing the body for the request in Postman for RLS, however more research was required for how to apply it in our ASP.NET web app.
This has been resolved now, thank you for your help.
Hi @SeSPowerBi ,
Please review the solution in the following threads, hope they can help you.
REST API for Power BI, Reports - Export To File giving error
400 Bad Request Error when embedding report
Get Reports REST api not working - Showing 400 Bad Request (see message 5 from v-jiascu-msft)
Best Regards
Hi @Anonymous,
I had to use Fiddler to get more information on the error. It has to do with effective identities that needed to be provided in the body for RLS.
The links were helpful when determing the body for the request in Postman for RLS, however more research was required for how to apply it in our ASP.NET web app.
This has been resolved now, thank you for your help.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
11 | |
6 | |
4 | |
2 | |
2 |
User | Count |
---|---|
4 | |
3 | |
3 | |
3 | |
3 |