Skip to main content

Power BI OLS dataset enrichment

TL;DR

Complete configuration reference for Power BI OLS dataset enrichment in the Microsoft Power BI crawler, including the BIM file fields, S3 authentication, and how it restores Power BI lineage broken by OLS.

Connect

Power BI OLS dataset enrichment repairs the lineage gap caused by Power BI's Object Level Security (OLS), which prevents Atlan's crawler from retrieving PBI table metadata. It reads a BIM file exported from the Power BI Semantic Model and creates the missing Power BI tables, columns, column data types, and lineage processes, both upstream to the Data Warehouse and downstream to the PBI Dataset. This reference provides complete configuration details for each field.

Part of the Power BI crawler

Enrichment runs as part of the Microsoft Power BI crawl, under Advanced Configuration. It was previously delivered as a separate PBI OLS Dataset Enricher app. For the end-to-end procedure, see Enrich Power BI OLS datasets.

Prerequisites​

Before you begin, make sure you have:

  • Tabular Editor installed and available to run a script that extracts the BIM file from the Power BI Semantic Model.
  • A Service Principal to authenticate Tabular Editor with the PBI workspace and Semantic Model.
  • A Premium Capacity or Fabric workspace so Tabular Editor can connect to the Semantic Model.
  • An AWS S3 bucket where the extracted BIM file is uploaded and from which the crawler reads it.

Configuration​

The following fields appear under Advanced Configuration on the Microsoft Power BI workflow. They control where the crawler reads the BIM file from and which connections it builds lineage against.

Enable Power BI OLS dataset enrichment​

Turns enrichment on for this crawl. When set to False, the remaining BIM fields are ignored and OLS-protected tables stay missing in Atlan.

Source connections​

Select the data warehouse connections in Atlan to build upstream lineage against. When a source system has several connections holding similar metadata (for example, Prod, Staging, and Dev), selecting the right ones prevents duplicate lineage.

BIM file bucket​

Name of the AWS S3 bucket holding the extracted BIM files.

Example:

atlan-powerbi-bim-exports

BIM file bucket region​

AWS region of that bucket.

Example:

eu-west-2

BIM file prefix​

The directory path within the S3 bucket where the BIM file is located. Use forward slashes (/) as path separators. If left blank, the crawler searches from the root of the bucket.

Example:

POWERBI/

BIM bucket role ARN​

ARN of the IAM role Atlan assumes to read the bucket. Access to S3 is role-based only. The crawler takes no access key or secret.

Leave it blank when the bucket is readable by the EC2 role Atlan uses in its EKS cluster. Raise a support ticket to have Atlan attach your IAM policy to that instance role.

Enter a role ARN when the bucket is in a different AWS account from Atlan, and Atlan's node instance role needs to assume a role in yours:

  1. Raise a support ticket to get the ARN of the Node Instance Role for your Atlan EKS cluster.
  2. Create a new IAM role in your AWS account following the AWS IAM User Guide.
  3. Attach your IAM policy to this role.
  4. Create a trust relationship using the policy below, replacing <atlan_nodeinstance_role_arn> with the ARN provided by Atlan support:
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "AWS": "<atlan_nodeinstance_role_arn>"
      },
      "Action": "sts:AssumeRole",
      "Condition": {}
    }
  ]
}
  1. Share with Atlan support:
    • The name of the role you created.
    • The ID of the AWS account where the role was created.

For storage credentials, access methods, and required fields across providers, see Object storage configuration for apps, which applies to S3, GCS, and ADLS-based imports.

See also​