Skip to main content
Community Hub
TL;DR

Configuration reference for Power BI OLS dataset enrichment, including BIM file source fields for Atlan Object Storage, Amazon S3, and Azure Blob Storage.

Your AI can read this via Docs MCPcurl -fsSL "https://docs.atlan.com/install-docs-mcp" | bashConnect

Power BI OLS dataset enrichment

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.
  • Storage for the extracted BIM files: Atlan Object Storage, an Amazon S3 bucket, or an Azure Blob Storage container. Google Cloud Storage isn't supported.

Configuration​

The following fields appear under Advanced Configuration on the Microsoft Power BI workflow. They control where the crawler reads the BIM files from and which connections it builds lineage against. No storage field takes a secret. Atlan reads storage with its own platform access, its own AWS identity, or a role it assumes, and reads Azure Blob Storage with the Power BI credential.

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. If you turn it off after a successful run, the crawler deletes the tables that enrichment created.

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 source​

Where the crawler reads the BIM files from.

  • Atlan Object Storage (default): your tenant's own Atlan storage (Azure Blob on Azure-hosted tenants). Atlan reads it with its own platform access. Contact Atlan support to get a prefix and upload access.
  • External Object Storage: any Amazon S3 bucket or Azure Blob container, including an S3 bucket Atlan set up for you. Select the provider in Storage provider.

Crawlers configured with a bucket and region before this field existed read as External Object Storage with AWS S3. When you edit one, select External Object Storage and AWS S3 if the form shows Atlan Object Storage. The saved bucket, region, prefix, and role values are kept.

BIM file prefix​

The path that holds the BIM files. Use forward slashes (/) as path separators. The crawler also reads .bim files in subfolders of the prefix, up to 500 files in total.

  • With Atlan Object Storage, the prefix is required, because the root of your tenant's storage holds Atlan's own files.
  • With External Object Storage, the prefix is optional. If left blank, the crawler scans the whole bucket or container.

Example:

powerbi/ols/bim

Storage provider​

Appears when BIM file source is External Object Storage. Select AWS S3 (default) or Azure Blob Storage.

AWS role ARN​

Appears for AWS S3. ARN of an IAM role in your AWS account that Atlan assumes to read the bucket.

Atlan reads S3 with its own AWS identity: the node instance role on AWS-hosted tenants, or an AWS role Atlan provides on tenants hosted on another cloud. Raise a support ticket to get the ARN of that identity.

Leave it blank when you grant Atlan's identity read access to the bucket directly: s3:ListBucket on the bucket and s3:GetObject on the prefix in the bucket policy. Raise a support ticket so Atlan grants its identity the same actions, because a read across AWS accounts needs both.

Enter a role ARN when you want Atlan to assume a role in your account:

  1. Raise a support ticket to get the ARN of Atlan's AWS identity for your tenant.
  2. Create a new IAM role in your AWS account following the AWS IAM User Guide.
  3. Attach a policy that grants s3:ListBucket on the bucket and s3:GetObject on the prefix.
  4. Create a trust relationship using the policy below, replacing <atlan-aws-identity-arn> with the ARN provided by Atlan support:
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "AWS": "<atlan-aws-identity-arn>"
      },
      "Action": "sts:AssumeRole",
      "Condition": {}
    }
  ]
}
  1. Enter the role's ARN in this field.

If the bucket uses a customer-managed KMS key, also grant the identity that reads the bucket kms:Decrypt on that key.

Example:

arn:aws:iam::123456789012:role/roleName

Bucket name​

Appears for AWS S3. Required. The plain name of the S3 bucket holding the BIM files, without s3://.

Example:

example-bim-exports

Region​

Appears for AWS S3. Required. AWS region of the bucket.

Example:

us-west-2

Storage account name​

Appears for Azure Blob Storage. Required. The Azure storage account that holds the container.

Atlan reads the container with the Power BI app registration on your Power BI credential, so the credential must use service principal authentication. Grant that app registration the Storage Blob Data Reader role on the container or storage account. The storage account must be in the same Microsoft Entra tenant as the app registration, or the app registration must be multi-tenant with a service principal in the storage account's tenant.

Container name​

Appears for Azure Blob Storage. Required. The blob container that holds the BIM files.

See also​