Connect Microsoft Fabric

Nothing Broke. That's the Problem.

The expensive warehouse incidents never announce themselves. A monthly reconciliation comes out a few cents off per row. Every pipeline ran green. Every dashboard rendered. Nobody was paged. Three weeks earlier, a table was rebuilt and an `Amount` column went from `decimal(18,2)` to `float` — and the database did exactly what a database is supposed to do: it stored the values, coerced the types, and answered every query without complaint.

Recipe: SQL Server Estate Governance

Five Questions a Governed Warehouse Answers Without a Meeting

Every team that owns a Fabric Warehouse or a SQL Server estate fields the same handful of questions. They arrive in stand-ups, in review threads, in messages from someone who needs an answer before lunch. Individually they look small. Collectively they are where warehouse ownership goes: a day tracing a type, an afternoon explaining a join, a standing meeting whose only purpose is to reconstruct what everyone used to know.

Recipe: CI Drift Gate for Fabric · First Governed Import for Fabric · Generate T-SQL DDL from the Governed Model · SQL Server Estate Governance

A Catalog That Agrees With Everything Can Warn You About Nothing

Here is a design flaw hiding inside a lot of metadata tooling. Point it at your Fabric Warehouse and it crawls the schema, recording what it finds. Point it again next week and it records what it finds *now*. The tool is always current, always accurate, and useless for the one job that matters: telling you something changed that should not have.

Your Warehouse Is a Junction, Not a Destination

Draw your data estate on a whiteboard and the warehouse always ends up in the middle of the picture. That placement is accurate about traffic and misleading about authority. A Fabric Warehouse is where things pass through: transformations land tables in it, ingestion tools feed it, semantic layers and reports and notebooks and agents read out of it, and downstream systems copy from it. Very little of what a warehouse table *means* actually originated in the warehouse.

Pasting Your Schema Into the Prompt Is Not Grounding

The standard way to make an AI agent useful against a warehouse is to give it the schema: dump the DDL, or scrape `INFORMATION_SCHEMA` into a text blob, and paste it into the context window with "use this to answer questions about our data." It works well enough to demo, which is why it survives long enough to cause problems.

From INFORMATION_SCHEMA to a Governed Model: A Microsoft Fabric Walkthrough

Your warehouse already publishes a complete, machine-readable description of itself. Every Fabric Warehouse and SQL analytics endpoint answers `SELECT ... FROM INFORMATION_SCHEMA.COLUMNS` with the tables, the columns, the types, the nullability. Every one of them answers `INFORMATION_SCHEMA.TABLE_CONSTRAINTS` with the keys. That description is the whole input CoreModels needs to build a governed model of the estate and then guard it.

Recipe: Blank Fabric project · First Governed Import for Fabric · Generate T-SQL DDL from the Governed Model

The Fabric Integration API: Every Route, Every Role, Every Payload

CoreModels exposes vendor integrations over two HTTP surfaces, and the split is not decoration. The interactive surface under `graph/integrations/...` is what a person or a notebook calls with a normal CoreModels login token. The machine-to-machine surface under `v1/...` accepts user API keys and is what a build pipeline calls. Both require authentication; both then enforce a per-project role on top of it.

Governing a Fabric Warehouse from an Agent: the MCP Integration Tools in Practice

An agent has a context window, not a file system. That single constraint shapes how AI-driven governance of a Microsoft Fabric warehouse actually works: the model cannot paste a forty-megabyte INFORMATION_SCHEMA extract into a tool call, cannot hold your SQL credentials, and should not be trusted to invent a schema comparison in its head. What it *can* do is call a small set of typed tools that run the real audit engine server-side and hand back a verdict.

Wiring the Drift Gate: Continuous Schema Governance for Fabric and SQL Server

Schema governance that lives in a document is not governance. It is a document. The version that actually holds is the one a pipeline can fail on — a single number, checked on every change, with a trail behind it that shows whether the estate is getting better or worse.

Recipe: CI Drift Gate for Fabric

Identity, Types and Honest Loss: What a Fabric Import Actually Writes

Governance starts with a question that sounds trivial and is not: what *is* a table, once it stops being a table?

Recipe: SQL Server Estate Governance