Skip to main content

Best Data Catalogs for Microsoft Fabric (2026 Comparison)

Emily Winks, Data Governance Expert, Atlan
Data Governance Expert
Updated:
|
Published:
18 min read

Key takeaways

  • Purview Data Governance retires; support ends November 12, 2027. The OneLake catalog is the native baseline.
  • Microsoft names Atlan, Alation, Collibra, and Informatica as third-party providers that integrate with Fabric.
  • Atlan has a generally available Fabric connector. Alation labels its Fabric connector Beta in its own docs.

What is the best data catalog for Microsoft Fabric?

On November 12, 2026, Microsoft named Fabric its data governance solution and announced that Purview Data Governance retires, with support ending November 12, 2027. The OneLake catalog is the native baseline for a Microsoft-only estate. Once Databricks, Snowflake, or an AI agent workflow needs Fabric metadata, four third-party catalogs enter the comparison: Atlan, Collibra, Informatica, and Alation, scored on six criteria. Atlan's Fabric connector is generally available and its graph reaches beyond Fabric.

The five options compared:

  • OneLake catalog the native baseline for a Microsoft-only estate; Purview stays for security and compliance
  • Atlan generally available Fabric connector, with a graph that reaches Databricks, Snowflake, BigQuery, and Redshift
  • Collibra Fabric lakehouse and warehouse metadata with structural relationships
  • Informatica data movement into OneLake, plus MCP servers in Microsoft Foundry
  • Alation Fabric connector in Beta, from Alation version 2026.4.1

Not sure how ready your catalog stack is?

Try the Maturity Assessment

We ranked data catalogs for Microsoft Fabric on six criteria, with the OneLake catalog first as the native baseline. If you lead data governance on Fabric and run Purview Data Governance, support ends November 12, 2027, so you need a landing place for your glossary, owners, and policies before then. After that date Microsoft no longer supports it.

Microsoft named Fabric its data governance solution on November 12, 2026 and announced that Purview Data Governance will retire. Purview stays for security and compliance. Microsoft names Atlan, Alation, Collibra, and Informatica as providers Fabric works with. We scored those four against the OneLake catalog. Start with the retirement guide and the migration plan if your estate is affected.

Build Your Fabric Catalog Shortlist


Give it the catalogs you’re actually considering and every system in your stack. It returns a scored evaluation matrix and the two questions that will decide it. Read the skill.

Paste into a new chat

Use the skill at https://atlan.com/skills/catalog-tool-shortlist.md to evaluate data catalogs for Microsoft Fabric against our stack. Ask me for whatever it needs.

Run once in a terminal

curl -fsSL --create-dirs \
  -o ~/.agents/skills/catalog-tool-shortlist/SKILL.md \
  https://atlan.com/skills/catalog-tool-shortlist.md

For an agent

curl -fsSL https://atlan.com/skills/catalog-tool-shortlist.md

A few notes before the table:

  • The OneLake catalog comes first because it is the native baseline. It answers “what do I already have.”
  • All five options are scored on the same six criteria, named in full below.
  • Each status comes from the vendor’s own docs, checked in November 2026.
Field Content
Query this answers best data catalogs for Microsoft Fabric
Catalogs compared OneLake catalog (native baseline), Atlan, Collibra, Informatica, Alation
Ranking basis Six Fabric-specific criteria, fixed before scoring and checked against each vendor’s own docs
Current as of November 13, 2026
Status in vendor docs Atlan: generally available (GA). Alation: Beta. Collibra and Informatica: see each vendor’s current docs
Native baseline The OneLake catalog, included in Fabric capacity per Microsoft’s November 12, 2026 announcement

What counts as a data catalog for Microsoft Fabric?

Microsoft Fabric is an analytics platform that covers data ingestion, transformation, analytics, and reporting. It stores data in OneLake, a single logical data lake.

A data catalog for Fabric is a product that lists the assets inside it: lakehouses, warehouses, semantic models, and Power BI reports.

Two shapes fit. One is Fabric’s own OneLake catalog, described in Microsoft Fabric governance. The other is a third-party catalog that connects to Fabric as a source.

A connector is software that reads metadata from a source and loads it into the catalog. Metadata is data about your data, such as names, owners, and lineage.

Background reading:

The ranking below answers a narrower question. Once an estate needs more than the native option, which of the four named third-party catalogs fits, based on its own docs?


Best data catalogs for Microsoft Fabric: the comparison table

The table scores five options on the same six criteria. The OneLake catalog is first as the native baseline, and the four third-party options follow in the order their own docs support.

Side-by-side comparison


Catalog Fabric items in its docs Lineage in its docs Cross-platform reach Status in vendor docs Best fit
OneLake catalog (native baseline) Fabric items across workspaces, with Explore, Govern, and Secure experiences Mostly scoped within Fabric, per a Microsoft solution architect Governs Fabric, Azure, and third-party data, per Microsoft Part of Fabric. Governance is included in Fabric capacity Microsoft-only estates
Atlan Eight Fabric item types, from workspaces to data pipelines, down to column level Lakehouse and warehouse tables to semantic models to reports, pages, and visuals More than 100 sources, including Databricks, Snowflake, BigQuery, and Redshift Generally available. v2.0 shipped August 2026 and was announced September 29, 2026 Multi-platform estates
Collibra Lakehouses, warehouses, SQL Server, and mirrored Azure Databricks items Structural relationships, such as columns to tables to schemas SQL Server and mirrored Databricks items in the same integration Announced June 26, 2026. See Collibra’s current docs for status Estates already on Collibra workflows
Informatica OneLake connector for files and tables Documented as data movement and integration Over 300 sources into OneLake. MCP servers in Microsoft Foundry MCP servers announced as available May 2026 Estates that move data into OneLake
Alation Workspaces, lakehouses, and warehouses, with schemas, tables, and columns Lakehouse tables to semantic models to Power BI reports Connector page covers Fabric Beta, from Alation version 2026.4.1 Estates already on Alation

Read each row against your own estate, not against the other rows.


How did we rank these catalogs for Microsoft Fabric?

We fixed six criteria before scoring any vendor. Each can be checked against the vendor’s own docs.

  • Fabric item coverage. Which Fabric item types does the connector catalog? Workspaces, lakehouses and warehouses, semantic models, reports, pages, and visuals, or OneLake directly?
  • Lineage depth. Does lineage reach from external sources through Fabric into semantic models and reports? Testing lineage directly before buying beats reading a feature list.
  • Cross-platform reach. Does the same graph reach Databricks, Snowflake, BigQuery, and Redshift? Most Fabric estates run at least one of them.
  • Governance depth. What does the vendor’s own docs say about stewardship, policy, and compliance? With Purview Data Governance retiring, this criterion also asks where glossary, ownership, and policy live after the move.
  • AI agent and MCP support. Can the catalog’s context reach an AI agent? MCP is the Model Context Protocol, an open-source standard for connecting AI applications to external systems. This is the fastest-moving criterion.
  • Stated status. Is the connector GA or Beta, per the vendor’s own docs?

The native option is first because it is the checkable answer to what you already have. Atlan is second by the same rule as the others. The rule weighs Fabric item types, cross-platform reach, and stated GA status. Alation is last because its docs label the connector Beta. A vendor moves up when its own docs supports it.


OneLake catalog: the native baseline

Microsoft’s November 12, 2026 announcement makes Fabric its data governance solution. It calls the OneLake catalog “the single foundation for governing data across your entire estate.”

Purview Data Governance will be retired a year from the announcement, with support ending November 12, 2027. Microsoft Purview stays focused on data security and compliance. That means classifying, labeling, and protecting sensitive data, and preventing data loss across your estate and AI. Microsoft Learn adds that Unified Catalog and classic Purview data governance are in maintenance mode through November 12, 2027. New accounts can no longer be created.

If you run Purview Data Governance, read the retirement guide first. The migration plan then walks through five steps, from assessment to cutover. What Microsoft Purview is covers the rest of the product.

What the OneLake catalog offers


Per Microsoft’s overview, it has three experiences. Explore finds Fabric items. Govern shows governance health, recommended actions, and admin controls. Secure covers roles and access.

It is embedded in Teams, Excel, and Copilot Studio.

Microsoft’s announcement adds that it governs data across Fabric, Azure, and third-party sources without copying data.

Fabric also reads Azure Databricks through a mirrored Unity Catalog. Only the catalog structure is mirrored. The data is read through shortcuts. See the OneLake catalog guide for daily use.

James Serra, a solution architect at Microsoft, describes the scope: “Fabric lineage is mostly scoped within Fabric, not across the full data estate.”

He also notes the Explore tab is “primarily permission-scoped.” Users see only items they can already access.

Microsoft itself says some organizations have needs that reach beyond what is in Fabric today. That is why it names third-party providers. For where Purview’s own coverage stops, see Purview data governance coverage. The 20-question checklist turns this into questions for a vendor demo.

If Fabric is your only serious analytics platform, the OneLake catalog is enough to start.


Atlan: cross-platform context for a Fabric estate

Atlan is second here by the page’s own rule. Its Fabric connector is generally available and described at the item level.

Microsoft’s announcement names Atlan among the third-party providers Fabric integrates with.

Atlan’s Fabric connector:

  • Catalogs workspaces, lakehouses, warehouses, semantic models, reports, dashboards, dataflows, and data pipelines, down to column level, with end-to-end lineage.
  • Reached general availability with v2.0, which shipped in August 2026. It was announced on September 29, 2026 at FabCon Europe, per BusinessWire and Atlan’s docs.
  • Connects to more than 100 sources, so one graph reaches Databricks, Snowflake, BigQuery, and Redshift. See why AI agents need an enterprise context layer.
  • Uses Azure API Management as a gateway and calls metadata APIs only, per the setup guide.
  • Context Lakehouse stores context as open Apache Iceberg tables in OneLake that Fabric can query directly.
  • Context reaches people in Microsoft Teams and agents in Copilot Studio. Atlan is available in Microsoft Marketplace.

For teams leaving Purview Data Governance, Migration Studio is in private preview. It reads Purview Data Governance with read-only access and checks the plan against Atlan before writing.

The governance lead approves where each object lands. A reconciliation report then compares what landed with the plan. The migration plan has the steps.

Related reading: the context layer for AI, MCP, and what a context graph is.

It fits an estate that has grown past one platform. A Fabric-only shop with no agent plans can start with the OneLake catalog.


Collibra: structural metadata for Fabric lakehouses and warehouses

Collibra announced its Microsoft Fabric integration on June 26, 2026. Its docs describes what it ingests.

What Collibra lists:

  • Fabric lakehouses, with their files and tables.
  • Fabric warehouses, with schemas, tables, views, and columns.
  • SQL Server databases, schemas, tables, and columns. Column-level detail uses a JDBC connection.
  • Items from a mirrored Azure Databricks Unity Catalog in Fabric.
  • Structural relationships stay intact, such as columns to tables to schemas.
  • Metadata syncs on a schedule without moving the underlying data.
  • One Fabric synchronization capability per Azure tenant.

Collibra’s post also describes giving AI agents governed Fabric data to reason over. Confirm the current status in Collibra’s docs.

Collibra fits an estate that already runs Collibra governance workflows and wants Fabric brought into that deployment.


Informatica: data movement into OneLake and an agentic path

Informatica’s strength in the Fabric story is moving data. It also offers MCP servers through Microsoft Foundry.

What Informatica lists:

  • A Microsoft Fabric OneLake connector that reads from and writes to OneLake. It handles flat files and Avro, JSON, ORC, and Parquet, plus Delta and Iceberg in advanced mode.
  • Cloud Data Integration with Mass Ingestion and change data capture for Fabric Data Warehouse. It ingests from over 300 enterprise sources into OneLake or Fabric Data Warehouse, per Informatica’s May 2026 announcement.
  • Headless IDMC MCP servers, available in Microsoft Foundry. Agents can use them for governance, metadata search, and job management.
  • A listing as a Design Partner for Microsoft Fabric.

Informatica fits an estate that moves data into OneLake first and builds its agent path through Foundry.


Alation: Fabric support through an open connector

Alation’s Fabric connector overview says the connector is currently in Beta. It is available from Alation version 2026.4.1 on Alation Cloud Service, and you contact Alation to enable it.

What Alation lists:

  • The connector finds Fabric workspaces and adds their lakehouses and warehouses to the catalog.
  • It sets up a companion RDBMS data source for each workspace. That source extracts SQL metadata from the Fabric SQL analytics endpoints.
  • It catalogs schemas, tables, and columns for lakehouses and warehouses.
  • Lineage runs from lakehouse tables through a semantic model to Power BI reports.

Alation fits an estate already on Alation that is comfortable adopting a Beta connector. Alation’s release notes page did not load when we checked, so confirm the current status in its docs.


When do you need a third-party catalog instead of just the OneLake catalog?

Three signals, credited to the Microsoft Fabric governance overview, show that native coverage is no longer enough.

  1. The estate runs non-Microsoft platforms that need the same graph.
  2. AI agents need Fabric metadata alongside sources outside Fabric.
  3. Governance has outgrown a single tool.

A fourth signal applies to Purview Data Governance customers. You need somewhere for glossary, owners, and data products to land before support ends on November 12, 2027. Microsoft says customers with contract obligations or in regulated industries should talk to their account team early.

Coexist, extend, or replace is the decision. Many teams keep Purview for sensitivity labels and data loss prevention, and move governance to the OneLake catalog, a third-party catalog, or both. That matches the split in Microsoft’s announcement. The alternatives to Purview Data Governance page compares the options, and Atlan and Purview covers running them together.

The added layer reaches the systems that Microsoft’s native scope covers less. The question is not whether the OneLake catalog is good enough. It is whether your estate has grown past what “inside Fabric” covers.


How does Fabric lineage depth compare across these catalogs?

Lineage is the path data takes from source to report. Each vendor covers a different slice of it.

  • Atlan. Per its lineage docs, with the Scanner API disabled the graph covers lakehouse and warehouse tables and columns, semantic model tables and columns, and external SQL sources. It runs from semantic model to report to page, with table, column, and measure lineage to pages and visuals. Pipeline copy activity gets table-level lineage. With the Scanner API enabled, pages and visuals are not in the graph. Dataflow Gen2 (CI/CD) lineage needs the Contributor role on each workspace that holds those items.
  • Alation. Lakehouse tables through a semantic model to Power BI reports.
  • Collibra. Structural relationships between harvested assets.
  • OneLake catalog. Mostly scoped within Fabric, per James Serra.

Test any of these on your own reports before you commit. A lineage claim only counts once it appears on your data.


Can AI agents use Microsoft Fabric metadata through these catalogs?

Four vendors give four different answers, and the answers change fast. This is the newest of the six criteria.

It differs from Fabric’s own data agents, which turn a question into SQL, DAX, or KQL against a semantic model inside Fabric. The catalog question is about an agent that also reaches metadata outside Fabric.

Atlan connects to the Model Context Protocol to deliver business context to agents.

Informatica’s Headless IDMC MCP servers are available in Microsoft Foundry.

Collibra’s post describes agent-ready context from Fabric data. The OneLake catalog is embedded in Foundry, per Microsoft’s announcement. For Alation, check the current docs.

An agent needs the same lineage, definitions, and access boundaries a human steward uses. These pages go deeper:

Pick a catalog that can answer this question now, or plan to revisit it within a year.


What does a data catalog for Fabric cost?

Microsoft says governance in the OneLake catalog is included in Fabric capacity. It does not bill it through separate meters.

Collibra, Informatica, Alation, and Atlan each publish their own terms. Ask each for a quote that covers your connectors and users. Add the cost of the move itself if you are leaving Purview Data Governance. The context layer ROI page helps you size the return first.

The sources we cite give no deployment time. Ask each vendor for a dated plan.


How to choose the right catalog for your Fabric estate

The choice mostly comes down to one question. Does the estate stay inside Fabric, or does it already span other platforms and AI agent work?

If your Fabric estate… Consider… Why
Is single-tenant and Microsoft-only OneLake catalog, with Purview for security and compliance Microsoft’s stated governance solution, included in Fabric capacity
Also runs Databricks, Snowflake, BigQuery, or Redshift Atlan Generally available Fabric connector in a graph that reaches those platforms
Is already on Collibra governance workflows Collibra Its Fabric integration brings lakehouse and warehouse metadata into the same deployment
Puts moving data into OneLake first Informatica Its connector and Cloud Data Integration move data into OneLake
Is already on Alation and can adopt a Beta connector Alation Its Fabric connector catalogs workspaces, lakehouses, and warehouses
Needs AI agents to reach Fabric metadata today Atlan, or Informatica’s Foundry path Check each vendor’s current docs before you commit

Choose by estate shape, not company size. A Microsoft-only shop that adds a catalog it does not need yet pays for a layer it will not use. The simpler option is sometimes the right one.


Why the right Fabric catalog depends on what sits outside Fabric

The OneLake catalog is enough for a pure Microsoft estate. Microsoft’s direction is clear: governance moves into Fabric, and Purview Data Governance retires on November 12, 2027.

Once Databricks, Snowflake, or an agent workflow enters the picture, the six criteria decide.

Status changes faster than capability here. A Beta connector or a new MCP server can move a vendor within a year. How to build an AI agent harness and what is context engineering touch the agent criterion most. After you choose, how to implement an enterprise context layer for AI is the next step.


FAQs about data catalogs for Microsoft Fabric

Short answers to the questions readers ask most.

1. What is the difference between OneLake Catalog and Microsoft Purview?


The OneLake catalog is Fabric’s own catalog, with Explore, Govern, and Secure experiences. It is Microsoft’s data governance solution going forward. Microsoft Purview stays focused on security and compliance, such as labeling sensitive data and preventing data loss. Purview Data Governance is retiring, with support ending November 12, 2027.

2. Is Microsoft Purview Data Governance being retired?


Yes. Microsoft announced on November 12, 2026 that Purview Data Governance will retire a year later. Support ends November 12, 2027. Per Microsoft Learn, Unified Catalog and classic Purview data governance are in maintenance mode, and new accounts can no longer be created. Purview’s security and compliance work continues.

3. When do you need a third-party data catalog for Microsoft Fabric?


You need one when your estate runs platforms like Databricks or Snowflake that share a graph. You also need one when AI agents want Fabric metadata alongside other sources. A third reason is a landing place for Purview Data Governance assets before support ends. A Microsoft-only estate usually does not need one yet.

4. How do I connect Databricks Unity Catalog to Microsoft Fabric?


Microsoft Learn describes a mirrored Unity Catalog in Fabric. Fabric mirrors the Azure Databricks catalog structure and reads the data through shortcuts, with no copy. A third-party catalog that connects to both Fabric and Databricks is a separate way to put both in one metadata graph.

5. Can AI agents use Microsoft Fabric metadata via MCP?


Partially, and it differs by vendor. Atlan’s MCP Server connects Fabric metadata to AI agents. Informatica’s Headless IDMC MCP servers are available in Microsoft Foundry, and Collibra’s post describes agent-ready context from Fabric data. Check each vendor’s current docs.

6. Is Microsoft Purview included with Fabric, or is it a separate license?


Per Microsoft’s November 12, 2026 announcement, governance in Fabric is included in Fabric capacity rather than billed through separate meters. Microsoft Learn says Purview provides information protection and data loss prevention for supported Fabric data. Check Purview licensing with your Microsoft account team.

7. What does Alation’s Microsoft Fabric connector support today?


Alation’s connector overview says the Fabric connector is currently in Beta and available from Alation version 2026.4.1 on Alation Cloud Service. It finds workspaces and adds their lakehouses and warehouses to the catalog, with schemas, tables, and columns. Lineage runs from lakehouse tables through a semantic model to Power BI reports.

8. What does Collibra’s Microsoft Fabric integration catalog?


Collibra announced the integration on June 26, 2026. Its docs list Fabric lakehouses and warehouses, SQL Server databases, and items from a mirrored Azure Databricks Unity Catalog. Structural relationships stay intact. Metadata syncs on a schedule without moving data.

9. Can Informatica move data into OneLake, or only catalog what is already there?


Informatica documents a OneLake connector that reads and writes files and tables. Its Cloud Data Integration ingests from over 300 enterprise sources into OneLake or Fabric Data Warehouse, per its May 2026 announcement. Headless IDMC MCP servers are also available in Microsoft Foundry for agents.

10. What is the most common mistake when evaluating a Fabric data catalog?


Treating a connector’s status as settled instead of checking the vendor’s own docs. Alation’s connector overview, for example, labels its Fabric connector Beta. A roadmap slide or a sales call is not a documented capability. Verify status before you compare anything else.


Sources

  1. A next step in the evolution of the Microsoft data governance strategy, Microsoft Security Blog, November 12, 2026

  2. Learn about data governance with Microsoft Purview, Microsoft Learn

  3. OneLake catalog overview, Microsoft Learn

  4. What is Microsoft Fabric, Microsoft Learn

  5. Microsoft Fabric mirrored catalog from Azure Databricks, Microsoft Learn

  6. The OneLake catalog in Fabric: Explore, Govern, Secure, James Serra

  7. What is the Model Context Protocol, modelcontextprotocol.io

  8. Fabric OCF connector overview, Alation documentation (docs.alation.com), accessed November 13, 2026

  9. Govern your Microsoft Fabric estate with Collibra, Collibra blog (collibra.com), June 26, 2026

  10. About the Microsoft Fabric integration, Collibra documentation (productresources.collibra.com), accessed November 13, 2026

  11. Introduction to Microsoft Fabric OneLake connector, Informatica documentation (docs.informatica.com), accessed November 13, 2026

  12. Informatica World 2026: Informatica deepens collaboration with Microsoft, StorageNewsletter, May 25, 2026

  13. Informatica is a Design Partner for Microsoft Fabric, Informatica (now.informatica.com)

  14. How Atlan connects to Microsoft Fabric, Atlan docs

  15. What lineage does Atlan extract from Microsoft Fabric, Atlan docs

  16. Set up Microsoft Fabric with Azure API Management, Atlan docs

  17. Atlan brings governed context to Microsoft Fabric and OneLake, BusinessWire via FinancialContent

Share this article

signoff-panel-logo

Atlan is the Context Layer for AI. It translates business knowledge, including data definitions, working procedures, and governance policies, into context AI can actually use. This knowledge lives in a single Enterprise Data Graph that every team and AI agent can reach.

In Atlan's AI Labs benchmark, adding this context improved AI's text-to-SQL accuracy by 38%.

Atlan is recognized as a Leader across multiple Gartner reports and Forrester Waves, and is trusted by over 400 enterprises representing $10T+ in market cap, including Mastercard, Workday, General Motors, CME Group, HubSpot, FOX, Virgin Media O2, and Elastic.

Bridge the context gap.
Ship AI that works.