What causes Fabric Pipeline Error 3610?

The Function App URL is malformed, points to a non-existent endpoint, or has changed since the pipeline was configured. Network-level restrictions such as firewall rules, virtual network integration, or private endpoints are blocking the pipeline from reaching the Function App. The Azure Function App has been deleted, moved, or is in a stopped state. SSL/TLS certificate issues or HTTPS enforcement mismatches are causing the connection to fail before a response is received

How do I fix Fabric Pipeline Error 3610?

Step 1: Confirm the Function App still exists and is in a running state by checking the Azure Portal or using Azure CLI (`az functionapp show`).. Step 2: Verify the `functionAppUrl` in the activity definition is correct and reachable by testing it directly from a browser or using curl/Postman.. Step 3: Check whether the Function App has network restrictions (IP allowlists, VNet integration, or private endpoints) that may be blocking requests from Fabric pipeline's outbound IP ranges.. Step 4: If using a self-hosted integration runtime or gateway, ensure it has outbound network access to the Function App's domain and that no proxy is interfering with HTTPS traffic.. Step 5: Review the Function App's diagnostic logs and Azure Monitor for any endpoint-level errors coinciding with the pipeline failure timestamp.

High severityconnectivityMicrosoft Fabric →

Power BI Refresh Error:
Fabric Pipeline Error 3610

What does this error mean?

The Fabric pipeline encountered a general error when attempting to call the configured Azure Function endpoint. This typically indicates a network, DNS, or endpoint reachability problem rather than a code-level function failure.

Common causes

1The Function App URL is malformed, points to a non-existent endpoint, or has changed since the pipeline was configured
2Network-level restrictions such as firewall rules, virtual network integration, or private endpoints are blocking the pipeline from reaching the Function App
3The Azure Function App has been deleted, moved, or is in a stopped state
4SSL/TLS certificate issues or HTTPS enforcement mismatches are causing the connection to fail before a response is received

How to fix it

1Step 1: Confirm the Function App still exists and is in a running state by checking the Azure Portal or using Azure CLI (`az functionapp show`).
2Step 2: Verify the `functionAppUrl` in the activity definition is correct and reachable by testing it directly from a browser or using curl/Postman.
3Step 3: Check whether the Function App has network restrictions (IP allowlists, VNet integration, or private endpoints) that may be blocking requests from Fabric pipeline's outbound IP ranges.
4Step 4: If using a self-hosted integration runtime or gateway, ensure it has outbound network access to the Function App's domain and that no proxy is interfering with HTTPS traffic.
5Step 5: Review the Function App's diagnostic logs and Azure Monitor for any endpoint-level errors coinciding with the pipeline failure timestamp.

Frequently asked questions

How do I find which IP ranges Fabric Data Pipelines uses for outbound calls so I can allowlist them in my Function App firewall?

Microsoft publishes the Azure Data Factory and Fabric pipeline outbound IP ranges in the Azure IP Ranges and Service Tags JSON file. You can also use the `DataFactory` service tag in Azure network security group rules to allowlist traffic without managing individual IP addresses.

Is Error 3610 different from Error 3608?

Yes. Error 3608 means the pipeline reached the function and received an HTTP error response from the function itself, whereas Error 3610 means the pipeline could not complete the call to the endpoint at all, typically due to a network or infrastructure issue before the function had a chance to respond.