Skip to content
Analytics ⇄ CRM

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

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

Put live Salesforce data behind every dashboard and cohort in Microsoft Power Bi, and write the segments and scores Microsoft Power Bi computes back onto the Salesforce record — one connection, not a nightly export.

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

Microsoft Power Bi turns data into dashboards, cohorts, and metrics; Salesforce is where customers, contacts, deals, and activity actually live and change. The two meet wherever a number is really about a specific account, segment, or stage — yet most teams feed the CRM into analytics as a nightly extract or a hand-maintained connector, so the reporting lags the business and can't be sliced by the customers and segments that matter.

Stacksync syncs Campaigns, Tasks and Events, Products and Price Books, Custom Objects from Salesforce into Microsoft Power Bi field by field and within seconds, so every dashboard and cohort runs on current records instead of a stale copy. Because the connection runs both ways, the cohorts, scores, and metrics computed in Microsoft Power Bi write back to fields in Salesforce, landing where the people working accounts can see them. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Pull Dataflow and Datasource definitions to document lineage between Power BI and its upstream warehouses in a governance database.
  • 02 Load dataset Refresh History into an operational database to alert on-call teams when scheduled refreshes fail or run long.
  • 03 Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
  • 04 Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.

Common sync patterns

Where Salesforce accepts updates: segments and scores back on the record

Cohorts, scores, and computed metrics from Microsoft Power Bi sync onto fields in Salesforce, putting the analysis where reps and owners actually work the accounts.

One customer across analytics and CRM

The same account or person is keyed consistently in both systems, so a profile or row in Microsoft Power Bi lines up with the contact or account in Salesforce.

A record that outlives edits in the CRM

A continuously synced copy of Salesforce's records and activity in Microsoft Power Bi keeps a queryable history even as records change or age out of the CRM.

What you can sync between Microsoft Power Bi and Salesforce

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.

Microsoft Power Bi objects Salesforce objects How this pairing syncs
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. Cases Support records; synced with help desk tools or internal databases for escalation workflows. Users and Access is specific to Microsoft Power Bi and Cases to Salesforce — each maps to any object or custom field on the other side.
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. Campaigns Marketing membership data; read out for attribution analysis in the warehouse. Datasets (Semantic Models) is specific to Microsoft Power Bi and Campaigns to Salesforce — each maps to any object or custom field on the other side.
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. Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. Reports is specific to Microsoft Power Bi and Tasks and Events to Salesforce — each maps to any object or custom field on the other side.
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. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. Dashboards and Tiles is specific to Microsoft Power Bi and Products and Price Books to Salesforce — each maps to any object or custom field on the other side.
Dataflows Power Query ETL definitions read via GET /groups/{id}/dataflows; used to document lineage from upstream sources into datasets. Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. Dataflows is specific to Microsoft Power Bi and Custom Objects to Salesforce — each maps to any object or custom field on the other side.
Datasources and Gateways The connections behind datasets and dataflows and the on-premises gateways serving them, read via REST for lineage and dependency mapping. Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. Datasources and Gateways is specific to Microsoft Power Bi and Accounts to Salesforce — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Power Bi and Salesforce

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.

Microsoft Power Bi Salesforce 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 written to Salesforce through its API, with automatic retries and rate-limit backoff.

Salesforce Microsoft Power Bi Sub-second propagation

DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).

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

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.
  • Salesforce: Daily API request allocations vary by edition and license count.
What ships with Microsoft Power Bi ⇄ Salesforce

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Microsoft Power Bi or Salesforce 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 Microsoft Power Bi or Salesforce record.

Observability

Monitoring

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

Trading partners

EDI

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

How the Microsoft Power Bi and Salesforce connectors work

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.

Salesforce

Integration surface
REST, SOAP, and Bulk APIs
Authentication
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection
Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
Capabilities
read · write · CDC
Rate limits
Daily API request allocations vary by edition and license count.
Salesforce setup guide
How it works

How to connect Microsoft Power Bi to Salesforce — 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 Microsoft Power Bi and Salesforce 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
    Microsoft Power Bi connected
    Salesforce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

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

Popular · 8 of 469
All Microsoft Power Bi integrations All Salesforce 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