Skip to content
Database ⇄ Analytics

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

Keep MarkLogic 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 MarkLogic and Microsoft Power Bi

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

Microsoft Power Bi is a read-only source: Stacksync reads its data in real time and delivers it into MarkLogic, so MarkLogic 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 MarkLogic 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 Read Users and workspace access for periodic access reviews reconciled against an HR or Microsoft Entra ID source of record.
  • 02 Mirror Workspaces, Reports, Dashboards, and Dataset metadata into a catalog database so teams discover Power BI content from a central index.
  • 03 Feed harmonized entities into search and analytics applications as documents change.
  • 04 Sync curated master data from a MarkLogic data hub into operational CRMs and ERPs.

Common sync patterns

One version of each user or account

A user, account, or record corrected in either system updates the other, so the identity your reports group by matches the identity your database stores.

Filter and grouping dimensions kept fresh

Attributes teams slice by, such as plan, region, or account owner, stay current in Microsoft Power Bi because they sync from MarkLogic as they change, instead of going stale after a one-time import.

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

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

What you can sync between MarkLogic 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.

MarkLogic objects Microsoft Power Bi objects How this pairing syncs
Databases & Forests Storage units that define the scope and placement of synced content. 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. Databases & Forests is specific to MarkLogic and Datasets (Semantic Models) to Microsoft Power Bi — each maps to any object or custom field on the other side.
Users & Roles Security principals that govern what an integration credential can read or write. 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. Users & Roles is specific to MarkLogic and Reports to Microsoft Power Bi — each maps to any object or custom field on the other side.
Documents JSON and XML documents, the primary records read from and written to the database. 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. Documents is specific to MarkLogic and Dashboards and Tiles to Microsoft Power Bi — each maps to any object or custom field on the other side.
Collections Named groupings used to scope which documents a sync reads or updates. Dataflows Power Query ETL definitions read via GET /groups/{id}/dataflows; used to document lineage from upstream sources into datasets. Collections is specific to MarkLogic and Dataflows to Microsoft Power Bi — each maps to any object or custom field on the other side.
Semantic Triples RDF data stored alongside documents, queryable with SPARQL for linked-data syncs. Datasources and Gateways The connections behind datasets and dataflows and the on-premises gateways serving them, read via REST for lineage and dependency mapping. Semantic Triples is specific to MarkLogic and Datasources and Gateways to Microsoft Power Bi — each maps to any object or custom field on the other side.
TDE Views Relational projections of documents that let syncs read document data as SQL rows. Refresh History Dataset refresh runs read via GET /datasets/{id}/refreshes, including status, type, and timing, to alert on failed or slow scheduled refreshes. TDE Views is specific to MarkLogic and Refresh History to Microsoft Power Bi — each maps to any object or custom field on the other side.

How changes propagate between MarkLogic 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.

MarkLogic Microsoft Power Bi Interval-based propagation

DetectionStacksync polls MarkLogic for changes on an incremental schedule, reading only records changed since the previous pass. No exposed transaction log.

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 MarkLogic records.

Microsoft Power Bi MarkLogic 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 MarkLogic as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • 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 MarkLogic ⇄ Microsoft Power Bi

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

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

Real-time

Real-time sync

Changes in MarkLogic 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 MarkLogic 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 MarkLogic or Microsoft Power Bi record.

Observability

Monitoring

Track your MarkLogic ⇄ 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 MarkLogic and Microsoft Power Bi.

How the MarkLogic and Microsoft Power Bi connectors work

MarkLogic

Integration surface
REST API (Client API), plus SQL/ODBC access over TDE views and Java/Node client libraries
Authentication
Username/password (digest or basic), with certificate-based options
Change detection
No exposed transaction log; polling on document timestamps/metadata, or server-side triggers that record changes for pickup
Capabilities
read · write

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 MarkLogic 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 MarkLogic 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
    MarkLogic connected
    Microsoft Power Bi connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the MarkLogic 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 · MarkLogic ⇄ 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
    MarkLogic Microsoft Power Bi
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

MarkLogic 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 370 integrations available for MarkLogic and Microsoft Power Bi.

Popular · 7 of 370
All MarkLogic 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