Back to Blog
Published:
Last Updated:
Fresh Content
ERP Write-Back & IntegrationChapter 9

Is BYOD retired?

8 min read
1,750 words
high priority
Muhammad Mudassir

Muhammad Mudassir

Founder & CEO, Cognilium AI

TL;DR

Microsoft's transition FAQ answers this under its own heading, on a page revised in July 2026 — a retirement date for BYOD hasn't been determined, and Microsoft recommends transitioning in the same sentence. Both halves are the answer. Here are the five Microsoft pages checked, the four dates Microsoft documents for Export to Data Lake, why any single-date summary of it is wrong, and why a bounded no is still not a reason to stay.

Is BYOD retired?

No — and the reason to move anyway is better than a deadline would be. Microsoft's own transition FAQ, revised in July, says a retirement date "hasn't been determined" while recommending in the same sentence that you transition. Both halves of that are load-bearing.

Microsoft's sentence, and the date on the page carrying it

BYOD (bring your own database — the feature that exports finance and operations data entities into an Azure SQL database you own) has its own question on Microsoft's transition FAQ. The heading is Is BYOD service retired? Is there a retirement date? The answer:

"While a retirement date for BYOD service hasn't been determined, we recommend that you transition to Synapse Link or Fabric link services." — Azure Synapse Link transition FAQ

That page declares ms.date: 2026-07-23 and updated_at: 2026-07-24. It is nine days old, which matters more than usual for a question about whether something has ended.

So the label is [GA] with a transition recommendation attached — not [DEPR]. Those carry different obligations, and the difference is the whole article.

The five Microsoft pages we opened, and what each says

A retirement date, if one existed, would appear on at least one of these. All five were opened on 1 August 2026, and the dates below are the pages' own.

  • Azure Synapse Link transition FAQ — ms.date: 2026-07-23 · What it says about a BYOD retirement date: States it directly: the date "hasn't been determined", plus a recommendation to transition
  • Bring your own database (BYOD) — ms.date: 2026-01-15 · What it says about a BYOD retirement date: Documents the feature in the present tense, including service tiers and limitations. Carries no deprecation or retirement notice
  • Removed or deprecated platform features — ms.date: 2026-06-09 · What it says about a BYOD retirement date: BYOD, bring your own database and Entity export to database return no occurrence
  • Removed or deprecated features in Dynamics 365 Finance — ms.date: 2025-12-17 · What it says about a BYOD retirement date: Same three terms return no occurrence
  • Export to Azure Data Lake overview — ms.date: 2026-01-16 · What it says about a BYOD retirement date: BYOD appears only as a thing you can transition from, in a section arguing the case for moving

One near-miss is worth naming, because it is where a careful person would look first. Microsoft also publishes Removed or deprecated features in previous releases, and BYOD is absent there too — but its opening callout reads "This article is no longer updated."

Silence on a page that says it is not maintained is not evidence. The two current lists above are the ones that count.

The other correction: Export to Data Lake has four dates, not one

If you have Export to Data Lake filed as "retired in November 2024", that single date collapses four documented ones — and it is not the date Microsoft gives for decommissioning.

  • Deprecation announced — Date: October 15, 2023 · Microsoft's own wording, and the page carrying it: "we've announced the deprecation of the Export to Data Lake feature, effective October 15, 2023" — Export to Azure Data Lake overview
  • End of normal use — Date: November 1, 2024 · Microsoft's own wording, and the page carrying it: "If you're already using the Export to Data Lake feature, you can continue to use it until November 1, 2024" — same page
  • Decommissioning begins — Date: March 25, 2025 · Microsoft's own wording, and the page carrying it: "We plan to decommission export to data lake service beginning March 25, 2025" — transition FAQ
  • Staged, customer by customer — Date: After that date · Microsoft's own wording, and the page carrying it: "We plan to start the decommissioning process with customers who have completed the transition as well as customers who aren't actively using the service" — transition FAQ

Two things follow. First, the decommissioning began on a date; it was not a switch. Microsoft attaches a "past due extension" process to it — "You'll be notified before the decommission process begins and have the option to ask for a past due extension" — so even the staged date was not the same date for every customer.

Second, Microsoft's own two pages date the deprecation differently. The overview page dates the deprecation effective October 2023, with use permitted until November 2024; the FAQ says "deprecated as of November 1, 2024, but will continue to operate under limited support until March 25, 2025."

Microsoft publishes no page reconciling the two, and this article does not either. Anyone reading one page and not the other produces a confidently wrong sentence, and that is how "retired in November 2024" happened.

Deprecated is not removed, and Microsoft defines both

The vocabulary is doing real damage here, and Microsoft supplies the fix. Both current lists open with the same two lines:

"A removed feature is no longer available in the product." "A deprecated feature isn't in active development and might be removed in a future update." — Removed or deprecated platform features

Read against those definitions: Export to Data Lake is deprecated and being decommissioned on a published, staged schedule [DEPR]. BYOD is on neither list and has no determined retirement date [GA]. "Retired" is a third word that means the thing has stopped, and applying it to either one is a claim nobody has made.

A bounded no is not an endorsement

Here is where the correction has to stop being a defence. Microsoft recommends you transition, and the reasons are on BYOD's own page rather than in anybody's marketing.

  • A production-grade Azure SQL database you size and pay for — Minimum tiers "For production environments": P4 or higher, S6 or higher, BC\_Gen5\_8 or higher, HS\_Gen5\_24 or higher, GP\_Gen5\_8 or higher
  • No composite entities — "Currently, you can't use BYOD to export composite entities into a database"
  • No incremental push without a unique key — "You can't export entities that don't have unique keys by using incremental push"
  • A scheduling path you can't use — "Use of recurring exports in Manage > Manage recurring data jobs for BYOD isn't supported. You must use the Export in batch option"
  • Serialised cross-company exports — From version 10.0.16, "all execution across companies is sequential per company", so "jobs with a high number of entities and companies take longer to run"

And the comparison Microsoft draws: on the Synapse Link side, "The table limits in the Export to Data Lake service aren't applicable in Azure Synapse Link for Dataverse", and the FAQ says "we want to enable you to export data well into the future."

The honest summary for a CIO: on the five pages in section 2 there is no deadline, and there is a bill. No deadline means you plan the move rather than execute it under a notification — a better position than the market is describing, and a worse reason to do nothing than it sounds.

One caution before you treat the destination as settled ground. The Synapse path carries a live date dispute of its own: the trusted-services firewall exception underneath it was dated for retirement on 1 August 2026 in Microsoft's documentation, while a Microsoft Q&A answer from a moderator badged Microsoft External Staff describes a move to 2027. We wrote that up separately.

Do not resolve it from a blog, including this one — open the Azure portal, go to Service Health, and read the notification sent to your own subscription.

What to do this quarter

  1. Write down where your BYOD extract feeds. Reports, a warehouse, a downstream pipeline, an integration nobody owns. That list is the migration, not the feature.
  2. Count entities without unique keys. Microsoft's BYOD page says incremental push requires one, so those are the entities running full pushes, which is one thing worth timing your export window against.
  3. Price the Azure SQL database against a Dataverse storage increase. We set the two paths side by side with Microsoft's own figures.
  4. Diary a re-check rather than a migration date. The transition FAQ is where Microsoft's answer lives today, so its ms.date is the signal to watch.
  5. Stop quoting retirement dates you did not read on a Microsoft page. Including ours.

Where we would draw the line

We would not tell you to migrate this quarter. No page in section 2 publishes a date forcing it, and a migration run to an absent deadline is how a data platform ends up half-moved across two budget years.

We would also not tell you to wait: Microsoft's recommendation is explicit, the destination is generally available, and BYOD's limitations are documented rather than alleged.

And we would not run this project for you. Choosing and building the analytics path is your data team's work with your implementation partner, and that layer is where we stay out.

What we own is what happens after the data lands. An Optimizer trains on that history and optimizes the decision on top of it — the safety-stock level, the margin-optimal price — so what we ask about your extract is which surface it uses and how fresh it is.

Dynamics 365 stays the system of record; the optimizer is the system of intelligence beside it, and only ever as current as the feed beneath it.

About Cognilium Cognilium is the AI optimization layer for Dynamics 365 — complementary apps that optimize the pricing, inventory, warehouse and planning decisions your ERP manages but can't optimize. Built on Power Platform, Dataverse and Azure. https://cognilium.ai · https://www.linkedin.com/company/37180269/

If an Optimizer of yours will read Dynamics 365 history through an extract, the path underneath it is part of its accuracy. Book a fifteen-minute call and we will walk your data path with you — which surface, how fresh, and what a move would change. No deck. https://cognilium.ai

Sources

Sources

Share this article

The work behind this series
AI optimization apps for Dynamics 365

The write-back mechanism every optimizer shares — read the system of record, compute the decision, return it behind an approval step.

Muhammad Mudassir

Muhammad Mudassir

Founder & CEO, Cognilium AI

Mudassir Marwat's argument is that ERP systems record decisions they never optimise.

Founder & CEO of Cognilium AI; 37 AI agents in production across four products; 4 production AI products built and operated; three clouds in production (AWSGCPAzure)
Agentic AIRAG → GraphRAG retrievalVoice AIMulti-Agent Orchestration
ContactView Profile
Next in this series
Did the Synapse trusted-services firewall exception retire on 1 August 2026?
Chapter 10 · 8 min
In short

Key takeaways

  • Microsoft's transition FAQ states that a retirement date for BYOD hasn't been determined, and recommends transitioning in the same sentence. Both halves are the answer; quoting either one alone produces a wrong article.
  • Deprecated and removed are defined differently on Microsoft's own lists — a deprecated feature isn't in active development and might be removed later, whereas a removed feature is already gone. "Retired" is a third word appearing in neither definition, so it is not a claim either list makes.
  • Export to Data Lake carries an announcement date, an end-of-normal-use date, a decommissioning start date and a staged rollout with an extension process. Any single-date summary of it is wrong, and the two Microsoft pages describing it do not agree on which date is the deprecation.
  • A page that tells you it is no longer updated cannot be used as evidence that something is absent. Microsoft's older removed-or-deprecated article says exactly that in its opening callout.
  • Having no published retirement date is a planning advantage, not a reason to stay. The documented cost of the older export path is a database you size and pay for, plus Microsoft's stated limitations on composite entities, incremental push and cross-company scheduling.
What goes wrong

Common mistakes to avoid

  • Answering "is BYOD retired?" from memory or from someone's summary. Microsoft's transition FAQ answers that exact question under its own heading, and the answer as written is that a retirement date hasn't been determined.
  • Reading "deprecated" as "switched off". The service Microsoft did deprecate was decommissioned in stages, with notification and an extension process attached.
  • Treating the destination as risk-free because the origin is deprecated. The Azure Synapse path carries its own live networking change, and Microsoft's documentation and a Microsoft support answer currently give different dates for it.
  • Checking a deprecation list without checking whether that list is maintained. Microsoft publishes both a current one and an archived one, and only the current one is evidence.