D365 F&O Fabric integration
Governed ERP data in Fabric, deployed in days
Zap lands governed, duplicate-proof Dynamics 365 Finance & Operations data into SQL Database in Fabric, with enforced primary keys, lookup-aware incremental loads and a semantic model that stays in sync. Power BI reports this week, Fabric notebooks and AI when you're ready, all from one trusted Dynamics 365 Finance & Operations foundation.
Primary keys are defined as metadata only and not physically enforced.Microsoft Fabric Community
Fabric's missing pieces
No key enforcement
Fabric doesn't enforce primary keys. Duplicates from retries and bad joins silently inflate your totals.
Stale incremental loads
When a looked-up value changes, standard loads miss every dependent row. Your numbers go wrong silently.
Model out of sync
Warehouse schema changes require manual semantic model updates. Default Semantic Models was supposed to help, but Microsoft sunset it in 2025.
Free 14-day trial with guided setup. We can loop in your Dynamics 365 Finance & Operations partner when you're ready.
Request Free TrialFabric foundations done right
Your data, proven correct
- Enforced primary keys Every table, every load. Duplicates rejected, not absorbed.
- Lookup-aware incremental When a looked-up value changes, Zap reprocesses dependent rows. Standard loads leave data stale, and stale means wrong.
- Pre-built ERP models GL, AR, AP and inventory, validated across hundreds of deployments. Or build custom.
One model, two layers, zero drift
- Orchestrated deployment Warehouse and semantic model update in sequence. No manual pipeline orchestration.
- No XMLA scripting Fabric says 'write C# against REST APIs.' Zap says one click.
- Schema changes propagate Add a column, rename a field, change a type. Both layers reflect it.
Live in days, not months
- Go live, then grow Power BI reports this week. Fabric for data science when you're ready.
- Built for AI, not just BI The governed star schema you build today is what AI needs to reason against, not hallucinate from.
- No migration to scale Your star schema already mirrors to OneLake, so notebooks and Copilot work from day one.
What is SQL Database in Fabric?
SQL Database in Fabric is the ACID-compliant, fully governed relational layer inside Fabric. It's a full SQL Server engine that enforces primary keys and runs Zap's ELT transforms in place. Data automatically mirrors to OneLake, giving notebooks, data science and AI access at lake scale. Zap lands governed ERP data here. Microsoft built it to close the governance gap Lakehouse couldn't. Zap runs inside it.
What we deliver
Duplicate-proof architecture
Enforced primary keys on every warehouse table. Duplicates are caught at load time, not discovered during an audit.
Dependency-aware refresh
Zap checks timestamps on all looked-up columns to determine the true minimal incremental set. 5x faster and actually correct.
Synchronized semantic layer
Warehouse and semantic model publish together. One change, one action, no drift between layers.
Pre-built ERP intelligence
Star schemas for your ERP built by people who've done it hundreds of times. Validated currency conversion, multi-company, chart of accounts.
Excel + Power BI, same data
Finance teams use Zap Live in Excel. Analysts use Power BI. Both query the same governed model. Single source of truth.
Explore the Zap platform
Fabric Integration for Dynamics 365 Finance & Operations, answered.
How does Zap prevent duplicate records?
Zap lands data in SQL Database in Fabric with enforced primary keys, so duplicates from retries or bad joins are rejected at load time, not discovered later. Fabric itself marks all keys 'NOT ENFORCED'.
What's wrong with standard incremental loads?
When a looked-up value changes, standard incremental loads miss every dependent row and your numbers go silently wrong. Zap's lookup-aware refresh reprocesses the dependent rows, so the data stays correct.
How does Zap make Power BI refreshes 5x faster?
Zap uses ledger-style delta processing: each change becomes an add-only transaction synced via XMLA, instead of reloading whole partitions. That's more than 5x faster and stays correct.
Why can't Fabric keep the semantic model in sync with the warehouse?
Fabric needs manual semantic-model updates when the warehouse schema changes. Default Semantic Models was meant to help, but Microsoft sunset it in 2025. Zap publishes warehouse and semantic model together, so there's no drift.
How does Zap relate to Fabric, is it a replacement?
No. Zap runs inside Fabric. It lands governed ERP data into SQL Database in Fabric and runs its ELT transforms in place, then mirrors to OneLake for notebooks, data science and AI.
How quickly can we go live?
Days, not months. Start with pre-built ERP models for Power BI this week, and switch on Fabric notebooks and data science when you're ready.
How does Zap Live work with Power BI?
Finance teams use Zap Live in Excel and analysts use Power BI, both querying the same governed model. One source of truth across both tools.
Talk data to us.
Getting started is easy. We're with you every step of the way, with in-app training, dedicated support and a global team committed to your data transformation.