What causes DF-Executor-StoreIsNotDefined?

The linked service referenced by the source or sink dataset was deleted or renamed in ADF Studio without updating the data flow. The data flow was imported or copied between ADF instances and the linked service with the same name does not exist in the target instance. A dataset was configured as an inline dataset without a linked service assigned — the transformation has no store to connect to. Recent infrastructure changes (linked service re-authentication or credential rotation) left the dataset referencing a deleted linked service

How do I fix DF-Executor-StoreIsNotDefined?

Open the failing source or sink transformation in ADF Studio and verify that a linked service (store) is selected — the dataset cannot be inline without a valid linked service assigned.. Check the dataset associated with the failing transformation and confirm it has a linked service assigned.. If the linked service was recently deleted or renamed, reassign a valid linked service to the dataset in ADF Studio.. Publish all pending changes in ADF Studio before rerunning — unsaved linked service or dataset changes may cause the store reference to be unresolved.. Enable debug mode to verify that all source and sink transformations resolve their linked services correctly before full execution.

Medium severitydata flow

Power BI Refresh Error:
DF-Executor-StoreIsNotDefined

What does this error mean?

A source or sink transformation in the data flow references a data store (linked service) that is not defined or has been removed. The data flow cannot resolve the connection for this transformation because no linked service is assigned to the dataset.

Common causes

1The linked service referenced by the source or sink dataset was deleted or renamed in ADF Studio without updating the data flow
2The data flow was imported or copied between ADF instances and the linked service with the same name does not exist in the target instance
3A dataset was configured as an inline dataset without a linked service assigned — the transformation has no store to connect to
4Recent infrastructure changes (linked service re-authentication or credential rotation) left the dataset referencing a deleted linked service

How to fix it

1Open the failing source or sink transformation in ADF Studio and verify that a linked service (store) is selected — the dataset cannot be inline without a valid linked service assigned.
2Check the dataset associated with the failing transformation and confirm it has a linked service assigned.
3If the linked service was recently deleted or renamed, reassign a valid linked service to the dataset in ADF Studio.
4Publish all pending changes in ADF Studio before rerunning — unsaved linked service or dataset changes may cause the store reference to be unresolved.
5Enable debug mode to verify that all source and sink transformations resolve their linked services correctly before full execution.

Frequently asked questions

How do I find which transformation is causing the StoreIsNotDefined error?

The error message names the affected transformation. Check each source and sink in ADF Studio — the transformation with a missing linked service is the cause.

We migrated our ADF to a new instance — why are store errors appearing?

Linked services are not exported with pipeline migrations. The data flow references them by name — recreate the linked service with the same name in the target instance.

Can I prevent this during linked service changes?

Before deleting or renaming a linked service, right-click it in ADF Studio and choose 'Find references' to see all dependent datasets — update them before removing the service.

Will downstream Power BI datasets be affected?

Yes — the data flow fails immediately and no data reaches the target. All downstream datasets and reports serve stale data until a valid linked service is assigned.

Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/data-flow-troubleshoot-guide