Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
We are unable to view paginated report in APP own data application. We are seeing the below error message
pbi.error:
code: "PowerBINotAuthorizedException"
status: 401
We are using Power BI Embedded A5 SKU and created a workspace, uploaded a sample report
Using service principal to generate embed token as well. Still unable to view the report. Please suggest what could be the issue
Solved! Go to Solution.
Thanks Stephen. I was able to figure out the issue.
The powerbi.bootstrap method isn't supported when embedding paginated reports. Commenting the bootstrap code solved the issue. I believe the app own data sample code needs a comment in place for the same.
Thanks,
Naresh
Thanks Stephen. I was able to figure out the issue.
The powerbi.bootstrap method isn't supported when embedding paginated reports. Commenting the bootstrap code solved the issue. I believe the app own data sample code needs a comment in place for the same.
Thanks,
Naresh
Hi Stephen,
Thank you for the response.
I have done the following steps.
1. Create app registration, configured Power BI Service API permissions and generated a new client secret
2. Create a new group in AAD and added the service principal to the group
3. In Power BI service added the new group to "Allow service principals to use Power BI APIs" setting
4. Create Power BI Embedded Capacity (SKU: A5, Gen 2)
5. Created workspace and assigned premium Capacity and app registration service principal id as admin
6. Enabled Gateway to connect to on-prem SQL server and uploaded paginated reports.
7. Used the App Own Data application to view the paginated report
Can you please let me know if I need to check any other settings
Thanks,
Naresh
Hi @Anonymous ,
Please refer to this troubleshooting article.
A fiddler capture may be required to investigate further. The required permission scope may be missing for the registered application within Azure AD. Verify the required scope is present within the app registration for Azure AD within the Azure portal.
Possibile reasons: 1.Wrong group ID 2.Unauthorized group
Best Regards,
Stephen Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.