Groups that grow by acquisition often run D365 Finance and Operations next to SAP or Oracle, and replacing an ERP takes years. The analytics question is where the numbers from each system become comparable. Microsoft now documents routes for SAP data in Microsoft Fabric, and for D365 F&O and Oracle Database data, so all three can sit in OneLake; Oracle Fusion Cloud ERP is the exception, covered below. The work that remains is conforming them into one model: chart of accounts, dimensions, currency, fiscal calendar, and master data. This guide covers how each ERP gets into Fabric today, what the routes cost, and how to build one ERP analytics layer on top. Statuses are as of October 19, 2026.
What one ERP analytics layer means
- One copy of each ERP’s data in OneLake, which Microsoft describes as one copy of data to use with multiple analytical engines, without duplication.
- One conformed model: a group chart of accounts, shared dimensions, one currency approach, and one fiscal calendar.
- One Power BI semantic model that finance uses for every company in the group.
It does not mean moving to one ERP, and it does not replace your consolidation process. It is the layer where group reporting and analysis run.
How SAP, Oracle, and D365 data get into Fabric today
| Source | Route into OneLake | What to know |
|---|---|---|
| D365 Finance and Operations | Link to Microsoft Fabric | Not a connector: Dataverse manages a Delta copy and exposes it as shortcuts; one environment links to one workspace |
| Dynamics 365 Business Central | Dataflow Gen2 connector | Not on Dataverse, so no Link to Fabric; Microsoft has announced Business Central mirroring as coming soon |
| Dynamics AX 2012 or NAV on SQL Server | Fabric mirroring for SQL Server, or pipelines | Mirroring covers SQL Server 2016 to 2025 through a gateway, up to 1,000 tables per mirrored database, so select the finance tables; 2016 to 2022 also needs change data capture and a primary key on each table |
| SAP S/4HANA, ECC, and BW | Mirroring through SAP Datasphere; a copy job with Microsoft’s ABAP add-on; SAP-certified partners through open mirroring; built-in SAP HANA, SAP Table, and SAP BW connectors | Datasphere mirroring is generally available; SAP Business Data Cloud Connect for Fabric is announced, with general availability not yet confirmed |
| Oracle Database, including E-Business Suite and JD Edwards on Oracle | Mirroring for Oracle, copy job change data capture, or the Oracle database connector | Mirroring is generally available |
| Oracle Fusion Cloud ERP | No route built for it in Microsoft’s documentation | Microsoft lists a new Oracle ERP connector for Power Query in preview, but its page does not name the product it targets, so test it first |
| NetSuite | A partner tool through open mirroring (Microsoft names CData Sync) | Microsoft lists no first-party NetSuite connector |
| Azure Databricks | Metadata mirroring of Unity Catalog, and shortcuts | Fabric reads the data in place, without moving it |
SAP: the licensing note that decides your route
An update to SAP Note 3255746 announced a security patch that blocks third-party calls to SAP’s ODP RFC interface, which tools such as the Azure Data Factory SAP CDC connector use. Microsoft lists Fabric alternatives that are not affected, including mirroring through SAP Datasphere, SAP Business Data Cloud Connect, the copy job with Microsoft’s ABAP add-on, and SAP-certified partners through open mirroring. The built-in SAP HANA, SAP Table, and SAP BW connectors are not on that list, so check them against your SAP license first.
- Mirroring through SAP Datasphere. A Datasphere replication flow lands initial and changed data as Parquet files in Azure storage, and Fabric mirroring merges them into OneLake. It supports S/4HANA, ECC, BW/4HANA, BW, and Datasphere, and SAP’s Datasphere Premium Outbound Integration pricing applies.
- Copy job with Microsoft’s ABAP add-on. The add-on is installed on the SAP system and reads tables, views, and CDS views. It supports S/4HANA, ECC 6.0 EhP8 on NetWeaver 7.50, BW/4HANA, and BW 7.50, not earlier ECC releases, and it needs an on-premises data gateway and the SAP .NET Connector.
- Partner tools. Microsoft lists SAP-certified partners that write into Fabric through open mirroring, including AecorSoft, ASAPIO, dab Nexus, SNP Glue, and Theobald Xtract Universal.
- SAP Business Data Cloud Connect. SAP and Microsoft announced zero-copy sharing of SAP data products with Fabric in November 2025; general availability is not yet confirmed. Microsoft asks customers to review SAP’s terms on downstream use of the data.
Agree on the route with your SAP licensing contact before you build, because it decides both cost and what you may do with the data.
Oracle: database mirroring, and why Fusion Cloud is different
Mirroring for Oracle reads Oracle Database 10 and later through LogMiner, with archive log mode and supplemental logging turned on, through an on-premises data gateway. Its limits matter for ERP schemas: up to 1,000 tables per mirrored database, every table needs a primary key or unique index, table names of 30 or more characters are not supported, and column type changes are not supported. That makes it the first route to test for Oracle E-Business Suite or JD Edwards on Oracle Database: check table counts and name lengths against these limits, and note that it must read a database in write mode, not a read-only standby. Oracle Fusion Cloud ERP is a SaaS application without direct database access, so database mirroring does not apply to it.
What landing the data costs
- Mirroring: the replication compute is free, and each purchased capacity unit includes 1 TB of mirroring storage, so an F64 includes 64 TB. Queries on mirrored data use capacity, storage is billed while the capacity is paused, and optional extended capabilities such as change data feed are billed separately.
- Copy jobs: billed by data movement, with incremental copies at twice the rate of full copies.
- Link to Fabric: the D365 copy counts toward your Dataverse database capacity.
- Vendor charges: SAP Datasphere mirroring adds SAP’s Premium Outbound Integration charges, so the free replication covers only the Fabric side.
The real work is conforming the data
A group chart of accounts
D365 Finance already models this for consolidation: each main account can carry a default consolidation account, which Microsoft suggests when charts of accounts differ or must map to a headquarters chart, and consolidation account groups add further mapping sets. Use the same pattern across ERPs: a mapping table that assigns every D365 main account, SAP general ledger account, and Oracle natural account segment (object account in JD Edwards) to one group account.
Legal entities and dimensions
Map each system’s company to the group’s legal entity list, for example the SAP company code, the Oracle balancing segment, or the JD Edwards company. Then map SAP cost and profit centers and Oracle segments to the financial dimensions finance reports by. On the D365 side, decode financial dimensions first, as described in what Link to Fabric leaves you to build.
Intercompany
D365 consolidation typically uses a financial dimension such as Trading Partner for eliminations. Carry the same counterparty attribute on every ERP’s data so intercompany balances can be matched across systems; see intercompany transactions and consolidation risk.
Currency
D365 stores transaction, accounting, and reporting currency amounts on general ledger lines, the last when a reporting currency is set on the ledger. Carry each source’s local and group currency amounts into the conformed layer, and translate once there, rather than in each report.
Fiscal calendars
D365 closing periods share their dates with the last period of the year, and SAP special periods and Oracle adjusting periods also post on dates inside a regular period, so a date alone cannot place a row. Give every row a period type alongside its date. D365’s consolidation import format already uses one: opening, operating, or closing. For 4-4-5 style calendars, Power BI’s calendar-based time intelligence is in preview.
Master data
Customers, vendors, and items carry different codes in each ERP. Build cross-reference tables in the conformed layer so a customer that trades with two group companies appears once; see master data governance for ERP reporting.
A Fabric layout that works
- A workspace per source. The D365 Link to Fabric lakehouse and each mirrored SAP or Oracle database stay in their own workspaces as the raw layer. Because a Dataverse environment links to one workspace, read the D365 tables from the group workspace through shortcuts.
- A conformed layer. Mapping tables, cross-references, and cleaned Delta tables, which Microsoft’s guidance calls the silver layer.
- A star schema on top. Facts and conformed dimensions, such as date, legal entity, account, and product, shared across fact tables, with Direct Lake reading them; see Direct Lake vs import.
- Domains for governance. Fabric domains group workspaces by business area, but assigning a domain does not grant anyone access.
Security does not travel with the data
Roles in D365, SAP, and Oracle do not carry into Fabric. Access is controlled by Fabric workspace roles, OneLake security, and row-level security in the semantic model, so build row-level security by group legal entity once, in the model finance uses, and keep finance users out of the raw source workspaces.
When D365 stays the consolidation system
Some groups keep the statutory consolidation in D365 Finance and use Fabric for analysis. D365 can consolidate from a text file in Microsoft’s import format, with main account, period type, currency, posting layer, and financial dimensions, so mapped balances from SAP or Oracle can be loaded into a D365 consolidation company. The conformed layer in Fabric can produce that file from the same mappings the reports use; see financial consolidation analytics for the D365 side.
Where Metrixs fits
Metrixs runs in your own Microsoft Fabric environment. It reads D365 F&O through Link to Fabric or Azure Synapse Link, connects natively to Business Central and Databricks, reports on Dynamics NAV data, brings in Dynamics AX through custom pipelines, and takes SAP and Oracle data through Microsoft Fabric connectors into the same model; other connectors are built to a customer’s needs. It adds its data model and 150+ pre-built Power BI reports, with 1,200+ metrics and 250+ KPIs, and supports financial consolidation, including Business Central groups with several companies. See ERP integration services, Microsoft Fabric for D365 F&O, or request a demo and see if you qualify for a free 6-month trial.
FAQs
1. Do we need SAP Datasphere to bring SAP data into Fabric?
No, but it is one of the main routes. Microsoft’s options include mirroring through SAP Datasphere, a copy job using Microsoft’s ABAP add-on installed on the SAP system, SAP-certified partner tools that write through open mirroring, and the built-in SAP HANA, SAP Table, and SAP BW connectors, which are not on Microsoft’s list of routes unaffected by SAP Note 3255746. Check SAP’s licensing notes before you choose.
2. Is Fabric mirroring free?
The replication compute is free, and each purchased capacity unit includes 1 TB of mirroring storage. Queries on the mirrored data use capacity, optional extended capabilities are billed, storage is billed while the capacity is paused, and SAP Datasphere mirroring also carries SAP’s own Premium Outbound Integration charges.
3. Can Fabric mirror Oracle Fusion Cloud ERP?
Not with database mirroring, which needs access to an Oracle database. Fusion Cloud ERP is a SaaS application, and Microsoft documents no route built for it. Microsoft lists a new Oracle ERP connector for Power Query in preview, but its page does not name the product it targets, so test it before you plan around it.
4. Does Link to Fabric work for SAP or Oracle?
No. Link to Microsoft Fabric is for Dataverse, which is how D365 Finance and Operations data reaches OneLake. SAP and Oracle come in through mirroring, copy jobs, or built-in connectors.
5. Can D365 Finance consolidate balances from SAP or Oracle?
D365 Finance can consolidate from a text file in Microsoft’s import format, with main account, period type, currency, and financial dimensions, so balances from another ERP can be brought into a D365 consolidation company after mapping. Detailed analysis across ERPs still needs the conformed model in Fabric.
Sources
All pages below were checked on October 19, 2026.
- SAP change data capture: architecture and alternatives in Fabric
- Mirroring SAP in Microsoft Fabric
- Copy job for SAP with the Microsoft ABAP add-on
- Fabric Data Factory connector overview
- Open mirroring partner ecosystem
- SAP and Microsoft: SAP Business Data Cloud Connect for Microsoft Fabric, November 2025
- Mirroring for Oracle in Microsoft Fabric
- Mirroring for Oracle: limitations
- Copy job change data capture from Oracle
- Oracle ERP connector for Power Query (preview)
- Mirroring SQL Server in Microsoft Fabric
- Mirroring in Microsoft Fabric: overview
- Mirroring extended capabilities billing
- Copy job pricing
- OneLake overview
- Dimensional modeling: dimension tables
- Medallion lakehouse architecture in Microsoft Fabric
- Fabric domains
- Time intelligence in Power BI Desktop
- Financial consolidations and currency translation in D365 Finance
- Consolidate with import: file format
- Dual currency
- Link your Dataverse environment to Microsoft Fabric
- FabCon Barcelona 2026: what’s new in Fabric Data Factory

Operations head with 20 years of experience delivering business intelligence, ERP, and AI programs across healthcare, finance, and manufacturing. Focus areas include Power Platform adoption and governance, delivery models, and managed services.