Skip to content
CRM ⇄ Analytics

Microsoft Dynamics 365 Sales to Microsoft Power Bi integration — real-time data sync

Keep Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales and Microsoft Power Bi

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

Microsoft Power Bi turns data into dashboards, cohorts, and metrics; Microsoft Dynamics 365 Sales 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 Opportunities, Quotes, Orders, Invoices from Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales, 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 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 Write product usage and warehouse-computed scores onto Dataverse tables so sellers see them in the model-driven app.
  • 04 Run a two-way dual-run between Dynamics and another CRM during a migration.

Common sync patterns

A record that outlives edits in the CRM

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

Customer context in Microsoft Power Bi

Accounts, contacts, deals, and activity from Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales appear in Microsoft Power Bi within seconds, so dashboards and cohorts track the current pipeline rather than last night's export.

What you can sync between Microsoft Dynamics 365 Sales 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.

Microsoft Dynamics 365 Sales objects Microsoft Power Bi objects How this pairing syncs
Opportunities Deal records with stages and estimated revenue; synced for pipeline reporting and close-triggered workflows. 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. Opportunities is specific to Microsoft Dynamics 365 Sales and Reports to Microsoft Power Bi — each maps to any object or custom field on the other side.
Quotes Pricing proposals; often synced with CPQ or ERP pricing data. 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. Quotes is specific to Microsoft Dynamics 365 Sales and Dashboards and Tiles to Microsoft Power Bi — each maps to any object or custom field on the other side.
Orders Confirmed sales; handed off to ERP systems for fulfillment and billing. Dataflows Power Query ETL definitions read via GET /groups/{id}/dataflows; used to document lineage from upstream sources into datasets. Orders is specific to Microsoft Dynamics 365 Sales and Dataflows to Microsoft Power Bi — each maps to any object or custom field on the other side.
Invoices Billing records; usually mastered in the ERP and mirrored back for seller visibility. Datasources and Gateways The connections behind datasets and dataflows and the on-premises gateways serving them, read via REST for lineage and dependency mapping. Invoices is specific to Microsoft Dynamics 365 Sales and Datasources and Gateways to Microsoft Power Bi — each maps to any object or custom field on the other side.
Activities Emails, calls, appointments, and tasks; read out for activity analytics. Refresh History Dataset refresh runs read via GET /datasets/{id}/refreshes, including status, type, and timing, to alert on failed or slow scheduled refreshes. Activities is specific to Microsoft Dynamics 365 Sales and Refresh History to Microsoft Power Bi — each maps to any object or custom field on the other side.
Custom Tables Tenant-defined Dataverse tables; exposed through the same Web API as standard tables. Workspaces (Groups) Containers for content read via GET /groups (tenant-wide via GET /admin/groups); mirrored to reproduce the tenant's content hierarchy in a catalog. Custom Tables is specific to Microsoft Dynamics 365 Sales and Workspaces (Groups) to Microsoft Power Bi — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Dynamics 365 Sales 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.

Microsoft Dynamics 365 Sales Microsoft Power Bi Sub-second propagation

DetectionMicrosoft Dynamics 365 Sales notifies Stacksync of record changes through webhook events. Dataverse change tracking with delta tokens, plus registered webhooks on table events.

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 Microsoft Dynamics 365 Sales records.

Microsoft Power Bi Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Microsoft Dynamics 365 Sales: Requests are governed by Dataverse service protection limits evaluated per user and time window.
  • 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 Microsoft Dynamics 365 Sales ⇄ Microsoft Power Bi

Connect Microsoft Dynamics 365 Sales and Microsoft Power Bi for flexible, real-time data sync.

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

Real-time

Real-time sync

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

Observability

Monitoring

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

How the Microsoft Dynamics 365 Sales and Microsoft Power Bi connectors work

Microsoft Dynamics 365 Sales

Integration surface
Dataverse Web API (OData v4 REST)
Authentication
OAuth 2.0 via Microsoft Entra ID
Change detection
Dataverse change tracking with delta tokens, plus registered webhooks on table events
Capabilities
read · write · webhooks
Rate limits
Requests are governed by Dataverse service protection limits evaluated per user and time window.

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

    Choose tables

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

Microsoft Dynamics 365 Sales 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 363 integrations available for Microsoft Dynamics 365 Sales and Microsoft Power Bi.

Popular · 7 of 363
All Microsoft Dynamics 365 Sales 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