Create Power BI report and dataset components (preview)

[This topic is pre-release documentation and is subject to change.]

As data culture spreads across more and more organizations, and analytics becomes a vital part of decision making and the daily actions taken by employees, it has become critical to have reliable, up-to-date analytics readily available in your Power Apps.

As a step towards achieving this goal, it possible to add Power BI reports and datasets as components in Power Apps solutions. Once you've added a Power BI report to a solution, it can be seamlessly managed as part of your ALM process across environments and tenants.


  • This is a preview feature.
  • Preview features aren’t meant for production use and may have restricted functionality. These features are available before an official release so that customers can get early access and provide feedback.

In this article, you'll learn how to do the following tasks:

  • Add Power BI reports and dataset components to a solution.
  • Configure the behavior of Power BI mashup parameters upon import and export as part of the Power Apps solution.
  • Configure the dataset component so that the dataset automatically connects to a Microsoft Dataverse data source when the solution is deployed to a new environment.


  • A Power BI Pro license.
  • A Power BI report and/or dataset that you want to create Power Apps solution components for.

General limitations and restrictions

  • The Power BI Extensions (Preview) system solution must be installed. In new environments it's installed by default. Existing environments must install it manually from PPAC before importing solutions and creating Power BI components. To install the extension, go to the Power Platform admin center.
  • Only Power BI reports and datasets can be added to a solution. Only datasets created with the enhanced dataset model are supported. Any other artifact type is not supported (such as dashboard, dataflow, and paginated report).
  • Connection references to Power BI data sources aren't supported (for example, in composite models).
  • The Power BI dataset parameter types "Any" and "Binary" aren't supported in the Power BI integration with Power Apps solutions.
  • Sharing Power BI reports and datasets can only be done from Power BI (sharing the model driven app doesn't share the embedded report).
  • Recovery from workspace deletion isn't supported. Once the dedicated environment workspace has been deleted, you won't be able to add/import any Power BI component to the Power Apps environment.
  • Power Apps Application IDs aren't supported during public preview.
  • Information sharing between Power Platform environments and Power BI workspaces located in different geographies is supported if the relevant settings are ON. More information: Cross-geo operations.
  • Environment life cycle operations aren't supported during preview. More information: Considerations working with the Power Apps/Power BI integration.
  • Dataverse for Teams environments are not supported.
  • National clouds are not currently supported.

Create Power BI report and dataset components

  1. Open your Power Apps solution development environment.

  2. Create a new solution.

  3. In the new solution, choose Add existing > Analytics > Power BI Report.

    Screenshot of add Analytics menu showing Power B I component dataset and report options.

  4. Select Outside Dataverse, find and select the Power BI report you want to add to the solution, and then choose Add.

    Screenshot showing Outside Dataverse tab for selecting a Power B I item that is outside Dataverse.

    When you add a Power BI report component to a solution, a component for the report's dataset is added to the solution as well.

    In addition, when you add a report from outside of Dataverse, copies of the report and its dataset are created in the workspace that is dedicated to the environment. Afterwards, all updates should start from this dedicated environment workspace.

    Screenshot showing Power B I components successfully added to solution.


    The Add operation can last a few minutes while the actual reports and datasets are being exported to Dataverse.

  5. If your dataset connects to a Dataverse data source, you can configure it to automatically connect to the Dataverse data source in deployment environments.

    Select the dataset and choose Edit.

    Screenshot showing the edit buttons for a Power BI component.

  6. In the edit pane that appears, select Yes to configure the dataset so that it automatically connects to an existing connection when the solution is imported into another environment.

    Screenshot showing how to automatically connect a Power B I component to an existing connection in deployment environments.


    Steps 5 and 6 are only relevant for Dataverse data sources.

  7. Now, you can create a Power BI embedded system dashboard based on the report component or embed it (the report component) in a form using the form designer.

  8. When done, export the solution. You can export the solution as either a managed or unmanaged solution.

Configure Power BI parameters

Power BI components allow you to configure Power BI mashup parameters. However, you can't create Power BI mashup parameters in the solution environment – they must already be present in the Power BI dataset you add to the solution.


The Power BI dataset parameter types Any and Binary are not supported in the Power BI integration with Power Apps solutions.

In this section the options you have for configuring how a Power BI dataset parameter is going to get its value when the solution is deployed in a different environment are displayed.

  1. Go to your Power Apps environment > Solutions.

  2. Create a solution.

  3. Select the dataset that has the parameters you want to configure, and then choose Edit parameters:

    Screenshot of how to open the edit parameter page.

  4. Choose Add a parameter. You can only add parameters that are already part of the Power BI dataset:

    Screenshot of how to add a new Power B I parameter.

  5. Select a Power BI mashup parameter and choose Edit to open the parameters edit pane. Select the Replace current value with * drop-down to view the parameter configuration options.

    Screenshot of how to replace the current parameter value.

    You have three options for determining how the parameter is going to get its value when the solution is installed in a different environment:

    • Custom text: This is the most straightforward way to set a value. When you select the custom text option, you specify a text string, and then, when the solution is deployed in another environment, that text string will be the value of the parameter.

    • Current environment domain: When you choose current environment domain, the value of the parameter will be domain of the current environment. This means that wherever the solution is deployed, the value of the parameter will be the domain of the deployment environment.

    • Environment variable: With this option you associate the parameter value with an environment variable. When you select this option, you'll notice all the environment variables in the current environment, and you can select one. If the environment variable you need doesn't exist, you can create one in the solution.

      The environment variable option is significant because it makes it possible to require the installer to provide a value for a parameter during deployment. This is done by associating the parameter with an environment variable that has a blank value.

      When you configure a parameter with an environment variable in order to require the installer to provide a value upon deployment, make sure that the default value is blank. If there is a current value, remove it by right-clicking and choosing Remove from solution.

      For more information about environment variables, go to Environment variables overview.

  6. Once you're done configuring the parameters, select Apply all to apply all parameter values.

    Screenshot of how to apply all parameter values.

  7. Once you’re applied the parameters, you can export the solution and deploy it in your deployment environments.

Updating a solution that includes Power BI components

Updates to Power BI components must be made in Power BI on the artifacts in the dedicated Power BI environment workspace that are connected to the components. You can access these artifacts either by opening the workspace directly in the Power BI service, or by using the Open in Power BI option in the Power Apps environment.

Screenshot showing the Open Power BI option in Power Apps.


Updating a solution with Power BI components automatically updates the relevant artifacts of the dedicated environment workspace in Power BI for both managed and unmanaged solutions.

After you update the component, you can export the solution as a managed or unmanaged solution, and then import it into a different environment (for unmanaged solutions you can also import into the same environment).

See also