Hi
As my understand, you are mentioning about PBI Embeded (using js/c#) and IFRAME of Public to web feature? Basically, they are same uses that returns iframe to embed. But
Iframe from Public to web
- Public to web: manually
- Token expiration to view: none (just remove embed from Manage Embed code panel)
- None security - everyone has same permission with data
- Managed in PBI service
- Support both of DQ & Import mode of reports
- Free - No cost
Iframe from api of PBI embeded
- Using code to embed (automatically)
- Support direct query mode so far
- Has expiration (default 15-20') and could be extended by c#
- Permission by RLS (if available) (DAX handling in report layer for database source or user roles in SSAS source) or user group of tenants
- Could embed tiles separately report
- Managed in Azure PBI workspace collection by using azure portal, cli command, js and C# code
- Charge embeded fee by "session"
if amount of roles is not large (e.g 10 roles of 1000 users), you could do workaround solution with "Public to web" by clone pbix file to 10 files and set the filter for data in Query Editor, so you have 10 different iframes and using if/else in your app to show them by role of users.
On the other hand, you could implement RLS in PBI Embeded as mentioned above