What causes DF-SAPODP-StageGen2PropertyInvalid?

The storage account name in the ADLS Gen2 staging linked service does not match the actual account. The endpoint suffix is wrong for the Azure environment — e.g. using .dfs.core.windows.net in a sovereign cloud environment. The ADLS Gen2 linked service references a storage account that does not have Hierarchical Namespace (HNS) enabled. A pipeline was migrated from a different environment and the Gen2 staging linked service properties were not updated

How do I fix DF-SAPODP-StageGen2PropertyInvalid?

In ADF Studio, open Manage > Linked services and open the ADLS Gen2 staging linked service.. Verify the storage account name matches the account in the Azure portal exactly.. Check the endpoint — for global Azure ADLS Gen2 it should be https:// .dfs.core.windows.net.. In the Azure portal, open the storage account > Settings > Properties and check Hierarchical namespace. If 'Disabled', the account is regular Blob — switch the staging linked service to Azure Blob Storage.. Click Test connection to verify the corrected linked service works, then save and retry the pipeline.

Medium severitydata source

Power BI Refresh Error:
DF-SAPODP-StageGen2PropertyInvalid

What does this error mean?

A required property of the ADLS Gen2 staging configuration for SAP ODP is incorrect.

Common causes

1The storage account name in the ADLS Gen2 staging linked service does not match the actual account
2The endpoint suffix is wrong for the Azure environment — e.g. using .dfs.core.windows.net in a sovereign cloud environment
3The ADLS Gen2 linked service references a storage account that does not have Hierarchical Namespace (HNS) enabled
4A pipeline was migrated from a different environment and the Gen2 staging linked service properties were not updated

How to fix it

1In ADF Studio, open Manage > Linked services and open the ADLS Gen2 staging linked service.
2Verify the storage account name matches the account in the Azure portal exactly.
3Check the endpoint — for global Azure ADLS Gen2 it should be https://<accountname>.dfs.core.windows.net.
4In the Azure portal, open the storage account > Settings > Properties and check Hierarchical namespace. If 'Disabled', the account is regular Blob — switch the staging linked service to Azure Blob Storage.
5Click Test connection to verify the corrected linked service works, then save and retry the pipeline.

Frequently asked questions

How do I tell if my storage account is ADLS Gen2 or regular Blob?

In the Azure portal, open the storage account > Settings > Properties and check 'Hierarchical namespace'. 'Enabled' means ADLS Gen2 (.dfs.core.windows.net endpoint); 'Disabled' means regular Blob — use the Azure Blob Storage linked service instead.

Can I switch from ADLS Gen2 staging to Blob staging without recreating the pipeline?

Yes — update the staging linked service in the SAP ODP source settings to point to Azure Blob Storage instead of ADLS Gen2. The data format is the same; only the storage type changes.

How is StageGen2PropertyInvalid different from StageBlobPropertyInvalid?

Same error type for different storage backends. StageBlobPropertyInvalid applies to Blob staging; StageGen2PropertyInvalid applies to ADLS Gen2 staging. The fix is identical: verify account name, endpoint, and credentials in the staging linked service.

Will downstream Power BI datasets be affected?

In the ADF Monitor, click the failed pipeline run, then click the failed activity. The activity detail pane shows the error code, error message, and any sub-error codes from the underlying connector.

Will downstream Power BI datasets be affected when an ADF pipeline fails?

Yes — a dataset refreshing after the pipeline will use stale data or fail if the target table was cleared. The Power BI refresh may succeed while serving wrong data.

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