Data & Storage · Integration
Power BI
Add Power BI to your product for your customers, and give your AI agents governed access to it.
Power BI holds the reporting a customer's business already trusts, and an embedded Power BI integration puts that inside your product instead of a screenshot. The objects are workspaces, the semantic models and datasets inside them, reports, dashboards and dataflows, plus the refresh history that says whether a figure is current. Two details govern the build. Row level security is defined in the model, so an embed token has to carry the right identity or a viewer sees numbers meant for somebody else. And a refresh is asynchronous and capped by a daily allowance, so your product schedules one rather than demanding it. fastn holds each tenant's service principal credentials and tracks Microsoft's API changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Power BI tenant so your product lists the workspaces and reports they already publish.
Generate an embed token that carries the viewer's identity, so row level security decides what each person sees.
Trigger a dataset refresh after your product loads new figures, then read refresh history to confirm it landed.
Read dataset and dataflow metadata while onboarding, so your screens list the reports that tenant genuinely owns rather than a fixed set.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which datasets failed their last refresh and when each was last current.
An agent answers a question from a report's figures for one workspace, with the workspace it read recorded.
An agent checks whether a dashboard's underlying dataset is stale before it quotes a number from it.
Example prompt
Which datasets in this workspace failed to refresh overnight, and which reports depend on them?
Set up Power BI in 4 steps
- 01Enable the Power BI connector from your fastn dashboard.
- 02Have each customer authorise their own Power BI 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 Power BI integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Power BI integration without building it. Your customers connect their own Power BI 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 Power BI update is not your on-call problem.
- One integration serves your product and your agents. The same governed Power BI 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
Tableau
Looker
Microsoft FabricOften used alongside
Tools the same teams tend to run next to Power BI, across other categories.
Anthropic Claude
OpenAI
Hugging FacePower BI integration FAQ
How do I add a Power BI integration to my product?
Enable the Power BI connector in your fastn dashboard, then let each customer authenticate their own Power BI account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Power BI client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Power BI account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Power BI 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 Power BI 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 reports which datasets failed their last refresh and when each was last current.
Who maintains the Power BI integration?
fastn does. When Power BI 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 Power BI 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 Power BI 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 Power BI integration?
A common starting point: let a customer connect their own Power BI tenant so your product lists the workspaces and reports they already publish. 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 Power BI integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Power BI does not change your per-connector cost. You can start free with 3 connected accounts.
Add Power BI to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.