Data & Storage · Integration
Microsoft Fabric
Add Microsoft Fabric to your product for your customers, and give your AI agents governed access to it.
Embed a Microsoft Fabric integration so your customers can point your product at the analytics estate they already run in their own Fabric workspaces. Fabric holds lakehouse and warehouse tables in OneLake alongside semantic models and pipelines, and every workspace is organised differently, so table and field selection is configuration per customer rather than code. fastn handles per-tenant authentication, capacity-aware throttling and paginated reads, so a large first query does not consume the capacity a customer's reports depend on.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Fabric workspace so your product queries their lakehouse and warehouse tables in place, with no copy to maintain.
Read semantic model metadata so your product offers the measures a customer actually has rather than a fixed list.
Trigger a pipeline or notebook run from your product and read its status back.
Keep reads paginated and capacity-aware so analytics inside your product never starves the customer's own reporting.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent runs a scoped read-only query against the customer's warehouse before it answers.
An agent inspects table and column names to build a correct query instead of guessing a schema.
An agent starts a pipeline run within governed permissions, with the action attributed per tenant.
Example prompt
Query the sales lakehouse for revenue by region for the last two quarters and explain the biggest change.
Set up Microsoft Fabric in 4 steps
- 01Open the Microsoft Fabric connector from your fastn dashboard.
- 02Have each customer authorise their own Fabric workspace with the scopes your product needs.
- 03Map the tables, semantic models and pipelines your product uses, then enable the actions you need.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Microsoft Fabric integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Microsoft Fabric integration without building it. Your customers connect their own Microsoft Fabric account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Microsoft Fabric update is not your on-call problem.
- One integration serves your product and your agents. The same governed Microsoft Fabric connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
Power BI
Databricks
SnowflakeOften used alongside
Tools the same teams tend to run next to Microsoft Fabric, across other categories.
Anthropic Claude
OpenAI
Hugging FaceMicrosoft Fabric integration FAQ
How do I add a Microsoft Fabric integration to my product?
Enable the Microsoft Fabric connector in your fastn dashboard, then let each customer authenticate their own Microsoft Fabric account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Microsoft Fabric client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Microsoft Fabric account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Microsoft Fabric account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Microsoft Fabric integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent runs a scoped read-only query against the customer's warehouse before it answers.
Who maintains the Microsoft Fabric integration?
fastn does. When Microsoft Fabric changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Microsoft Fabric integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Microsoft Fabric reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Microsoft Fabric integration?
A common starting point: connect their own Fabric workspace so your product queries their lakehouse and warehouse tables in place, with no copy to maintain. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Microsoft Fabric integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Microsoft Fabric does not change your per-connector cost. You can start free with 3 connected accounts.
Add Microsoft Fabric to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.