Decube
Try for free
  • 🚀Overview
    • Welcome to decube
    • Getting started
      • How to connect data sources
    • Security and Compliance
    • Data Policy
    • Changelog
    • Public Roadmap
  • 🔌Data Warehouses
    • Snowflake
    • Redshift
    • Google Bigquery
    • Databricks
    • Azure Synapse
  • 🔌Relational Databases
    • PostgreSQL
    • MySQL
    • SingleStore
    • Microsoft SQL Server
    • Oracle
  • 🔌Transformation Tools
    • dbt (Cloud Version)
    • dbt Core
    • Fivetran
    • Airflow
    • AWS Glue
    • Azure Data Factory
    • Apache Spark
      • Apache Spark in Azure Synapse
    • OpenLineage (BETA)
    • Additional configurations
  • 🔌Business Intelligence
    • Tableau
    • Looker
    • PowerBI
  • 🔌Data Lake
    • AWS S3
    • Azure Data Lake Storage (ADLS)
      • Azure Function for Metadata
    • Google Cloud Storage (GCS)
  • 🔌Ticketing and Collaboration
    • ServiceNow
    • Jira
  • 🔒Security and Connectivity
    • Enabling VPC Access
    • IP Whitelisting
    • SSH Tunneling
    • AWS Identities
  • ✅Data Quality
    • Incidents Overview
    • Incident model feedback
    • Enable asset monitoring
    • Available Monitor Types
    • Available Monitor Modes
    • Catalog: Add/Modify Monitor
    • Set Up Freshness & Volume Monitors
    • Set Up Field Health Monitors
    • Set Up Custom SQL Monitors
    • Grouped-by Monitors
    • Modify Schema Drift Monitors
    • Modify Job Failure Monitors (Data Job)
    • Custom Scheduling For Monitors
    • Config Settings
  • 📖Catalog
    • Overview of Asset Types
    • Assets Catalog
    • Asset Overview
    • Automated Lineage
      • Lineage Relationship
      • Supported Data Sources and Lineage Types
    • Add lineage relationships manually
    • Add tags and classifications to fields
    • Field Statistcs
    • Preview sample data
  • 📚Glossary
    • Glossary, Category and Terms
    • Adding a new glossary
    • Adding Terms and Linked Assets
  • Moving Terms to Glossary/Category
  • AI Copilot
    • Copilot's Autocomplete
  • 🤝Collaboration
    • Ask Questions
    • Rate an asset
  • 🌐Data Mesh [BETA]
    • Overview on Data Mesh [BETA]
    • Creating and Managing Domains/Sub-domains
    • Adding members to Domain/Sub-domain
    • Linking Entities to Domains/Sub-domains
    • Adding Data Products to Domains/Subdomains
    • Creating a draft Data Asset
    • Adding a Data Contract - Default Settings
    • Adding a Data Contract - Freshness Test
    • Adding a Data Contract - Column Tests
    • Publishing the Data Asset
  • 🏛️Governance
    • Governance module
    • Classification Policies
    • Auto-classify data assets
  • ☑️Approval Workflow
    • What are Change Requests?
    • Initiate a change request
    • What are Access Requests?
    • Initiate an Access Request
  • 📑Data reconciliation
    • Adding a new recon
    • Understand your recon results
    • Supported sources for Recon
  • 📋Reports
    • Overview of Reports
    • Supported sources for Reports
    • Asset Report: Data Quality Scorecard
  • 📊Dashboard
    • Dashboard Overview
    • Incidents
    • Quality
  • ⏰Alert Notifications
    • Get alerts on email
    • Connect your Slack channels
    • Connect to Microsoft Teams
    • Webhooks integration
  • 🏛️Manage Access
    • User Management - Overview
    • Invite users
    • Deactivate or re-activate users
    • Revoke a user invite
  • 🔐Group-based Access Controls
    • Groups Management - Overview
    • Create Groups & Assign Policies
    • Source-based Policies
    • Administrative-based Policies
    • Module-based Policies
    • What is the "Owners" group?
  • 🗄️Org Settings
    • Multi-factor authentication
    • Single Sign-On (SSO) with Microsoft
    • Single Sign-On (SSO) with JumpCloud
  • ❓Support
    • Supported Features by Integration
    • Frequently Asked Questions
    • Supported Browsers and System Requirements
  • Public API (BETA)
    • Overview
      • Data API
        • Glossary
        • Lineage
        • ACL
          • Group
      • Control API
        • Users
    • API Keys
Powered by GitBook
On this page
  • Supported Capabilities
  • Prerequisite
  • Creating Service Principals and Security Group
  • Setting up and providing permissions to Service Principal
  • Additional Configuration for lineage
  1. Business Intelligence

PowerBI

Add a PowerBI connection to your decube so that you can discover the lineage of your assets from source to dashboards.

PreviousLookerNextAWS S3

Last updated 3 months ago

Supported Capabilities

Data Quality
Capability

Freshness

Volume

Schema Drift

Field Health

Custom SQL

Job Failure

Catalog
Capability

Data Profiling

Data Preview

Data Recon
Capability

Add Recon

Connecting to PowerBI requires credentials that can be configured and found through this guide. These credentials include:

  • Tenant ID

  • Client ID

  • Client Secret

  • BigQuery

  • PostgreSQL

  • Microsoft SQL

  • Snowflake

  • Synapse

The connector might be rate-limited when it is scanning more than 1000 workspaces.

Prerequisite

  1. Access to Azure Active Directory for service principals.

  2. A PowerBI Pro or Premium (Premium per-user or Premium capacity ) workspace.

  3. Admin access to PowerBI to change Tenant Settings.

Creating Service Principals and Security Group

  1. Go to Azure Active Directory, under the Manage tab to the left of the screen, look for App Registrations and click it.

  2. Click on New Registrations on the top of the tab and you'll be presented with the screen below.

  1. We recommend entering decube as the Name. Click Register when you are done.

  1. Click Overview on the left tab and take note of the Client ID and Tenant ID we would require when setting up decube.

  2. Click on Certificates and Secrets on the left tab again and click on New Client Secret as below. We recommend the description to be 'decube client secret' and the expiry date to be until the end of your contract with us.

Make sure to copy the Value of the Client Secret and store it somewhere safe like Azure Key Vault. We will need this value for registration.

  1. Go back to the Azure Active Directory main page and on the left tab again click on Groups. Click Create New Group.

  1. Ensure Group Type is Security.

  2. Click on members and search for the previously configured Service Principal. Here it would be decube.

  1. Click on Select to add the service principal into the group.

  2. Click on Create and we are done retrieving the Tenant ID, Client ID and Client Secret for this integration.

Setting up and providing permissions to Service Principal

  1. On the main PowerBI workspace page, on the top right corner, click on the gear icon to Setting and below Governance and Insight you will find Admin Portal.

  2. Here in the Admin Portal, find Tenant Settings and search for Allow service principals to use Power BI APIs under Developer Settings.

  3. Enable it and either Apply to Entire Organisation or Specific Security Group. Here you can search for the one we created earlier. Example of how it should look like below.

  1. Please enable and do this for the following settings as well under Admin API settings.

  • Allow service principals to use read-only admin APIs

  • Enhance admin APIs responses with detailed metadata

  • Enhance admin APIs responses with DAX and mashup expressions

Additional Configuration for lineage

To build out the lineage, we will need to know the data sources that you've referenced within your PowerBI definitions. You can do a one-time mapping for the sources by going to the Data Sources page > Modify Data Source > Additional Config.

To note, for complete Lineage to report sources, with we only support sources from:

🔌
additional configurations
❌
❌
❌
❌
❌
❌
❌
❌
❌
Required credential to connect Decube to PowerBI