MetricSign
EN|NLRequest Access
Medium severitydata source

Power BI Refresh Error:
HttpSourceUnsupportedStatusCode

What does this error mean?

The HTTP source returned a status code ADF does not treat as success. By default, ADF expects HTTP 200 — other 2xx or redirect codes may trigger this error.

Common causes

  • 1The HTTP server returned a 201, 204, or 3xx redirect that ADF does not handle for the file source
  • 2The API returns a non-200 success code that is not in the ADF accepted status code list

How to fix it

  1. 1Review the HTTP server response to understand which status code was returned.
  2. 2Update the ADF HTTP source additional headers or request settings if a different response code indicates success.
  3. 3If the server returns a redirect (3xx), ensure the linked service is configured to follow redirects.
  4. 4Contact the ADF support team if the status code is a valid success code not recognized by ADF.

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/connector-troubleshoot-ftp-sftp-http

Other data source errors