BeyondERP.Newsletter
Menu

Setup page · System administration

Export to Data Lake

A setup page for Export to Azure Data Lake, a retired service that permanently stops on November 30, 2026; until then it exports finance and operations table data to Azure Data Lake Storage Gen2.

Business process
Administer system features
Menu item
DataFeedsDefinitionWorkspace
Setup steps
1 on this page
Show what matters for
PAGE GUIDEWhat the page does and how to use it8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA setup page for Export to Azure Data Lake, a retired service that permanently stops on November 30, 2026; until then it exports finance and operations table data to Azure Data Lake Storage Gen2.
What you do hereUse this page only to manage tables that an existing export still sends while you move them to Azure Synapse Link for Dataverse or Link to Microsoft Fabric; don't build new pipelines on it.
ExampleFor example, BEAT lists the tables it still exports on the Choose Tables tab, sets up the same tables in Azure Synapse Link for Dataverse, checks that the figures match, and then deactivates them here before November 30, 2026.
Export to Data Lake page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

Business processAdminister system features
Menu pathSystem administration › Setup › Export data to Azure data lake › Export to Data Lake
Set up firstData entity row version change tracking validation report Microsoft Learn
Used next byExport Entity Store to Azure data lake Checked in Dynamics 365
Related pagesEntity Store Checked in Dynamics 365
End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

Step by step, with screenshots

Set up Export to Data Lake1 screen

Use this page to keep table data and metadata in the data lake up to date through initial and incremental exports.

  1. Screen 1

    Review an existing Export to Data Lake feed before moving it

    Go to System administration > Setup > Export data to Azure data lake > Export to Data Lake

    1. Open the page only to review an existing feed: Export to Data Lake is retired, and Microsoft set November 30, 2026 as the date it stops exporting
    2. On the Choose Tables tab, check which tables are still active
    3. Plan the move of those tables to Azure Synapse Link for Dataverse or Link to Microsoft Fabric; do not activate new tables here
    Review an existing Export to Data Lake feed before moving it (zoomed on the outlined fields)
    Show the full screenReview an existing Export to Data Lake feed before moving it
    page title tab to open what to set or check

How to use it

  1. Go to System administration > Setup > Export data to Azure data lake > Export to Data Lake.
  2. On the Choose Tables tab, use Filter by status to narrow the list of tables.
  3. Select a table, then select Activate or Deactivate.
  4. Select Add Tables to add tables to the list.
  5. Select the Choose using Entities tab to pick tables by entity.
  6. Open the Manage tab to find Rebuild data feed catalog and Metadata.

Source: Checked in Dynamics 365

Fields on the page

FieldWhat it means
Choose Tables (tab)Lists the tables in the export; Filter by status narrows the list and Activate or Deactivate starts or stops a table.Checked in Dynamics 365
Choose using Entities (tab)Picks the tables to export through data entities.Checked in Dynamics 365
Rebuild data feed catalog (Manage)Rebuilds the list of tables the export can offer.Checked in Dynamics 365

Common errors and fixes

MessageWhat to do
The data lake stops receiving new or changed dataExport to Azure Data Lake permanently stops on November 30, 2026, with no extensions. Move the tables to Azure Synapse Link for Dataverse or Link to Microsoft Fabric. Microsoft Learn

Test checklist

  1. List every table exported today and the downstream consumers.
  2. Set up the same tables in Link to Microsoft Fabric or Azure Synapse Link for Dataverse.
  3. Change a record and check the change reaches the new destination.
  4. Point downstream reports to the new destination and check the figures match.
  5. Uninstall the Export to Data lake add-in from the environment page in Lifecycle Services.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Set up Export to Data LakeDon't use it for new pipelines; move existing ones to Link to Microsoft Fabric or Azure Synapse Link for Dataverse, then uninstall the Export to Data lake add-in in Lifecycle ServicesExport to Azure Data Lake was retired on November 1, 2024 and permanently stops on November 30, 2026, after which it doesn't export new or changed data.Which service replaces Export to Data Lake?Export to Azure Data Lake is retired, and Microsoft set November 30, 2026 as the date it permanently stops exporting new or changed data; design new data pipelines on Azure Synapse Link for Dataverse (or Link to Microsoft Fabric) instead.Test: Tables move to the replacement before the service stops

Feature management and licence

Licence or add-inMicrosoft replaces the service with Azure Synapse Link for Dataverse. No Feature management feature needs to be turned on for this page.

Microsoft Learn

Solution architect

5Design impact

Shared or per companyEnvironment-wide: the export runs through the Export to Data lake add-in installed on the environment in Lifecycle Services. Microsoft Learn
Can it be undoneOne-way: Warning: After November 30, 2026 Export to Data Lake permanently stops and can't be extended. Uninstalling the add-in starts turning off change data capture for its tables. Microsoft Learn
If you change it laterExport to Azure Data Lake is retired: Microsoft set November 30, 2026 as the date it stops exporting new or changed data and replaces it with Azure Synapse Link for Dataverse, so new data pipelines should not be built on it. Microsoft Learn
Technical architect

6Technical

Menu itemDataFeedsDefinitionWorkspace Checked in Dynamics 365
FormDataFeedsDefinitionWorkspace Checked in Dynamics 365
Who can open itPrivilegesData feeds security privilege DataFeedsModelSecurityPrivilegeDutiesData feeds security duty DataFeedsModelSecurityDutyChecked in Dynamics 365
Actions on the pageManage: Rebuild data feed catalog, MetadataOptionsChecked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=DataFeedsDefinitionWorkspace
Data migrationLoad order: Export to Data Lake has no data entity in Data management, so it can't be loaded from a file or a configuration template. The table selection is made on this page in each environment; for the replacement, choose the tables in Azure Synapse Link for Dataverse.Checked in Dynamics 365
Everyone

8Sources