Skip to main content
Use the @bijection/connectors/powerbi entrypoint to declare Power BI resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Datasets

pull: The workspace’s semantic models

The following example matches configuration standard.

Configuration: standard

Case: powerbi/datasets/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: powerbi. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: datasets
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Refresh history

pull: One dataset’s latest refresh entries

The following example matches configuration standard.

Configuration: standard

Case: powerbi/refreshes/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: powerbi. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: refreshes
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

DAX query

dax: One fixed DAX query computed by Power BI

The following example matches configuration standard.

Configuration: standard

Case: powerbi/query/dax/standard. Connection and resource configuration are declared by this exact case. Credential kind: powerbi. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: rows
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. Read-only access to Power BI semantic models through the Power BI REST API (https://api.powerbi.com/v1.0/myorg/). Nothing here refreshes, edits or deletes a dataset. Power BI computes every query; Bijection reads the answer. The connection is anchored to one workspace (workspaceId setup): GET groups/{workspaceId} must answer that workspace’s id, which is the identity. The credential is the deployment’s envelope: an Entra client credentials grant for a service principal (scope https://analysis.windows.net/powerbi/api/.default) or a bearer. Power BI answers throttling with 429 and Retry-After seconds. datasets.pull reads groups/{id}/datasets once; the reference states no paging and no completeness, so it claims no coverage. A caller with only Read permission receives a subset of properties, so a null field means “not returned”. A dataset missing from a later listing is not withdrawn. refreshes.pull reads one dataset’s latest $top (default and maximum 60) refresh entries, keyed by requestId. An entry is Unknown with no endTime while it runs, then Completed, Failed (with serviceExceptionJson) or Disabled. It requires Write permission on the dataset. query.dax posts one fixed DAX query to executeQueries with includeNulls: true. A DAX result has no key, so the caller declares the key columns; a repeated or null key refuses the page. Numbers are JSON doubles, so Decimal and Currency values are not exact through this API; dates arrive as strings. Documented limits: one query and one table per request, 100,000 rows or 1,000,000 values, 15 MB, 120 query requests per minute per user, the tenant setting “Dataset Execute Queries REST API”, no service principals on datasets with RLS or SSO. A result over the row limit answers 200 with limited rows and an error, which this recipe refuses. The host retains at most 512 KiB per response, so keep results small. The XMLA endpoint is not built: Microsoft documents it only through the Analysis Services client libraries. Nothing here has run against Power BI or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.