Skip to content
Database ⇄ Analytics

DuckDB to Microsoft Power Bi integration — real-time data sync

Keep DuckDB and Microsoft Power Bi in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect DuckDB and Microsoft Power Bi

Give Microsoft Power Bi the users, events, and records that live in DuckDB in real time, and sync the cohorts and scores Microsoft Power Bi computes back into DuckDB where your applications read them.

Microsoft Power Bi is a read-only source: Stacksync reads its data in real time and delivers it into DuckDB, so DuckDB always reflects the current state of Microsoft Power Bi — without exports, scripts, or schedulers.

A database holds the rows your business runs on: the users, events, orders, and records that every service reads and writes. Microsoft Power Bi is where people make sense of them, as dashboards, funnels, cohorts, and metrics. Moving the data from DuckDB into Microsoft Power Bi usually means a hand-built extract or a change-data-capture pipeline that breaks the moment a column is renamed, and reporting that always trails last night's load.

Common use cases

  • 01 Load dataset Refresh History into an operational database to alert on-call teams when scheduled refreshes fail or run long.
  • 02 Sync admin Activity Events into a warehouse for tenant-wide security, access, and usage reporting.
  • 03 Use DuckDB as a transform step: read synced Parquet exports, aggregate with SQL, and write results back to an operational database.
  • 04 Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.

Common sync patterns

Where Microsoft Power Bi tracks product events: behavior onto stored records

Signup, usage, and lifecycle events captured in Microsoft Power Bi sync into DuckDB as rows, so applications and internal tools can read behavioral data next to the records they already keep.

Where Microsoft Power Bi builds cohorts or scores: results your services can read

Segments, cohorts, or scores computed in Microsoft Power Bi sync back into DuckDB, where the services that read from the database act on them at query speed without calling the analytics API.

Analytics on live operational data, minus the pipeline

The users, events, orders, and records stored in DuckDB land in Microsoft Power Bi as they change, so dashboards, funnels, and metrics run on current data instead of last night's extract.

What you can sync between DuckDB and Microsoft Power Bi

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

DuckDB objects Microsoft Power Bi objects How this pairing syncs
External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. Users and Access Workspace users and roles read via GET /groups/{id}/users or the admin scanner APIs; read for access reviews and identity reconciliation against an IdP. External files (Parquet/CSV/JSON) is specific to DuckDB and Users and Access to Microsoft Power Bi — each maps to any object or custom field on the other side.
Attached databases Additional database files or external systems attached into one session for cross-source queries. Datasets (Semantic Models) Tabular models behind reports; their rows are read with DAX via POST datasets/{id}/executeQueries, and datasource and refresh metadata via REST list endpoints. Attached databases is specific to DuckDB and Datasets (Semantic Models) to Microsoft Power Bi — each maps to any object or custom field on the other side.
Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. Reports Report definitions and metadata read via GET /reports and per-workspace GET /groups/{id}/reports; enumerated to mirror the content inventory into a catalog. Database files is specific to DuckDB and Reports to Microsoft Power Bi — each maps to any object or custom field on the other side.
Schemas Namespaces within a database used to organize tables in sync outputs. Dashboards and Tiles Dashboards and their pinned tiles read via GET /dashboards and /dashboards/{id}/tiles; inventoried to map dashboard content back to its source datasets. Schemas is specific to DuckDB and Dashboards and Tiles to Microsoft Power Bi — each maps to any object or custom field on the other side.
Tables Columnar tables created via SQL; the destination for materialized sync data. Dataflows Power Query ETL definitions read via GET /groups/{id}/dataflows; used to document lineage from upstream sources into datasets. Tables is specific to DuckDB and Dataflows to Microsoft Power Bi — each maps to any object or custom field on the other side.
Views SQL views used to shape or filter data for downstream consumers. Datasources and Gateways The connections behind datasets and dataflows and the on-premises gateways serving them, read via REST for lineage and dependency mapping. Views is specific to DuckDB and Datasources and Gateways to Microsoft Power Bi — each maps to any object or custom field on the other side.

How changes propagate between DuckDB and Microsoft Power Bi

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

DuckDB Microsoft Power Bi Interval-based propagation

DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.

DeliveryMicrosoft Power Bi does not accept inbound record writes, so this direction carries requests rather than records: Microsoft Power Bi's output flows back as field updates on the originating DuckDB records.

Microsoft Power Bi DuckDB Interval-based propagation

DetectionStacksync polls Microsoft Power Bi for changes on an incremental schedule, reading only records changed since the previous pass. Pull-based: no webhooks or change-data-capture.

DeliveryEach detected change is applied to DuckDB as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
  • Microsoft Power Bi: Endpoints throttle per user and per app and return HTTP 429 with a Retry-After header. Execute Queries allows up to 120 requests per minute per user and caps a query at 100,000 rows (or 1,000,000 values) and 15 MB; admin scanner metadata APIs are limited to about 500 requests per hour with 16 concurrent.
What ships with DuckDB ⇄ Microsoft Power Bi

Connect DuckDB and Microsoft Power Bi for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Microsoft Power Bi connection.

Real-time

Real-time sync

Changes in DuckDB or Microsoft Power Bi instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever DuckDB or Microsoft Power Bi data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single DuckDB or Microsoft Power Bi record.

Observability

Monitoring

Track your DuckDB ⇄ Microsoft Power Bi sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between DuckDB and Microsoft Power Bi.

How the DuckDB and Microsoft Power Bi connectors work

DuckDB

Integration surface
In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
Authentication
None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
Change detection
Polling or full re-reads; no change feed or transaction log API
Capabilities
read · write
Rate limits
No API rate limits; throughput is bounded by local compute and I/O

Microsoft Power Bi

Integration surface
Power BI REST API, including the Execute Queries (DAX) endpoint and admin scanner APIs; a read-write XMLA endpoint is available on Premium, Premium-Per-User, and Fabric capacity.
Authentication
Microsoft Entra ID (Azure AD) OAuth 2.0 bearer tokens. Supports delegated user tokens and app-only service principals; service principals must be enabled under the tenant's Developer settings and granted workspace access. Tenant-wide admin reads require the Tenant.Read.All scope.
Change detection
Pull-based: no webhooks or change-data-capture. Content is polled via REST list endpoints, dataset changes are inferred from Refresh History and the admin Activity Events audit log, and the scanner API's GetModifiedWorkspaces reports workspaces changed since a given time.
Capabilities
read
Rate limits
Endpoints throttle per user and per app and return HTTP 429 with a Retry-After header. Execute Queries allows up to 120 requests per minute per user and caps a query at 100,000 rows (or 1,000,000 values) and 15 MB; admin scanner metadata APIs are limited to about 500 requests per hour with 16 concurrent.
How it works

How to connect DuckDB to Microsoft Power Bi — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate DuckDB and Microsoft Power Bi with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    DuckDB connected
    Microsoft Power Bi connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the DuckDB and Microsoft Power Bi objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · DuckDB ⇄ Microsoft Power Bi
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    DuckDB Microsoft Power Bi
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

DuckDB and Microsoft Power Bi integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 380 integrations available for DuckDB and Microsoft Power Bi.

Popular · 7 of 380
All DuckDB integrations All Microsoft Power Bi integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own