Question 1

How is this different from the Power BI SQL connector?

Accepted Answer

The SQL connector reads Power BI's underlying datasets via the XMLA endpoint or direct dataset queries. The REST API connector reads Power BI Service metadata — workspaces, reports, dashboards, refresh history, and usage analytics. Use SQL for raw data, REST API for service-level insights.

Question 2

Can Ana execute DAX queries?

Accepted Answer

Yes. The Power BI REST API supports executing DAX queries against any dataset the authenticated user has access to. Ana can run ad-hoc DAX expressions and join the results with warehouse data in a single question.

Question 3

Does this work with Power BI Embedded?

Accepted Answer

Yes. The REST API connector works with Power BI Service, Power BI Premium, and Power BI Embedded. The setup is the same — register an Azure AD app with the right scopes and authorize TextQL.

Question 4

How are tokens secured?

Accepted Answer

Azure AD OAuth tokens are encrypted at rest in TextQL's credential vault. When Ana makes a Power BI API request, tokens are injected at the network boundary. Ana's Python sandbox sees only sanitized request helpers — never the raw token.

Question 5

Per-org or per-user OAuth?

Accepted Answer

Both are supported. Per-org uses a service principal with admin-level access to all workspaces. Per-user means each TextQL user signs in with their own Microsoft account, and Ana inherits their individual Power BI permissions for every query.