Skip to main content

Microsoft Power BI Connector

Status: In development: its code is written and tested on its own, but it does not work end to end on the platform yet. It cannot be installed.

KindVersionPublisherLicence
Connector1.0.0ZAITRACKApache-2.0

What it does​

Writes the organisation's completed trips, alerts, geofence entries and exits, flagged fuel purchases and fuel drains as rows of a push dataset in its own Power BI workspace, as they happen: tables Trips, Alerts, Geofences and Fuel, ready for its own reports. It signs in as the organisation's own Microsoft Entra app (a service principal with a client secret); the dataset is made on the first rows. Installing it copies the organisation's trips, alerts, geofence visits and fuel findings to its own Power BI tenant, where they are stored in whatever region that tenant is in, which may be outside the GCC. The organisation chooses this by installing it.

  • Regions: AE, US, EU, UK, IN
  • Capabilities: integration.bi.push.rows

How to use it​

Not yet: see its status above.

Configuration​

SettingTypeRequiredAllowed values and default
azure_tenant_idstringyesYour Microsoft Entra directory's ID (or its domain, contoso.onmicrosoft.com)
azure_client_idstringyesThe Entra app ZAITRACK signs in as: a Member or Admin of the workspace, with service principals allowed to use the Power BI APIs
workspace_idstringyesThe Power BI workspace the dataset is in (in its address: /groups//); not My workspace
dataset_namestringnodefault "ZAITRACK"; The push dataset's name: made on the first rows when the workspace has none of that name
push_eventsarraynoThe events written as rows (all by default)

Credentials​

Each is a secret setting of the installation: kept sealed (OpenBao in production), never shown again; Adapter Studio shows it as set.

  • azure_client_secret

Limits​

  • Memory: 256 MB
  • Time per call: 30,000 ms
  • Largest message: 1,048,576 bytes
  • Calls at once: 16
  • Network: only login.microsoftonline.com, api.powerbi.com

Troubleshooting​

  • Credentials refused. The secret settings must be the ones the provider issued for this account and environment (sandbox or live); give them again in Adapter Studio, since they are never shown back.
  • Rate limited. The provider's limit applies to the account: calls are retried with a growing pause; spread scheduled work or ask the provider for a higher limit.
  • Nothing is sent or synced. The installation must be active, its version approved; it reaches only the hosts listed under Limits.
  • Webhooks rejected. The webhook secret must match the one configured at the provider; a request whose signature does not match is refused.

Source​

adapters/connectors/microsoft-power-bi