Forum Discussion
PBI Embedded App Owns Data - Export Data from visual to Excel fails with 403 Forbidden error
Hi,
My team is building a web app with embedded Power BI reports using the app-owns-data method with service principal authentication.
One key feature for our users is the ability export data from a visual to Excel. Clicking the ellipsis > Export data function on a visual displays the Export Data dialog box, but when the "Excel" option is chosen, the resulting file is not downloaded to the browser. Note the "CSV" option does work as expected.
F12 devtools indicate the service endpoint (https://wabi-canada-central-redirect.analysis.windows.net/export/xlsx) returns a 403 Forbidden error with response message "API is not accessible for application".
Can anyone on the forum advise what the issue is here?
Thanks,
Craig
7 Replies
- AnonymousNot applicable
Note that exporting to Excel works perfectly well from the demo app shown here:
- AnonymousNot applicable
I have same issue. If I authenticate as a user I can do both. As a service principal, only csv works. The difference in the way how it does it:
https://wabi-canada-central-redirect.analysis.windows.net/export/xlsx
for excel and this one for csv
https://wabi-canada-central-redirect.analysis.windows.net/explore/querydataI suspect that my service principal is missing some permissions but can't figure out which one.
- AnonymousNot applicable
In my case the issue was caused by using Service Principal account. According to the support, this option has been in preview and will be GA sometime in May.
- AnonymousNot applicable
Hi Anonymous
Apologies for not replying back sooner...
Yes! My team just got back to looking at this problem last week and we were able to make it work by removing the Service Principal authentication and using Master User method instead. Not ideal, but at least it works.
Thanks for relaying the news that Service Principal will be GA later this month. Will keep my eyes open for the announcement.
Cheers,
Craig
- KuladeepAdvocate II
Anyone help me here!
Is this still a limitation with SPN? or is the erport function working with SPN auth?
How to activate that feature?
We are also facing same issue with embedded reports when authenticating with SPN. And our reports are in Directlake mode.