Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi all,
I've built a report in pBI, but would like to publish it in on a website.
https://docs.microsoft.com/nl-nl/power-bi/collaborate-share/service-publish-to-web
In this link it is stated: "You need to be a Microsoft Power BI user to use Publish to web. Your report viewers don't need to be Power BI users."
But the next link mentions "To view the embedded report, users need either a Power BI Pro license or the content needs to be in a workspace that's in a Power BI Premium capacity (EM or P SKU)."
Thanks for your feedback!!
Would be much appreciated!!
Solved! Go to Solution.
Hi @Anonymous ,
Embed a report in a secure portal or website and Publish to web are different.
1.Embed a report in a secure portal or website: To view the embedded report, users need either a Power BI Pro license or the content needs to be in a workspace that's in a Power BI Premium capacity (EM or P SKU).
2.Publish to web: You need to be a Microsoft Power BI user to use Publish to web. Your report viewers don't need to be Power BI users.
The URL used for Publish to Web has an embed code (not an embed token) at the end which provides anonmyous access. That means that Publish to Web works without requring any form of user authentication. If you have the URL with the embed code at the end, you are able to view the report. That's why we say the Publish to Web is inherently insecure.
Power BI embedding, on the other hand, will always require authentication with Azure AD. Today, Power BI embedding requires that a specific user with enough permissions to authenticate to acquire an access token. The access token is passed back to the browser for embedding when using first-party embedding and the user-owns-data model. With third-party embedding, the access token is used to call to the Power BI Service API to retrieve an embed token, and it is the emebd token not the access token which is then passed to the browser.
Reference: Power BI Embedded vs Publish to Web
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.
Hi @Anonymous ,
Sorry to disturb you...
But did I answer your question ? Please mark my reply as solution. Thank you very much.
Best Regards,
Stephen Tao
Hi @Anonymous ,
Embed a report in a secure portal or website and Publish to web are different.
1.Embed a report in a secure portal or website: To view the embedded report, users need either a Power BI Pro license or the content needs to be in a workspace that's in a Power BI Premium capacity (EM or P SKU).
2.Publish to web: You need to be a Microsoft Power BI user to use Publish to web. Your report viewers don't need to be Power BI users.
The URL used for Publish to Web has an embed code (not an embed token) at the end which provides anonmyous access. That means that Publish to Web works without requring any form of user authentication. If you have the URL with the embed code at the end, you are able to view the report. That's why we say the Publish to Web is inherently insecure.
Power BI embedding, on the other hand, will always require authentication with Azure AD. Today, Power BI embedding requires that a specific user with enough permissions to authenticate to acquire an access token. The access token is passed back to the browser for embedding when using first-party embedding and the user-owns-data model. With third-party embedding, the access token is used to call to the Power BI Service API to retrieve an embed token, and it is the emebd token not the access token which is then passed to the browser.
Reference: Power BI Embedded vs Publish to Web
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.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.