Data & Storage · Integration
Fabric
Add Fabric to your product for your customers, and give your AI agents governed access to it.
Embed a Fabric integration so your customers can connect their own Fabric account and work the records they already keep there from inside your product. Because every customer models data differently, field and schema mapping is configuration per tenant rather than code, and pagination and throttling on large reads are handled for you. fastn maintains per-customer authorisation and API upkeep, so onboarding another account is configuration rather than a release from you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Fabric account so their records are available inside your product.
Read records per tenant so one customer's data never mixes with another's.
Write records back so a change made in your product is reflected where the data lives.
Refresh reads on a schedule so your product is not working from a stale copy.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads records before answering a question grounded in the customer's own data.
An agent creates or updates a record within governed permissions, with each call logged.
An agent reads on a schedule and reports what changed since the previous run.
Example prompt
Read the records updated in the last 24 hours and summarise what changed.
Set up Fabric in 4 steps
- 01Enable the Fabric connector from your fastn dashboard.
- 02Have each customer authorise their own Fabric account, so calls run under their credentials rather than a shared key.
- 03Decide which records, datasets and fields your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Fabric integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Fabric integration without building it. Your customers connect their own 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 Fabric update is not your on-call problem.
- One integration serves your product and your agents. The same governed 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
Microsoft Fabric
Databricks
SnowflakeOften used alongside
Tools the same teams tend to run next to Fabric, across other categories.
Anthropic Claude
OpenAI
Hugging FaceFabric integration FAQ
How do I add a Fabric integration to my product?
Enable the Fabric connector in your fastn dashboard, then let each customer authenticate their own Fabric account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no 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 Fabric account?
Yes. Every connection is scoped to the individual customer, so each authorises their own 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 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 reads records before answering a question grounded in the customer's own data.
Who maintains the Fabric integration?
fastn does. When 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 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 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 Fabric integration?
A common starting point: let each customer connect their own Fabric account so their records are available inside your product. 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 Fabric integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Fabric does not change your per-connector cost. You can start free with 3 connected accounts.
Add Fabric to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.