SigmaBI

Synapse, BYOD and Export to Data Lake are going away: timeline and migration path

If you report on Dynamics 365 Finance & Operations data today, you almost certainly do it through an export route Microsoft is cleaning up: Export to Data Lake, BYOD, or one of the Synapse paths. Doing nothing is not an option — but neither is panic. The dates are set, and the migration is very plannable. Below is the timeline per route, using only dates and figures we can verify with Microsoft.

The timeline per route

| Route | Status | Dates | | --- | --- | --- | | Export to Data Lake | Deprecated, decommissioning under way | Deprecation 15 Oct 2023 · end of use 1 Nov 2024 · decommissioning started 25 March 2025 | | BYOD | Discouraged, no end date announced | Microsoft explicitly recommends transitioning | | Synapse paths | Keep working, innovation has stopped | New capabilities land in Fabric |

Export to Data Lake is the hardest case. Microsoft announced the deprecation effective 15 October 2023, existing customers could continue until 1 November 2024, and since 25 March 2025 the service is being decommissioned in phases — customers are notified before their turn comes. In Microsoft's own words: "Export to data lake service is deprecated as of November 1, 2024 and support will be limited." Anyone still reporting on it is reporting on a service that is formally being wound down.

BYOD has no announced end date — we say that honestly. But Microsoft's own transition FAQ leaves little room: "While a retirement date for BYOD service hasn't been determined, we recommend that you transition to Synapse Link or Fabric link services." Nothing new is coming; the clock is ticking, only the alarm has not been set yet.

The Synapse paths remain supported, and Microsoft says it wants to keep exports possible "well into the future". But the platform unification is unambiguous: new investment lands in Fabric, not in Synapse. Migrating to Synapse now means building on the previous generation — and moving again in a few years.

Why Fabric link is the logical destination

In 2022, reporting on F&O data was a maze of workarounds. With Fabric link that same connection is a single checkbox: a read replica of your D365 data in OneLake, with no ETL, no copies, and no pipelines to maintain. Three properties make it the logical destination:

  • No integration to operate. The connection is a Microsoft service, not a pipeline of yours. What you don't build, you don't maintain.
  • Open format. The data sits in OneLake as Delta Parquet — the data layer outlives any future product decision, Microsoft's or yours.
  • Double duty. The same Fabric capacity that runs your reporting also runs budgeting and forecasting. One migration pays for two workstreams.

The migration is smaller than it feels — but not zero

The connection itself is not the work. The work is in the reporting layer, because the schemas do change. The main differences, from Microsoft's transition documentation:

  • The ID field from the old exports is now called FnO_Id.
  • Deleted rows remain as soft deletes — filtering on the isDelete flag becomes mandatory in every query.
  • Column names that are reserved SQL words (such as Level, Resource) get a suffix.
  • Binary fields and legacy time-zone fields (TZID) are dropped; long text fields are truncated at 2,000 characters.

Every report and every pipeline that leans on the old schema has to pass through this. Which is exactly why this is the moment to decide per report: relocate or replace. A reporting layer built properly once — medallion architecture, one tested semantic model — is often less work than moving the old layer brick by brick.

What it costs

For most mid-market organisations the bill is manageable: an F4 capacity costs about €4,000 per year, an F8 about €8,100 (reserved, West Europe, excluding VAT). The full arithmetic per SKU, including pause schedules and reserved versus pay-as-you-go, is in what does Microsoft Fabric cost. And if you migrate anyway, two things come along for the ride: the BPA reporting module already included in your Finance licence, and the licensing arithmetic for budgeting and forecasting on that same capacity.

The step-by-step plan

  1. Inventory which export route sits under your reporting — there is often more than one.
  2. Map the consumers: which reports, pipelines and integrations read from the old schemas.
  3. Enable Fabric link alongside the existing route. Running in parallel is possible; you don't have to break anything to start.
  4. Move the reporting layer over, deciding per report: relocate or replace.
  5. Decommission the old route only once the numbers demonstrably reconcile.

The retirement dates above were verified on 14 August 2026 against Microsoft's transition FAQ and the Export to Data Lake documentation. Re-check them before a migration decision — Microsoft does adjust dates.