Muokkaa

Jaa


Publish a Power BI Desktop file to Power BI

Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019

Once you've created a Power BI Desktop file and the associated datasets, measures, and charts, you can share them with others by creating a dashboard on Power BI. This article shows you how.

Publish to Power BI

  1. If using an Analytics view, verify that the view is Shared and not Private.

  2. Open the Power BI Desktop file with your data.

  3. Select Publish on the Home tab.

    Publish Power BI Desktop file

  4. Respond to the prompts to sign in. If you don't already have a Power BI account, you'll need to create one. Select Sign in.

    Publishing successful

  5. Select the Open <file name> in Power BI link.

Configure refresh schedule

  1. Expand the navigation pane in Power BI and select the work space that you selected when you published the report.

  2. Select Datasets in the upper right corner.

  3. Select the ellipsis next to the dataset that represents the report you just loaded. It's typically the file name.

    Select the dataset

  4. Select Schedule Refresh.

  5. Select the Edit credentials link next to ODATA under Data source credentials as shown here:

    Update odata credentials

  6. Select the appropriate authentication option.

    • Use oAuth2 for Microsoft Entra ID or Windows credentials. This is the recommended approach.

      Configure Areas dialog

    • Use Basic for PAT credentials.

      Configure Fabrikam Data dialog, Enter credentials

      Important

      If you are using a Personal Access Token, remember that the token expires on a set interval. When it expires you'll need to update the credentials. Otherwise the report, while still displaying data, won't update with the latest data.

  7. Select Sign in.

At this point, the data will update on your scheduled basis using the credentials entered.

Important

Any data included in the Analytics view and published Power BI will be accessible to all users with access to the report, regardless of the project permissions configured in Azure DevOps.