| Scroll ignore | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
This page will walkthrough the setup of PowerBI in K.
...
Set Allow Service Principals to use read-only Power BI admin APIs to Enabled
Select Specific Security Groups
Add an 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 as the previous API Settings option
| Note |
|---|
If you have previously published PowerBI datasets and the Enhance admin APIs response with detailed metadata was not enabled, you will need to republish all PowerBI datasets in workspaces that you want K to profile. The ability to collect detailed lineage information only applies to datasets that are published after this feature is turned on. |
Set Enhance admin APIs responses with DAX and mashup expressions to Enabled
Add the same 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 as the previous 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.
...
| Warning |
|---|
Troubleshooting failed loads
|
...
Troubleshooting missing lineage
...
|
...