Skip to content
Analytics ⇄ CRM

Microsoft Power Bi to Veeva CRM integration — real-time data sync

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

Put live Veeva CRM data behind every dashboard and cohort in Microsoft Power Bi, and write the segments and scores Microsoft Power Bi computes back onto the Veeva CRM 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 Veeva CRM, so Veeva CRM always reflects the current state of Microsoft Power Bi — without exports, scripts, or schedulers.

Microsoft Power Bi turns data into dashboards, cohorts, and metrics; Veeva CRM 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 Key Messages and CLM Content, Territories and Alignments, Events, Approved Email Activity from Veeva CRM 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 Veeva CRM, 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 Mirror Workspaces, Reports, Dashboards, and Dataset metadata into a catalog database so teams discover Power BI content from a central index.
  • 02 Pull Dataflow and Datasource definitions to document lineage between Power BI and its upstream warehouses in a governance database.
  • 03 Sync HCP and HCO accounts between Veeva CRM and a customer master or MDM system to keep the customer master aligned.
  • 04 Replicate call and activity data into a warehouse for field-force effectiveness reporting.

Common sync patterns

Customer context in Microsoft Power Bi

Accounts, contacts, deals, and activity from Veeva CRM sync into Microsoft Power Bi, so metrics and dashboards group by real customers, segments, and stage instead of anonymous IDs.

Report on live CRM data

New records and status changes in Veeva CRM appear in Microsoft Power Bi within seconds, so dashboards and cohorts track the current pipeline rather than last night's export.

Where Veeva CRM accepts updates: segments and scores back on the record

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

What you can sync between Microsoft Power Bi and Veeva CRM

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 Veeva CRM 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. Approved Email Activity Sent-email records from Veeva Approved Email, used in engagement reporting. Users and Access is specific to Microsoft Power Bi and Approved Email Activity to Veeva CRM — 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. Accounts (HCPs and HCOs) Healthcare professionals and organizations; the central entity most syncs key on. Datasets (Semantic Models) is specific to Microsoft Power Bi and Accounts (HCPs and HCOs) to Veeva CRM — 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. Calls Recorded visits and interactions with HCPs, including samples dropped and key messages shown. Reports is specific to Microsoft Power Bi and Calls to Veeva CRM — 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. Medical Inquiries Information requests captured in the field and routed to medical affairs. Dashboards and Tiles is specific to Microsoft Power Bi and Medical Inquiries to Veeva CRM — 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. Sample Transactions Sample disbursement records tracked for regulatory compliance. Dataflows is specific to Microsoft Power Bi and Sample Transactions to Veeva CRM — 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. Consent Records Channel-level communication consent for HCPs, synced to enforce opt-outs across systems. Datasources and Gateways is specific to Microsoft Power Bi and Consent Records to Veeva CRM — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Power Bi and Veeva CRM

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 Veeva CRM 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 Veeva CRM through its API, with automatic retries and rate-limit backoff.

Veeva CRM Microsoft Power Bi Interval-based propagation

DetectionStacksync polls Veeva CRM for changes on an incremental schedule, reading only records changed since the previous pass. Polling on record modification timestamps.

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 Veeva CRM 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.
  • Veeva CRM: Subject to the underlying platform's API request allocations, which are contract-dependent.
What ships with Microsoft Power Bi ⇄ Veeva CRM

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

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

Real-time

Real-time sync

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

Observability

Monitoring

Track your Microsoft Power Bi ⇄ Veeva CRM 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 Veeva CRM.

How the Microsoft Power Bi and Veeva CRM 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.

Veeva CRM

Integration surface
Salesforce-platform APIs (REST, SOAP, Bulk) for classic Veeva CRM; Vault REST API for Vault CRM
Authentication
OAuth 2.0
Change detection
Polling on record modification timestamps; platform event streams where the underlying org enables them
Capabilities
read · write
Rate limits
Subject to the underlying platform's API request allocations, which are contract-dependent.
How it works

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

    Choose tables

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

Microsoft Power Bi and Veeva CRM 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 437 integrations available for Microsoft Power Bi and Veeva CRM.

Popular · 8 of 437
All Microsoft Power Bi integrations All Veeva CRM 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