Versions Compared

Old Version 25

changes.mady.by.user Dean Nguyen

Saved on

compared with

New Version Current

changes.mady.by.user Chichi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Scroll ignore
scroll-viewporttrue
scroll-pdftrue
scroll-officetrue
scroll-chmtrue
scroll-docbooktrue
scroll-eclipsehelptrue
scroll-htmltrue
scroll-epubtrue

Open in new tab

This page will walkthrough the setup of PowerBI in K using the direct connect method.

Integration details

Scope

Included

Comments

Metadata

Status
colourGreen
titleYES

 See limitations below

Lineage

Status
colourGreen
titleYES

 

Usage

Status
colourGreen
titleYES

Sensitive Data Scanner

Status
titleN/A

 

Note

Known Power BI limitations (limited by Microsoft)

  • Power BI API is currently rate limited. This may impact extracts where you have 200+ workspaces or groups. Some Power BI reports may fail to extract correctly and may their details may not be profiled.

  • Power BI datasets using large dataset storage format cannot be profiled.

  • Power BI reports created in web browser (not uploaded from desktop) cannot be profiled for detailed lineage. Dataset lineage will be available.

  • Power BI dashboards in Apps are not able to be linked to their Power BI dashboard.

Known KADA Power BI integration limitations (to be resolved in upcoming releases)

  • Power BI currently only supports lineage to Snowflake, SQL Server and Oracle.Power BI reports that use inbuilt fields report measures cannot be profiled for detailed lineage.Power BI reports created in web browser missing dataset lineage.

  • Power BI access does not consider direct grants to users. Access is only detected for users via AD groups. Power BI data flows are not currently included in the metadata extracted.

...

Step 1) Enabling PowerBI Admin APIs to be accessible to an AD Group

Info

This step is performed by the Power BI Admin

At the end of this step, the AD Group will need to be provided with access to the following Admin API Settings:

  • Read-only Power BI admin APIs - Enabled

  • Detailed metadata - Enabled

  • DAX and mashup expressions - Enabled

  • Open Power BI portal and navigate to Admin Portal in the top right hand navigation

...

  • Set Allow Service Principals to use read-only Power BI admin APIs to Enabled

    • Select Specific Security Groups

      • Add an the AD group (K PowerBI AD Group) that is appropriate for managing this access. This is typically the Admin group for Power BI. If no appropriate group exists, contact your Azure AD admin to create a new security group.

      • Record this AD group for Step 2

  • [Required for Power BI detailed lineage] Set Enhance admin API responses with detailed metadata to Enabled

    • Add the same AD group (e.g. K PowerBI AD Group) as the previous API Settings option

...

  • Set Enhance admin APIs responses with DAX and mashup expressions to Enabled

    • Add the same AD group (e.g. K PowerBI AD Group)as the previous API Settings option

  • [Required for Power BI detailed lineage] Set Allow Service Principals to use Power BI APIs to Enabled

    • Select Specific Security Groups

      • Add the same AD group (e.g. K PowerBI AD Group) as the previous step

  • Set Download Reports to Enabled and apply to The entire organisation

    image-20240617-023914.pngImage Added
Info

Make sure you send the AD Group name used to the Azure AD Admin so that they can complete the next step

...

Info

This step is performed by the Power BI Admin

[Required for Detailed Lineage] Your K instance will now have access to the majority of your Power BI assets. To profile and catalog items such as Pages within a Report, or if your datasource connections use parameters, please add the KADA Power BI API Integration (created in Step 2) as a Member to each Power BI workspace you want it to profile.

...