You’re offline. This is a read only version of the page.
28
I have a Power BI report in which I integrated Power Apps for CRUD operations. After that, I created a main Power Apps application where I added a Power BI visual and embedded the Power BI report.
For the regular embedded report, I only need to sign in once. After that, whenever I open the app, I no longer see the sign-in prompt.
However, for a specific use case, I needed to create a paginated report, which I also added to the Power Apps visual. But the report did not load properly, so I enabled the "AllowNewAPI" function in Power Apps.
After enabling it, every time I open the app, I get a sign-in prompt. How can I bypass this sign-in requirement?
Thanks for your detailed explanation — you're working with a fairly advanced integration scenario, and the behavior you're seeing is likely tied to how authentication tokens are handled when AllowNewAPI is enabled in Power Apps.
When you enable AllowNewAPI, Power Apps uses a newer rendering and API model that may:
This can result in repeated sign-in prompts, even if the user is already authenticated in the app.
Here are a few things you can try to bypass or mitigate the sign-in prompt:
Ensure your Power Apps and Power BI are both registered in Azure AD and configured to use Single Sign-On (SSO). Also:
Share
Report
All responses (
Answers (
Power BI ServiceReport.Read.AllDataset.Read.AllPaginatedReport.Read.All (if available)If you're embedding the Power BI report using a Power BI visual in Power Apps, consider switching to service principal-based embedding or embed tokens with the correct scopes. This avoids relying on user session cookies.
AllowNewAPI if Not Strictly NecessaryIf the paginated report can be rendered without AllowNewAPI, try disabling it and see if the sign-in prompt disappears. This is a good test to confirm the root cause.
Instead of embedding the paginated report directly, you could:
Ensure that:
