Forum Discussion
Solved
Embedding - Difference between using Power BI API vs Share button
Hello,
I have been trying to understand what are the differences between using the Power BI API to embedded reports/dashboards/visuals, etc, and using the Share option in apps, which gives the option to embed in sharepoint or in a web page.
All the info I read seems to point to the API, but then I don't understand the advantage of it versus the Share option, which seems faster and simpler. Can you help me understand, because I haven't seen it anywhere fully explained? I seek to implement the option that has better performance.
Thank you.
Best regards,
André
Hi. Sure, let's see.
- Share secure code: it's a limited cheaper version. This options will let you create an extension of any report to share with another user. Both users must have pro to check it or stored in Premium with Free. This option enforce a Azure AD login. It's almost the same thing as getting inside Power Bi Service.
- Power Bi Embed API: this is much more flexible but you have to pay for capacity. Once you pay for Power Bi Embed capacity in azure, you can get this option. This solution let you handle almost everything in the front end. You can get report, dashboard, tile, visuals. You can set filters before loading the embed. You can add a lot of options like exporting or printing. There two ways to develop this. One is letting your App security to Microsoft Azure AD (meaning you need a company email to get in, I think you don't need PBI license). Two is embeding without asking the users the microsoft login. That last option is the strongest one. You can build your own login and share big time with external users removing the idea of license by user (you are already paying capacity).
I hope that make sense.
2 Replies
Hi. Sure, let's see.
- Share secure code: it's a limited cheaper version. This options will let you create an extension of any report to share with another user. Both users must have pro to check it or stored in Premium with Free. This option enforce a Azure AD login. It's almost the same thing as getting inside Power Bi Service.
- Power Bi Embed API: this is much more flexible but you have to pay for capacity. Once you pay for Power Bi Embed capacity in azure, you can get this option. This solution let you handle almost everything in the front end. You can get report, dashboard, tile, visuals. You can set filters before loading the embed. You can add a lot of options like exporting or printing. There two ways to develop this. One is letting your App security to Microsoft Azure AD (meaning you need a company email to get in, I think you don't need PBI license). Two is embeding without asking the users the microsoft login. That last option is the strongest one. You can build your own login and share big time with external users removing the idea of license by user (you are already paying capacity).
I hope that make sense.
