If you run Dynamics 365 Finance and Operations, getting data out for reporting has never been as simple as it should be. Over the years, Microsoft has offered at least four ways to do it: D365 BYOD, Export to Data Lake, Azure Synapse Link for Dataverse, and, now, Fabric Link (Link to Microsoft Fabric). Each came with its own setup, costs and quirks, and many D365 customers run more than one at the same time, often because a report built five years ago still depends on the old one. That patchwork is now forcing decisions. Export to Azure Data Lake stops for good on November 30, 2026. Synapse Link customers have just been through a forced Spark runtime upgrade and will face more. And with Microsoft putting its new data and AI features into Fabric, the question on most finance and IT leaders’ minds is simple: which of these should we be on, and what does moving actually involve?

This guide answers that in plain terms. We compare all four options side by side, explain how each one works and what it costs, cover the recent changes that affect you, and set out a step-by-step path off BYOD that doesn’t break month-end. If you only have a minute, the short answer is in the next section. If you’d rather hand the move to a team with ample experience working with Microsoft Fabric in Dynamics 365, Avantiico has three fixed-scope options:

  • Synapse Spark Runtime Upgrade ($9,500 fixed): gets you back on a supported runtime.
  • D365 BYOD Replacement (from $15,000; most projects $15,000–$30,000): rebuilds your feed on Fabric through Fabric Link, with a parallel run to prove the numbers match before cutover.
  • D365 F&O to Fabric Starter Pack (from $10,000): connects GL, AR, AP, vendors and customers to a clean Silver layer.

 

Skip Ahead

For most Dynamics 365 Finance and Operations customers moving to Microsoft Fabric, Fabric Link is the default choice. It puts F&O tables into a Fabric lakehouse with no pipelines, no storage account and no Spark pool to manage. Synapse Link still makes sense if you already run Synapse and need your own storage account. BYOD remains the option when downstream systems need a SQL database of data entities. Microsoft hasn’t announced its retirement, but it’s batch-based and doesn’t feed Fabric directly.

If you still use Export to Azure Data Lake, act now: Microsoft says it “will permanently stop on November 30, 2026” (Microsoft Learn).

BYODExport to Data Lake in Dynamics 365Azure Synapse LinkFabric Link
StatusSupportedRetired Nov 1, 2024; stops Nov 30, 2026SupportedSupported, Microsoft’s “Recommended” option in the maker portal
Where data landsYour Azure SQL databaseYour ADLS Gen2Your ADLS Gen2 + SynapseDataverse-managed storage, shortcut into a Fabric lakehouse
What’s exportedData entitiesTablesTables and entitiesTables and entities
FormatSQL tablesCSVDelta Parquet (required for F&O)Delta Parquet
FreshnessBatch jobs you scheduleContinuous (until it stops)5, 15, 60 or 1,440 min intervals (depends on Spark pool size)Incremental updates typically within an hour
You manageAzure SQL DB, batch jobsStorage accountStorage, Synapse workspace, Spark poolFabric workspace only
Main costAzure SQL (S6 / GP_Gen5_8 minimum for production)StorageStorage + Spark compute for Delta conversionDataverse database storage + Fabric capacity

Sources: BYOD, Synapse Link for F&O, Link to Fabric, Fabric Link FAQ, Microsoft Learn.

Related Article: Microsoft Fabric Pricing Guide (2027): F-SKU Costs Explained

How Each Dynamics 365 Data Export Option Works

D365 BYOD (Bring Your Own Database) in Dynamics 365

BYOD exports F&O data entities to an Azure SQL database you own, through the Data management workspace and batch jobs. Over 1,700 entities are available. Exports run either as a full push (delete everything and reload) or incrementally with change tracking (Microsoft Learn).

Why teams like it: plain T-SQL access, and downstream systems and reports were often built on it years ago. Why it’s painful: batch scheduling, full-push fallbacks when change tracking falls outside its retention period, timeouts on large entities, and an Azure SQL database (S6 or higher in production) to pay for and maintain. It also doesn’t land data in Fabric. To use BYOD data there, you’d mirror or copy it in again.

Related Article: Understanding Microsoft Fabric for Dynamics 365 Finance & SCM

Export to Data Lake in Dynamics 365 (Stops November 30, 2026)

This exported F&O tables as CSV into your own data lake. Microsoft retired it on November 1, 2024 and says it will permanently stop exporting on November 30, 2026, with no extensions. Files already exported stay where they are, but nothing new arrives (Microsoft Learn).

Related Article: What is Microsoft Fabric vs. Power BI: Key Differences in 2026 Every Business Leader Understand

Microsoft’s named replacement for Export to Data Lake. It exports F&O tables (and entities, enabled as virtual tables) to your ADLS Gen2 account. For F&O, Delta Lake format is mandatory, which means you provide a Spark pool that converts changes to Delta on an interval of 5, 15, 60 or 1,440 minutes. Shorter intervals and bigger volumes mean more Spark compute cost (Microsoft Learn).

Know the quirks before you build on it: memo fields are cut to 2,000 characters, deleted rows are kept with an isDelete flag, and derived tables need their base table selected too.

Related Article: Top 18 Microsoft Fabric Industry Solutions & Use Cases (Why Enterprises Need Microsoft Fabric)

Dynamics 365 Fabric Link keeps a Delta Parquet replica of your selected tables in Dataverse-managed storage and creates shortcuts to it in a Fabric lakehouse, along with a SQL endpoint. You don’t provide a storage account, a Synapse workspace or a Spark pool (Microsoft Learn).

What to know (Fabric Link FAQ):

  • F&O tables aren’t selected automatically. Add them through Manage tables.
  • Freshness: after the initial sync, incremental updates typically appear within an hour.
  • Storage cost: the replica counts toward your Dataverse database capacity, so link only the tables you need.
  • Cross-region is allowed: your Fabric capacity no longer has to be in the same region as Dataverse.
  • Permissions: you need System Administrator in the Power Platform environment and admin rights on the Fabric workspace.

Related Article: Fabric Data Agents: What They Are, How to Set One Up, and Where They Fall Short

Dynamics 365 Data Export Changes in 2026: What They Mean for You

DateChangeIf this affects you
Nov 30, 2026Export to Azure Data Lake permanently stops exportingMove to Fabric Link or Synapse Link before reports built on the lake go stale
Mar 31, 2026Synapse Spark 3.4 runtime reached end of support; phased disablement of 3.4 jobs to followSynapse Link profiles running on a Spark 3.4 pool can stop converting data. Upgrade to Spark 3.5, or move to Fabric
Nov 1, 2024Export to Azure Data Lake retired (no new features or support)Plan the move above

Sources: Export to Azure Data Lake, Synapse Spark 3.4 runtime, Microsoft Learn.

The Spark retirement is the one D365 teams notice too late. Synapse Link for F&O depends on a Spark pool to convert data to Delta. When that runtime is retired, the conversion can stop, and bank reconciliations or finance reports quietly go stale. Microsoft’s guidance is to move Spark 3.4 workloads to Spark 3.5 or Fabric Runtime 2.0 “as soon as possible”, and it “strongly” recommends Fabric.

Every forced runtime upgrade on Synapse Link is a reminder that Fabric Link has no Spark pool for you to maintain.

 

Related Article: What is Microsoft Fabric vs Databricks vs Snowflake: When to Switch and When to Connect

When it comes to choosing between Microsoft Fabric Link vs Synapse Link vs. BYOD in Dynamics 365, here’s how to make your choice:

If you…Choose
Are starting a Fabric data platform on D365 F&OFabric Link
Still use Export to Azure Data LakeFabric Link (or Synapse Link if you must keep your own storage), before Nov 30, 2026
Run Synapse Link today and maintain its Spark poolPlan a move to Fabric Link at your next forced runtime upgrade
Feed third-party systems that expect a SQL database of entitiesKeep BYOD for those, and use Fabric Link for analytics. Or rebuild the entity views in Fabric and retire BYOD
Need data within minutes, not the hourTest Fabric Link’s low-latency sync on your build first, or use Synapse Link with a 5- or 15-minute interval and a bigger Spark pool

The hard part of leaving BYOD isn’t moving the data. It’s that reports, reconciliations and downstream systems expect BYOD’s exact entity shapes. A safe migration keeps them working. Here’s how to replace Dynamics 365 BYOD with Microsoft Fabric Link in 6 simple steps:

  1. Inventory what reads BYOD. List every report, integration and query that touches the BYOD database, and which entities each uses.
  2. Turn on Fabric Link and add the F&O tables behind those entities.
  3. Rebuild the entity shapes in Fabric. Create views or Silver tables in the lakehouse or warehouse that return the same columns the consumers expect.
  4. Run in parallel and reconcile row counts and totals between BYOD and Fabric for at least one full month-end close.
  5. Repoint consumers one by one, starting with reports, then integrations.
  6. Retire BYOD once nothing reads it, and stop paying for the Azure SQL database.

Is Azure Synapse being retired?

This comes up in almost every conversation about Synapse Link, and it’s worth being precise. Microsoft hasn’t announced an end-of-life date for Azure Synapse Analytics as a whole. What it does retire, on a schedule, are the Spark runtimes Synapse Link depends on: Spark 3.4 reached end of support on March 31, 2026. For Spark workloads, Microsoft’s own guidance is to move to Spark 3.5 or, preferably, Fabric Runtime 2.0 (Microsoft Learn).

In practice, that means Synapse Link still works, but every runtime retirement is a project on your calendar. Fabric Link has no Spark pool for you to upgrade, which is one of the strongest practical reasons to move.

Moving the pipe is the easy part; the reports on top are where projects slip. Plan for these differences:

  • Tables, not entities. BYOD exports data entities, which are business-friendly views that combine several tables. Fabric Link syncs the underlying tables. Reports built on BYOD entities need those entity shapes rebuilt as views or Silver tables in Fabric.
  • Deleted rows. Synapse Link keeps deleted rows and flags them with isDelete. Make sure your Silver layer filters them out, or totals won’t match D365.
  • Long text fields. Synapse Link truncates memo fields at 2,000 characters. Check any report that relies on long descriptions or notes.
  • Freshness. Fabric Link updates typically arrive within an hour. If anyone is used to near-real-time numbers, set expectations or test the low-latency sync on your F&O build first.
  • Security. Row-level security that lived in BYOD views or reports has to be recreated in the Fabric semantic model.

For almost every D365 F&O customer starting or modernizing reporting today, Fabric Link is the default. There’s no storage account, no Spark pool and no batch jobs to maintain, and the data lands where Microsoft’s new analytics and AI features are being built. Keep BYOD only where a downstream system truly needs a SQL database of entities, and plan its retirement. If you’re still on Export to Data Lake, the deadline makes the decision for you.

Start now, run old and new in parallel through one month-end close, and switch over only when the numbers match.

Get off BYOD and Export to Data Lake without breaking month-end

Avantiico’s D365 BYOD Replacement (from $15,000; most projects $15,000–$30,000) rebuilds the feed on Fabric through Fabric Link. We deliver the same tables and views your downstream systems and reports expect, and prove the numbers match in a parallel run before cutover. Starting fresh? The D365 F&O to Fabric Starter Pack (from $10,000) connects GL, AR, AP, vendors and customers to a clean Silver layer. Stuck on Synapse? Our Synapse Spark Runtime Upgrade ($9,500 fixed) gets you back on a supported runtime.

Sources

Is BYOD being deprecated in Dynamics 365 Finance and Operations? 

Microsoft’s BYOD documentation contains no deprecation notice as of October 2026. What has been retired is Export to Azure Data Lake. Even so, new analytics investment is going into Synapse Link and Fabric Link, not BYOD.

It’s the “Link to Microsoft Fabric” option in the Power Apps maker portal. It replicates selected Dataverse and F&O tables in Delta Parquet and exposes them in a Fabric lakehouse through shortcuts, with no ETL.

Synapse Link writes to a storage account you own and needs a Synapse workspace and Spark pool for F&O data. Fabric Link uses Dataverse-managed storage and puts the data straight into Fabric, so there’s no storage or Spark to manage.

There’s no separate fee, but the replica counts toward your Dataverse database storage capacity, and you need a Fabric capacity (or trial) to use the data.

Microsoft says incremental updates typically appear within an hour after the initial sync. A low-latency sync engine is rolling out on newer F&O builds.

What’s the difference between the entity store and BYOD? 

The entity store is D365’s built-in analytics store, which Microsoft positions as the default for operational Power BI reporting. BYOD exports entities to your own Azure SQL database and is a “complementary option” for your own data warehouse, non-Power BI tools or integrations (Microsoft Learn).