Publish an app in Power BI

In Power BI, you can create official packaged content, then distribute it to a broad audience as an app. You create apps in workspaces, where you can collaborate on Power BI content with your colleagues. Then you can publish the finished app to large groups of people in your organization. The article Install and use apps with dashboards and reports outlines the app user experience.

Screenshot of Power BI apps.

Your business users often need multiple Power BI dashboards and reports to run their business. With Power BI apps, you can create collections of dashboards and reports and publish these collections as apps to your whole organization or to specific people or groups. For you as a report creator or admin, apps make it easier to manage permissions on these collections.

Business users get your apps in a few different ways:

  • They can find and install your app from Microsoft AppSource.
  • You can send them a direct link.
  • You can install it automatically in your coworkers' Power BI accounts if your Power BI administrator gives you permission.
  • Power BI does not send any email to internal users when you distribute or update an app. If you distribute it to external users, those users receive an email with a direct link.

You can create the app with its own built-in navigation, so your users can easily find their way around your content. They can't modify the contents of the app. They can interact with it either in the Power BI service, or one of the mobile apps -– filtering, highlighting, and sorting the data. They get updates automatically and you can control how frequently the data refreshes. You can also give them Build permission to connect to the underlying datasets, and to create copies of the reports in the app. Read more about the Build permission.

Licenses for apps

To create or update an app, you need a Power BI Pro or Premium Per User (PPU) license. For app consumers, there are two options.

  • Option 1 The workspace for this app is not in a Power BI Premium capacity: All business users need Power BI Pro or Premium Per User (PPU) licenses to view your app.
  • Option 2 The workspace for this app is in a Power BI Premium capacity: Business users without Power BI Pro or Premium Per User (PPU) licenses in your organization can view app content. However, they can't copy the reports, or create reports based on the underlying datasets. Read What is Power BI Premium? for details.

Publish your app

When the dashboards and reports in your workspace are ready, you choose which dashboards and reports you want to publish, then publish them as an app.

  1. In the workspace list view, decide which dashboards and reports you want to Include in app.

    Screenshot of Select the dashboard to publish.

    If you choose not to include a report that has a related dashboard, you see a warning next to the report. You can still publish the app, but the related dashboard won't have the tiles from that report.

  2. Select the Create app button in the upper right to start the process of creating and publishing an app from the workspace.

    Screenshot of the Create app button.

  3. On Setup, fill in the name and description to help people find the app. You can also set a theme color, add a link to a support site, and specify contact information.

    Screenshot of Setup for your app.

  4. On Navigation, you select the content to be visible in the app. Then you add app navigation, to organize the content in sections. See Design the navigation experience for your app in this article for details. Under Advanced, you can set the default width of the left navigation pane.

    Screenshot of App navigation.

  5. On Permissions, decide who has access to the app, and what they can do with it.

    • In the new experience workspaces: specific people, Azure AD security groups and distribution lists, and Microsoft 365 Groups. All workspace users are automatically given access to the app for the workspace.
    • In classic workspaces: everyone in your organization, specific people, or Azure Active Directory (Azure AD) security groups.
    • You can allow app users to connect to the app's underlying datasets by giving them Build permission. They'll see these datasets when they're searching for shared datasets. Read more about allowing users to connect to the app's datasets, in this article.
    • Users with Build permission can also have permission to copy reports from this app to another workspace. Read more about allowing users to copy reports in the app, in this article.


    If your app relies on datasets from other workspaces, it is your responsibility to ensure all app users have access to the underlying datasets. If the app or report is in the same workspace as the dataset, make sure you add the report associated with the dataset to the app as well.


    If you are removing permissions from an app that has already been published, see the note in the App permissions section below.

  6. You can install the app automatically for the recipients, if your Power BI admin has enabled this setting for you in the Power BI Admin Portal. Read more about automatically installing an app in this article.

    Screenshot of App permissions.

  7. When you select Publish app, you see a message confirming it's ready to publish. Select Publish.

  8. In the Successfully published dialog box, you can copy the URL that's a direct link to this app.

    Screenshot of App finish.

You can send that direct link to the people you've shared it with, or they can find your app on the Apps tab by going to Download and explore more apps from AppSource. Read more about the app experience for business users.

Change your published app

After you publish your app, you may want to change or update it. It's easy to update it if you're an admin or member in the new workspace.

  1. Open the workspace that corresponds to the app. If you're a workspace Admin or Member, you can open the workspace right from the app, by selecting the Edit app pencil.

    Screenshot of Open the workspace from the associated app.

  2. Make any changes you want to the dashboards or reports.

    The workspace is your staging area, so your changes aren't live in the app until you publish again. This lets you make changes without affecting the published apps.


    If you remove a report and update the app, even if you add the report back to the app, your app consumers lose all customizations such as bookmarks, comments, etc.

  3. Go back to the workspace list of contents and select Update app in the upper-right corner.

    Screenshot of select Update app.

  4. Update Setup, Navigation, and Permissions, if you need to, then select Update app.

    The people you've published the app to automatically see the updated version of the app.


    If you removed app permissions as part of the update, new app installers won't get those permissions. However, the update won't remove the permissions from users who already have them. To remove such existing access, go to the Direct access tab on the datasets manage permissions page and remove the permissions manually. See Manage direct access for detail.

Design the navigation experience

The New navigation builder option allows you to build a custom navigation for your app. The custom navigation makes it easier for your users to find and use content in the app. Existing apps have this option turned off and new apps default to the option being on.

When the option is off, you can select the App landing page to be either Specific content, for example a dashboard or report, or select None to show a basic list of content to the user.

When you turn on New navigation builder, you can design a custom navigation. By default all the reports, dashboards, and Excel workbooks you included in your app are listed as a flat list.

Screenshot of App navigation.

You can further customize the app navigation by:

  • Reordering the items using the up / down arrows.
  • Renaming items in the Report details, Dashboard details, and Workbook details.
  • Hiding certain items from the navigation.
  • Using the New option to add sections to group related content.
  • Using the New option to add a link to an external resource to the nav pane.

When you add a link, in Link details you can choose where the link opens. By default links open in the Current tab, but you can select New tab, or Content area.

Considerations for using the new navigation builder option

Here are general things to keep in mind when using the new navigation builder:

  • Report pages are shown in the app navigation area as an expandable section. When a report has one visible page, only the report name is shown. Clicking the report name in the navigation opens the first page of the report.


    Your report might have only one visible page because you've set up navigation to the rest of the pages with buttons or drill-through actions.

  • If you turn off the new navigation builder and then publish or update your app, you lose the customizations you've made. For example, sections, ordering, links, and custom names for navigation items are all lost.

  • The option to not use the app builder is available.

When adding links to your app navigation and selecting the Content area option:

  • Ensure the link can be embedded. Some services block the embedding of their content in third-party sites like Power BI.
  • Embedding Power BI service content like reports or dashboards in other workspaces isn't supported.
  • Embed Power BI Report Server content through its native embed URL content from an on premises deployment. Use the steps in creating the Power BI Report Server URL to get the URL. Be aware that regular authentication rules apply, so viewing the content requires a VPN connection to the on-premises server.
  • A security warning is shown at the top of the embedded content to indicate the content isn't in Power BI.

App permissions

This section describes the kinds of permissions you can grant to the specified users (Step 5 in Publish your app, above).

  • Allow all users to connect to the app's underlying datasets using the Build permission

    This option grants build permission on the app's underlying datasets.

  • Allow users to make a copy of the reports in this app

    This option grants the ability to create copies of the reports in the app. It can only be selected if the first option granting build permission is selected.

  • Allow users to share the app and the app's underlying datasets using the share permission

    This option grants users reshare permission on the app's underlying datasets.


Removing app permissions via the app's Permissions tab prevents new app installers from getting the permissions. However, users who already have these permissions on the underlying datasets will retain their permissions. To remove this existing access, go to the Direct access tab on the datasets manage permissions page and remove the permissions manually. See Manage direct access for detail.

Automatically install apps for end users

If an admin gives you permissions, you can install apps automatically, pushing them to end users. This push functionality makes it easier to distribute the right apps to the right people or groups. Your app appears automatically in your end users' Apps content list. They don't have to find it from Microsoft AppSource or follow an installation link. See how admins enable pushing apps to end users in the Power BI admin portal article.

How to push an app automatically to end users

Once the admin has assigned you permissions, you have a new option to install the app automatically. When you check the box and select Publish app (or Update app), the app is pushed to all users or groups defined in the Permissions section of the app on the Access tab.

Screenshot shows Power B I Publish app option with Install app automatically selected.

How users get the apps that you push to them

After you push an app, it shows up in their Apps list automatically. In this way, you can curate the apps that specific users or job roles in your organization need to have at their fingertips.

Screenshot shows Power B I Apps with your published app included.

Considerations for automatically installing apps

Here are things to keep in mind when pushing apps to end users:

  • It isn't possible to automatically install an app for an entire organization. You notice that when you select the checkbox for install app automatically, the option for entire organization becomes inactive.

  • Installing an app automatically to users can take time. Most apps install immediately for users, but pushing apps can take time. It depends on the number of items in the app and the number of people given access. We recommend pushing apps during off hours with plenty of time before users need them. Verify with several users before sending broad communication about the apps' availability.

  • Refresh the browser. Before seeing the pushed app in the Apps list, the user may need to refresh, or close and reopen their browser.

  • If users don't immediately see the app in the Apps list, they should refresh or close and reopen their browser.

  • Try not to overwhelm users. Be careful not to push too many apps so your users perceive the pre-installed apps are useful to them. It's best to control who can push apps to end users to coordinate timing. Establish a point of contact for getting apps in your organization pushed to end users.

  • Guest users who haven't accepted an invite don't get apps automatically installed for them.

Allow users to connect to datasets

When you check the option to Allow users to connect to the app's underlying datasets, you're giving app users Build permission on those datasets. With this permission, they can do several key actions:

  • Use the app datasets as the basis for their reports.
  • Search for these datasets in Power BI Desktop and in the get-data experience in the Power BI service.
  • Create reports and dashboards based on these datasets.

When you clear this option, new users you add to the app don't get Build permission. However, for existing app users, permissions on the underlying datasets don't change. You can remove Build permission manually from app users who should no longer have it. Read more about the Build permission.

Allow users to copy reports

When you check the option to Allow users to make a copy of the reports in this app, your users can save any of the reports in the app to their My Workspace or another workspace. To make a copy, users need a Pro or Premium Per User (PPU) license, even if the original report is in a workspace in a Premium capacity. They can then customize the reports to their unique needs. You have to select the Allow all users to connect to the app's underlying datasets using Build permission option first. By selecting these options, you're enabling the new copy reports from other workspaces capability.

Unpublish an app

Any member of a workspace can unpublish the app.


When you unpublish an app, app users lose their customizations. They lose any personal bookmarks, comments, or subscriptions associated with content in the app. Only unpublish an app if you need to remove it.

  • In a workspace, select More options (...) > Unpublish app.

    Screenshot of Select the Unpublish app button.

This action uninstalls the app for everyone you've published it to, and they no longer have access to it. It doesn't delete the workspace or its contents.

View your published app

When your app consumers open your app, they see the navigation you created, instead of the standard Power BI nav pane. The app navigation lists the reports and dashboards in the sections you've defined. It also lists the individual pages in each report, rather that just the report name. You can expand and collapse the left navigation by using the arrows in the menu bar.

Screenshot of App with navigation.

In full-screen mode, you can show or hide the navigation by selecting the option in the corner.

Screenshot of Full-screen navigation.

Considerations and Limitations

Things to keep in mind about publishing apps:

  • The permissions page doesn't change permission on datasets in other workspaces. You do see a warning reminding you to grant access to those datasets independently. A best practice is to contact the dataset owner before starting to build your app to ensure it is OK to give all your app users access those datasets.
  • You can have at most 100 users or groups in the access list for the app. However, you can give more than 100 users access to the app. To do so, use one or more user groups that contain all the desired users.
  • For the new workspace experience, if the user added to the app access list already has access to the app through the workspace, they will not be shown in the access list for the app.
  • The support site URL is shown in the item information card.
  • Apps can have a maximum of 200 dashboards.

Next steps