Scroll ignore | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
This page will walkthrough the setup of PowerBI in K using the direct connect method.
...
Integration details
Scope | Included | Comments | ||||||
---|---|---|---|---|---|---|---|---|
Metadata |
| See limitations below | ||||||
Lineage |
|
| ||||||
Usage |
| |||||||
Sensitive Data Scanner |
|
|
Note |
---|
Known Power BI limitations (limited by Microsoft)
Known KADA Power BI integration limitations (to be resolved in upcoming releases)
|
...
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:
|
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
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
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 (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
Info |
---|
Make sure you send the AD Group name used to the Azure AD Admin so that they can complete the next step |
...
Log in to your company’s Azure Portal and open the Azure Active Directory page
Select App Registration in the side panel and click New registration
Complete the registration form
Name: Enter a name for the integration e.g. KADA Power BI API Integration
Supported account types: Select Accounts in this organisation directory only
Redirect URL: Add Web / https://www.kada.ai
Click Register to complete the registration
Click on the newly created KADA Power BI API Integration App
Save the Application (client) ID and Directory (tenant) ID for use in a later step
Click on Endpoints and save the URL for OpenID Connect metadata document for use in a later step
Select Certificates & secrets in the side panel and click New client secret
Complete the new secret form and save the Secret IDValue for use in a later stope
Select API permissions in the side panel and check that that Microsoft.Graph - User.Read permission has been added
...
step
Return to the Azure Portal and select Group
Find the AD Group that was created in step 1 and click Members
Select Add Members and add KADA Power BI API Integration to the group as a Service Principal
Info |
---|
Make sure you send the following information to the K Admin so that they can complete the next process.
|
...
Step 3) Add Service Principal to PowerBI Workspace(s)
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.
...
Step 4) Add PowerBI as a New Source
Info |
---|
This step is performed by the K Admin |
...
Select Direct Connect and add your Power BI details and click Next
Fill in the Source Settings and click Save & Next
Name: Give the Power BI source a name in K
Host: Must be unique. You can use http://app.powerbi.com if you only have 1 instance of Power BI.
Timeout: Default is 10, sometimes it may take longer for the API to respond, so we recommend increasing it to 20
Add Update the Host / Mapping details. See Database mapping - see Host / Database Mapping for more details. This step can be completed after the initial load via the guided workflow.
Select Enable Workspace Filtering if you wish to load only select Workspaces
Add Connection Details and click Save & Next
Tenant ID: Add the Directory (tenant) ID copied from step 2
Client ID : Add the Application (client) ID copied from Step 2
Client Secret: Add the Secret ID copied from Step 2
Test your connection and click Next
If you selected Enabled Workspace Filtering select the Workspaces you want to load. If you have a lot of workspaces this may take a bit of time to load.
Click Finish Setup
...
Step 4) Schedule PowerBI source load
...
Step 5) Manually run an ad hoc load to test Power BI
Select Platform Settings in the side bar
In the pop-out side panel, under Platform Settings click on Batch Manager
In Source Load click Run
...
Select the name of the Source you created in Step 2 and click RunNext to your new Source, click on the Run manual load icon
Confirm how your want the source to be loaded
After the source load is triggered, the screen will change a pop up bar will appear taking you to the Monitor tab where you can see in the Batch Manager page. This is the usual page you visit to view the progress of the job.
...
source loads
Info |
---|
A manual source load will also require a manual run of
To load all metrics and indexes with the manually loaded metadata. These can be found in the Batch Manager page |
...
Warning |
---|
Troubleshooting failed loads
|