What causes DF-SAPODATA-NotReached?

The SAP system is on-premises and a Self-Hosted IR is required but not configured — Azure IR cannot reach on-prem SAP directly. A corporate firewall is blocking outbound connections from the SHIR machine to the SAP Gateway port. The SAP Gateway or OData service is down or not responding on the configured host and port. The SHIR machine's network route to the SAP host was changed (VPN, proxy, or DNS change)

How do I fix DF-SAPODATA-NotReached?

In ADF Studio, open the SAP OData linked service and check whether 'Connect via integration runtime' is set to a Self-Hosted IR (required for on-prem SAP).. On the SHIR machine, test network connectivity: `telnet [SAP-host] [SAP-port]` or `Test-NetConnection [SAP-host] -Port [SAP-port]` in PowerShell.. Confirm the SAP ICM (Internet Communication Manager) is active: in SAP transaction SMICM, check that the HTTP/HTTPS service is green.. Check corporate firewall rules to ensure outbound TCP on the SAP Gateway port (443, 8000, or 44300) is allowed from the SHIR host.. If using a VPN or proxy, verify the SHIR machine's proxy settings allow it to reach the SAP host directly.

Medium severitydata source

Power BI Refresh Error:
DF-SAPODATA-NotReached

What does this error mean?

ADF's Integration Runtime cannot reach the SAP OData endpoint — the TCP connection to the SAP application server or SAP Gateway is blocked or failing. SAP OData endpoints run on port 443 (HTTPS) or custom ports like 8000/44300, and require a Self-Hosted Integration Runtime if the SAP system is on-premises or behind a corporate network.

Common causes

1The SAP system is on-premises and a Self-Hosted IR is required but not configured — Azure IR cannot reach on-prem SAP directly
2A corporate firewall is blocking outbound connections from the SHIR machine to the SAP Gateway port
3The SAP Gateway or OData service is down or not responding on the configured host and port
4The SHIR machine's network route to the SAP host was changed (VPN, proxy, or DNS change)

How to fix it

1In ADF Studio, open the SAP OData linked service and check whether 'Connect via integration runtime' is set to a Self-Hosted IR (required for on-prem SAP).
2On the SHIR machine, test network connectivity: `telnet [SAP-host] [SAP-port]` or `Test-NetConnection [SAP-host] -Port [SAP-port]` in PowerShell.
3Confirm the SAP ICM (Internet Communication Manager) is active: in SAP transaction SMICM, check that the HTTP/HTTPS service is green.
4Check corporate firewall rules to ensure outbound TCP on the SAP Gateway port (443, 8000, or 44300) is allowed from the SHIR host.
5If using a VPN or proxy, verify the SHIR machine's proxy settings allow it to reach the SAP host directly.

Frequently asked questions

Does this error affect all pipeline runs or just the current one?

Depends on the root cause. A persistent misconfiguration fails every run; a transient issue may resolve on retry. Check the run history.

Can this error appear in Azure Data Factory and Microsoft Fabric pipelines?

Yes — the same connector errors appear in both ADF and Fabric Data Factory pipelines.

How do I see the full error detail for an ADF pipeline failure?

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

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