Public URL embedded in Sharepoint risk?

Hi, our company has Office 365 and uses Sharepoint. There is a Sharepoint component option to embed a website code and use the Publish to web URL to open it in Sharepoint to all Office 365 users. What are the risks to doing this vs the Embed in Sharepoint Online option and using the Sharepoint Power BI embed code?

Re: Public URL embedded in Sharepoint risk?

Publish to web allows users without a Power BI license to view the content as well. Simply because all security is removed from the content and the URL is public, everybody can see it.

For the publish to web feature, there is a feature which allows you to embed your Power BI report within the same Office365 tenant in SharePoint Online. This is a great way of embedding your reports in a portal or some other cool SharePoint stuff. Because Power BI, SharePoint and all other Office365 services are using the same accounts, things like row-level-security will still work.

One disadvantage of this way of embedding, is that you have to grant permission to the SharePoint site and the Power BI content separately. So, you have to take multiple steps to grant access to a user. To make this work automatically, you can use Active Directory groups, which are used for SharePoint Access and for Power BI access both. In that case you only have to add the right users to the AD group to grant access on all levels.

On license side, you have to make sure that every user who has access, does have a Power BI Pro license as well. Another option could be a Power BI Premium view-only consumer license.

Re: Public URL embedded in Sharepoint risk?

Publish to web allows users without a Power BI license to view the content as well. Simply because all security is removed from the content and the URL is public, everybody can see it.

For the publish to web feature, there is a feature which allows you to embed your Power BI report within the same Office365 tenant in SharePoint Online. This is a great way of embedding your reports in a portal or some other cool SharePoint stuff. Because Power BI, SharePoint and all other Office365 services are using the same accounts, things like row-level-security will still work.

One disadvantage of this way of embedding, is that you have to grant permission to the SharePoint site and the Power BI content separately. So, you have to take multiple steps to grant access to a user. To make this work automatically, you can use Active Directory groups, which are used for SharePoint Access and for Power BI access both. In that case you only have to add the right users to the AD group to grant access on all levels.

On license side, you have to make sure that every user who has access, does have a Power BI Pro license as well. Another option could be a Power BI Premium view-only consumer license.