What causes DF-SAPOODATA-StageContainerMissed?

The 'Container' field in the staging storage linked service or source options is empty. The staging container was deleted from the storage account but the ADF configuration still references it. The staging linked service points to a storage account where no containers exist. The container name contains invalid characters or exceeds Azure naming limits (3–63 lowercase characters)

How do I fix DF-SAPOODATA-StageContainerMissed?

In ADF Studio, open the SAP OData Source transformation > Source options and locate the staging storage container setting.. In the Azure portal, go to staging storage account > Containers and confirm the target container exists.. If no container exists, create one: click '+ Container', name it (e.g., 'adf-sap-staging'), set access to Private.. Update the container name in the ADF source options or linked service and re-publish.. Run a debug data flow to confirm staging works.

Medium severitydata flow

Power BI Refresh Error:
DF-SAPOODATA-StageContainerMissed

What does this error mean?

The SAP OData source is configured to use staging storage, but the container name in the staging linked service is missing or blank. ADF requires an explicit Blob Storage or ADLS Gen2 container name to stage SAP OData extractions — it cannot infer a default container.

Common causes

1The 'Container' field in the staging storage linked service or source options is empty
2The staging container was deleted from the storage account but the ADF configuration still references it
3The staging linked service points to a storage account where no containers exist
4The container name contains invalid characters or exceeds Azure naming limits (3–63 lowercase characters)

How to fix it

1In ADF Studio, open the SAP OData Source transformation > Source options and locate the staging storage container setting.
2In the Azure portal, go to staging storage account > Containers and confirm the target container exists.
3If no container exists, create one: click '+ Container', name it (e.g., 'adf-sap-staging'), set access to Private.
4Update the container name in the ADF source options or linked service and re-publish.
5Run a debug data flow to confirm staging works.

Frequently asked questions

What naming rules apply to the staging container?

Azure Blob Storage containers must use 3–63 lowercase letters, numbers, or hyphens — no leading or trailing hyphens. ADLS Gen2 file systems follow the same rules. The name must be unique within the storage account.

Can I use the same staging container for multiple SAP OData data flows?

Yes — multiple data flows can share a container. ADF writes to unique paths per run. Ensure the ADF managed identity has write access to the container root rather than a specific sub-path.

Is this the same error as StageLinkedServiceMissed?

No — StageLinkedServiceMissed means no staging linked service is configured at all. StageContainerMissed means the linked service exists but the container field within it is empty or invalid.

How do I find the staging container setting in ADF Studio?

In the data flow, click the SAP OData Source transformation > Source options tab. Look for 'Staging storage linked service' and 'Staging storage container' fields. Both must be filled in for the extraction to work.

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