MetricSign
EN|NLRequest Access
High severitydata source

Power BI Refresh Error:
DynamicsFailedToRequestServer

What does this error mean?

ADF could not send an API request to Dynamics 365 or Dataverse — network connectivity issues or server unavailability.

Common causes

  • 1A transient network interruption between the integration runtime and the Dynamics / Dataverse endpoint
  • 2The Dynamics 365 service is experiencing an outage or maintenance window
  • 3SSL/TLS issues between the integration runtime and the Dynamics endpoint
  • 4The integration runtime cannot resolve the Dynamics service DNS hostname

How to fix it

  1. 1Add a retry policy to the copy activity to handle transient server request failures.
  2. 2Check the Microsoft 365 and Dynamics service health dashboard for active incidents.
  3. 3Verify network connectivity from the integration runtime to the Dynamics service endpoint.
  4. 4If using a self-hosted IR, confirm DNS resolution of the Dynamics endpoint works from the IR machine.

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-dynamics-dataverse

Other data source errors