4.2 — Configure Apps and Choose a Distribution Method
PL-300 Domain 4 · Skill 4.2
What You Need to Know
Workspace apps
An app packages selected content from one workspace for a broad audience of readers. Each workspace can publish one app.
Creating or updating it (Create app / Update app in the workspace, Admin or Member role, or Contributor if the workspace allows it):
| Tab | Settings |
|---|---|
| Setup | Name, description, logo, theme color, contact information, support site |
| Content | Which reports, dashboards and other items to include, in what order, with sections and links |
| Audience | One or more audiences, each seeing a different subset of the content. Grant access to people, groups or the whole organization. Optionally let users build content with the underlying semantic models, share the app or the models, and install the app automatically |
- Changes in the workspace are not visible to app users until you choose Update app. This lets you work on content safely and release it on purpose.
- App users can't edit the original content. They can personalize visuals and create personal bookmarks.
- RLS applies to app users.
Choosing a distribution method
| Method | Best for | Watch out |
|---|---|---|
| Workspace roles | Collaborators who build and manage content (lesson 4.5) | Not for large reader audiences |
| App | Many readers, curated and versioned content, different audiences | One app per workspace |
| Sharing a report or dashboard | Quick, ad hoc access for a few people | Hard to manage at scale; recipients need a Pro license unless the content is on capacity |
| Links (People in your organization / People with existing access / Specific people) | Sending a link | Organization-wide links can be disabled by admins |
| Embed in Microsoft Teams, SharePoint Online or a portal (secure embed) | Reports where people already work | Permissions still apply |
| Analyze in Excel, Excel connected tables | Excel users who need pivot tables over the model | Needs Build permission |
| Subscriptions | Scheduled email snapshots (lesson 4.3) | |
| Publish to web | Public, anonymous websites (open data) | No security: anyone with the link can see all the data. Never for internal or sensitive data. Admins can disable it |
| Power BI Embedded | Showing reports in your own customer-facing application | Developer work and capacity needed |
Licensing reminder: viewing content shared by any method needs a Pro or PPU license, unless the content is in a workspace on Premium or Fabric F64+ capacity, where free users can view it.
Key Concept: Workspace roles are for people who create content; apps are for people who consume it. Publish to web is public and unsecured, so it's only for data meant for everyone.
Exam Traps
- Adding hundreds of readers as workspace Viewers instead of distributing an app
- Expecting app users to see workspace changes before the app is updated
- Using Publish to web for an internal report that needs a sign-in
- Planning two apps from one workspace (use audiences instead)
- Forgetting that free-license users need content on Premium or F64+ capacity
Check your understanding
Practice Scenario
🔒 This practice scenario is part of Skillmarked Pro
The lessons stay free. Pro unlocks the other 22 PL-300 practice scenarios and the 50-question timed mock exam, plus everything for every other exam.
Launch Deal: first month €9.95, then €19.90/month. Enter code LAUNCH50 at checkout. Ends 1 December.
Cancel anytime. Or €199 a year, which saves 17%.
Not sure yet? Try 10 free mock exam questions.
Already Pro? Log in.
Sources
- Publish an app in Power BI, Microsoft Learn
- Ways to share your work in Power BI, Microsoft Learn
- Publish to web from Power BI, Microsoft Learn
- Share Power BI reports and dashboards, Microsoft Learn