What Klyrova does with Microsoft Fabric
Klyrova is a Microsoft Fabric AI agent that works on top of the data you already have in Fabric. It connects to your warehouses, lakehouse SQL analytics endpoints, SQL databases, mirrored databases and KQL databases with your own Microsoft sign-in, so there are no passwords or service principals to set up. You ask a question; the agent writes read-only T-SQL (or KQL for a KQL database), runs it, reads the rows and answers. Keep the answer and it becomes a dashboard whose every chart is drawn from a stored query, replayed on each refresh with no AI involved.
Which Fabric items you can connect
| Fabric item | Klyrova queries it with | Notes |
|---|---|---|
| Warehouse | T-SQL | Dashboards, filters, data models and import. |
| Lakehouse | T-SQL, through its SQL analytics endpoint | Chat with your lakehouse tables as SQL. |
| SQL database | T-SQL | Dashboards, filters, data models and import. |
| Mirrored database | T-SQL, through its SQL analytics endpoint | Report on mirrored data without touching the source system. |
| KQL database | KQL | Answers and dashboards; filters and data models don't work on KQL yet. |
Connecting with your Microsoft account
- In Data sources, choose Add source and pick Microsoft Fabric.
- Sign in with your work or school Microsoft account and approve read access to your Fabric workspaces and items. The first time you add a SQL item or a KQL database, Microsoft also asks you to let Klyrova query it on your behalf. Personal Microsoft accounts can't hold Fabric workspaces, so they aren't offered.
- Klyrova lists every warehouse, lakehouse, SQL database, mirrored database and KQL database your account can see, grouped by workspace. Tick the ones you want and add them.
Klyrova keeps the sign-in as an encrypted refresh token and asks Microsoft for a short-lived access token for each query. If Microsoft stops accepting it, because a password changed or an administrator revoked access, the Data sources page shows Reconnect. Some organisations only let people approve apps that an administrator has approved; there, an administrator gives consent once for everyone.
The address of each item comes from Fabric itself. Klyrova only sends your Microsoft token to Microsoft-hosted endpoints, so a source can't be pointed anywhere else.
Your Fabric permissions are Klyrova's permissions
Because Klyrova queries Fabric as you, it can read exactly what your account can read, and nothing more. If you want a dashboard to see less, connect it with an account that has narrower access, or limit that account inside the warehouse with T-SQL GRANT and DENY as you would in SQL Server.
Dashboards belong to the person who built them and refresh with that person's sign-in, even when they are offline. When you share a dashboard, viewers see its results without getting any access to Fabric, and editors can only ask the agent to query the sources you choose to allow.
How it stays read-only
- T-SQL is parsed with Microsoft's own parser and must be exactly one SELECT, with no
INTO,EXEC,OPENROWSETor anything that writes. - KQL must be a query: control commands, the ones starting with a dot, are refused.
- Lakehouse and mirrored database SQL analytics endpoints are read-only in Fabric itself, which adds a lock of Microsoft's own.
An example: chat with a Fabric lakehouse
"From the sales lakehouse, what were our top five product categories by margin this quarter?"
The agent read the lakehouse's tables through its SQL analytics endpoint and ran:
SELECT TOP (5)
p.category,
SUM(f.revenue) AS revenue,
SUM(f.revenue - f.cost) AS margin,
CAST(100.0 * SUM(f.revenue - f.cost) / NULLIF(SUM(f.revenue), 0)
AS decimal(5, 1)) AS margin_pct
FROM dbo.fact_sales AS f
JOIN dbo.dim_product AS p ON p.product_key = f.product_key
WHERE f.order_date >= DATEADD(quarter, DATEDIFF(quarter, 0, GETDATE()), 0)
GROUP BY p.category
ORDER BY margin DESC;
Kept as a dashboard, it refreshes on the schedule you choose: once a day on Free, as often as every five minutes on Pro and Teams.
Fabric notes
- Queries run in your Fabric workspace like any other query, so they use your capacity. Refreshes run only the stored queries; on Pro and Teams you can instead import a warehouse or lakehouse data model into a fast copy up to eight times a day, so filters stop reaching Fabric between imports.
- Klyrova sits beside Power BI rather than replacing your semantic models. See how the two compare.
Microsoft Fabric questions
Do I need a service principal or a password?
No. Klyrova uses your own Microsoft sign-in, with delegated permissions, so it acts as you and nothing is typed in.
Which Fabric items does Klyrova support?
Warehouses, lakehouses through their SQL analytics endpoint, SQL databases, mirrored databases and KQL databases.
Can colleagues see my Fabric data through Klyrova?
Only through dashboards you share. Viewers see the results; editors can ask the agent to query only the sources you allow. Nobody receives your Microsoft access.
Why does my organisation need to approve Klyrova?
Some tenants only let people approve apps an administrator has approved. In that case an administrator grants consent once and everyone can connect.
Can Klyrova write to my warehouse?
No. Every T-SQL statement must be a single SELECT and every KQL request a query; anything else is refused before it reaches Fabric.
Updated 30 October 2026
