Real-time
Real-time sync
Changes in Dynamics 365 Business Central or Microsoft Power Bi instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Analytics
Dynamics 365 Business Central to Microsoft Power Bi integration — real-time data sync
Keep Dynamics 365 Business Central 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
Live sync
stacksync.com - <1s
- latency
- real-time
- sync
- 100M+
- records
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 Dynamics 365 Business Central and Microsoft Power Bi
Put Dynamics 365 Business Central's records into Microsoft Power Bi as live data for reporting and dashboards, without nightly exports, and send the segments and metrics Microsoft Power Bi computes back where Dynamics 365 Business Central can use them.
Microsoft Power Bi is a read-only source: Stacksync reads its data in real time and delivers it into Dynamics 365 Business Central, so Dynamics 365 Business Central always reflects the current state of Microsoft Power Bi — without exports, scripts, or schedulers.
ERP data is some of the most requested data for analysis and some of the hardest to pull: the record types are many, the APIs are strict, and export jobs break on every upgrade. Whether Dynamics 365 Business Central carries financials, operations, workforce data, or all three, those numbers belong in Microsoft Power Bi, next to the product, behavioral, and web data the team already measures.
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 Sync vendor and purchase order data with procurement or AP automation tools.
- 04 Create sales orders in Business Central automatically from e-commerce or CRM order records, and sync fulfillment status back.
Common sync patterns
Where Dynamics 365 Business Central holds the books: revenue and finance dashboards from live data
Financial records from Dynamics 365 Business Central land in Microsoft Power Bi as they change, so revenue, margin, and spend dashboards read current figures rather than last night's export.
Where Dynamics 365 Business Central runs order-to-cash: customer and account analytics
Orders, invoices, and account records from Dynamics 365 Business Central join the behavioral and usage data Microsoft Power Bi already tracks, so customer analysis spans activity and dollars in one view.
Where Dynamics 365 Business Central runs operations: inventory and fulfillment metrics
Operational records from Dynamics 365 Business Central become measurable in Microsoft Power Bi, joinable with the rest of what the company tracks for supply and fulfillment reporting.
What you can sync between Dynamics 365 Business Central 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.
| Dynamics 365 Business Central objects | Microsoft Power Bi objects | How this pairing syncs | |
|---|---|---|---|
| Purchase Orders Procurement documents exchanged with supplier-facing systems. | Refresh History Dataset refresh runs read via GET /datasets/{id}/refreshes, including status, type, and timing, to alert on failed or slow scheduled refreshes. | Purchase Orders is specific to Dynamics 365 Business Central and Refresh History to Microsoft Power Bi — each maps to any object or custom field on the other side. | |
| General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. | 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. | General Ledger Entries is specific to Dynamics 365 Business Central and Workspaces (Groups) to Microsoft Power Bi — each maps to any object or custom field on the other side. | |
| Journals Staging records for financial postings created by integrations before posting. | Activity Events (Audit Log) Admin audit log of user and content actions read via GET /admin/activityevents; loaded for security, access, and usage reporting across the tenant. | Journals is specific to Dynamics 365 Business Central and Activity Events (Audit Log) to Microsoft Power Bi — each maps to any object or custom field on the other side. | |
| Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. | 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. | Dimensions is specific to Dynamics 365 Business Central and Users and Access to Microsoft Power Bi — each maps to any object or custom field on the other side. | |
| Payments Customer and vendor payment records reconciled against invoices. | 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. | Payments is specific to Dynamics 365 Business Central and Datasets (Semantic Models) to Microsoft Power Bi — each maps to any object or custom field on the other side. | |
| Customers Core master data synced with CRMs so sales and finance share one customer list. | 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. | Customers is specific to Dynamics 365 Business Central and Reports to Microsoft Power Bi — each maps to any object or custom field on the other side. |
How changes propagate between Dynamics 365 Business Central 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.
Dynamics 365 Business Central Microsoft Power Bi Sub-second propagation
DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.
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 Dynamics 365 Business Central records.
Microsoft Power Bi Dynamics 365 Business Central 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 Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.
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 Dynamics 365 Business Central ⇄ Microsoft Power Bi
Connect Dynamics 365 Business Central and Microsoft Power Bi for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 Business Central–Microsoft Power Bi connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Dynamics 365 Business Central 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 Dynamics 365 Business Central or Microsoft Power Bi record.
Observability
Monitoring
Track your Dynamics 365 Business Central ⇄ 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 Dynamics 365 Business Central and Microsoft Power Bi.
How the Dynamics 365 Business Central and Microsoft Power Bi connectors work
Dynamics 365 Business Central
- Integration surface
- REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL
- Authentication
- OAuth 2.0 via Microsoft Entra ID
- Change detection
- API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime
- Capabilities
- read · write · webhooks
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 Dynamics 365 Business Central 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.
- 01
Connect your apps
Authenticate Dynamics 365 Business Central 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.
Dynamics 365 Business Central
connected
Microsoft Power Bi
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Dynamics 365 Business Central 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.
objects · Dynamics 365 Business Central ⇄ Microsoft Power BiCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Dynamics 365 Business Central Microsoft Power BiCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Dynamics 365 Business Central and Microsoft Power Bi integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between Dynamics 365 Business Central and Microsoft Power Bi — Microsoft Power Bi is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
-
Microsoft Power Bi: Power BI exposes no webhooks or change-data-capture feed for content or dataset rows, so incremental syncs re-poll REST endpoints and use Refresh History and Activity Events to detect changes. Dynamics 365 Business Central: The standard API exposes entities as OData v4 endpoints and supports $filter on lastModifiedDateTime, giving integrations a built-in incremental cursor. Stacksync's field mapping accounts for these differences between Dynamics 365 Business Central and Microsoft Power Bi without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Dynamics 365 Business Central and Microsoft Power Bi records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Dynamics 365 Business Central and Microsoft Power Bi connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Dynamics 365 Business Central–Microsoft Power Bi integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Dynamics 365 Business Central and Microsoft Power Bi. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Dynamics 365 Business Central: API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime. On Microsoft Power Bi: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 441 integrations available for Dynamics 365 Business Central and Microsoft Power Bi.
Popular · 8 of 441
-
Dynamics 365 Business Central ⇄ Adobeanalytics -
Dynamics 365 Business Central ⇄ Pendo -
Dynamics 365 Business Central ⇄ Splunk -
Dynamics 365 Business Central ⇄ Treasuredata -
Microsoft Power Bi ⇄ Linnworks -
Microsoft Power Bi ⇄ Logiwa WMS -
Microsoft Power Bi ⇄ Macola ERP -
Microsoft Power Bi ⇄ Manhattan Associates WMS
No integrations match .
