Org vs. Workspace Apps - permissions & embedding

Hi. I don't think embedding apps is a feature available for any of those. I mean, there no feature to do it with neither of them. If you copy a link of a power bi app and iframe it on sharepoint site, it's manual tweak and not real supported feature like embedding a report inside sharepoint that will generate specifically a link for that.

About sharing with entire organization, you can handle that creating a security group at Entra ID with all the users. Then share the org app with that group.

Consider OrgApps are the future. They can handle CICD and probably new features in time.

I hope that helps,

Hi pghMR​,

Both of those look like current limitations of org apps rather than a setting you are missing (they are still evolving, so worth re-checking the docs' limitations list before rollout). Two practical workarounds so you can still pick org apps:

1. "Entire organization" -> an all-employees group. Create a dynamic Entra ID group that always contains every active employee, and use it as the audience. Membership updates automatically for joiners and leavers:

Entra ID > Groups > New group
  Group type: Security
  Membership type: Dynamic User
  Rule:
    (user.accountEnabled -eq true) -and (user.userType -eq "Member")

(Dynamic groups need Entra ID P1. If you don't have it, many orgs already have an "All staff" group maintained by HR/IT that you can reuse.)

2. SharePoint -> embed the reports, link to the app. Rather than embedding the app, embed the key report pages with the Power BI web part (or "Embed report > SharePoint Online" link) and add a "Open full app" button that links to the org app. Permissions still flow from the app audience / workspace access, so users only see what they are allowed to.

SharePoint page
  -> Power BI web part: Report A (page "Overview")
  -> Power BI web part: Report B (page "Summary")
  -> Button: "Open the full Sales app" -> org app link

So my overall approach would be:

Org app as the main distribution channel
-> Audience = dynamic "all employees" group
-> SharePoint = embedded report pages + link to the app
-> Re-check org app limitations as they reach GA

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.

Hi pghMR​ 

From my perspective, using the new Org Apps is the way to go because more features are being put into this as well as it is shown with the CICD, which means that they're investing in this capability. And as others have mentioned, you should just be able to embed the URL into Sharepoint.

Hi pghMR​,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. 

Thank you.

Hi pghMR​,

May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.

Thank you

For an organization-wide Power BI rollout, Organizational apps and Workspace apps have different sharing and embedding capabilities, so the best choice depends on how users access reports.

1. “Share with the entire organization” — this option may not be available in Organizational apps in the same way it is for Workspace apps. Check whether the app's audience and underlying report permissions support your intended access model.

2. SharePoint embedding — if Organizational apps do not support your required embedding scenario, use a supported report URL or embed option from the workspace, with appropriate Power BI permissions and licensing.

Solution

• For organization-wide distribution: Org apps support sharing with users and groups; however, the exact “Entire organization” option may differ from workspace apps. See Microsoft's Org Apps documentation.
•  For SharePoint: Use the Power BI web part with the individual report URL, rather than trying to embed the entire app. Users still need permission to view the report.

Recommendation: Use Org apps for centralized content distribution, but embed individual reports in SharePoint pages where needed. If embedding the complete app experience is essential, retain Workspace apps for that scenario