MetricSign
EN|NLRequest Access
High severityexecution

Power BI Refresh Error:
FOREIGN_TABLE_NOT_FOUND

What does this error mean?

A query references a table in a Lakehouse Federation foreign catalog that does not exist in the remote database, has been renamed, or is not visible to the configured user.

Common causes

  • 1The table was dropped or renamed in the remote source system after the connection was created
  • 2The federated user lacks SELECT privilege on the specific table
  • 3Schema or database name in the three-part identifier is incorrect (catalog.schema.table)
  • 4The remote source uses case-sensitive identifiers and the query uses incorrect casing

How to fix it

  1. 1Step 1: On the remote system, verify the table exists with the exact name and schema used in the query.
  2. 2Step 2: Grant SELECT on the table to the credentials used by the Databricks connection.
  3. 3Step 3: Check Unity Catalog for cached metadata — run REFRESH FOREIGN TABLE <catalog>.<schema>.<table> if the table was recently added.
  4. 4Step 4: Confirm the three-part path uses the correct foreign catalog, schema, and table name.
  5. 5Step 5: If the remote source is case-sensitive (e.g., PostgreSQL), adjust the query to match the exact casing.

Frequently asked questions

Does Unity Catalog automatically detect remote schema changes?

Not automatically. You need to run REFRESH FOREIGN TABLE or REFRESH FOREIGN SCHEMA to sync metadata from the remote system into Unity Catalog.

Can I browse available foreign tables before querying?

Yes — use SHOW TABLES IN <foreign_catalog>.<schema> from a Databricks notebook or SQL editor to list tables the connection user can access.

Other execution errors