Finance | Project Operations, Human Resources, ...

Export to Data Lake in D365 F&O failing with Status Code 411

(2) Share

Report

Posted on by Ramkishor reddy

301

Hi everyone,

I’m facing an issue with Export to Data Lake in Dynamics 365 Finance & Operations where I’m getting Error (Status code 411) for all tables during activation.

This setup was working earlier, but suddenly stopped working.

What I’ve already verified:

Created a new client secret in Azure AD
Updated the Azure Key Vault with the new secret
Confirmed the client secret is active and not expired
Verified that the correct secret is referenced in Key Vault
Checked Key Vault access policies (Get/List permissions are properly assigned)
No changes were made in D365 F&O configuration
https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/finance-data-azure-data-lake

Current Issue:

Even after all the above validations, when I try to activate any table in Data Lake, I still receive Status code 411.

If anyone has faced a similar issue or has insights on what else to check (permissions, service principal roles, storage account access, etc.), please share your thoughts.

Thanks in advance!

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (4)

Answers (0)

Sort by

André Arnaud de Cal... 304,713 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Moved the question from the Dynamics 365 General to the Dynamics 365 Finance forum.

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 304,713 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Ramkishor,

The Export to Data Lake feature is deprecated for a while now. You can't use it anymore. Instead, you can use the Synapse link or Fabric link. This is mentioned at the top of the page you shared in your question.

Was this reply helpful? Yes No
Ramkishor reddy 301 on at

Like (0)

Report
Copy link

Link copied!

Hi @André Arnaud de Calavon

Thank you for your response.

Understood that the Export to Data Lake feature is deprecated and that moving to Synapse Link or Fabric Link is the recommended approach.

For the time being, could you please suggest if there is any workaround to keep the existing reports (built on top of the current Data Lake data) up and running?

This would help us ensure business continuity while we work on migrating to the supported options.

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 304,713 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Ramkishor,

Unfortunately, there is no option to continue using the Export to Data Lake feature. The feature was ended 12 months ago. After that, Microsoft started to decommission feature from all tenants. The move to either Synapse or Fabric should have been completed already a year ago to ensure business continuity.

Was this reply helpful? Yes No