What causes Fabric Pipeline Error 3607?

The `functionName` property was not included when the Azure Function activity was configured or scripted. An activity definition template or export omitted the functionName field during migration. A refactoring of the pipeline renamed or removed the functionName without updating the activity JSON. The activity was configured through the UI but the function name field was left blank and not validated

How do I fix Fabric Pipeline Error 3607?

Step 1: Open the failing Fabric Data Pipeline and select the Azure Function activity.. Step 2: Switch to the JSON/code view and locate the `typeProperties` section of the activity.. Step 3: Verify that a `functionName` property is present and contains the exact name of the Azure Function you intend to call.. Step 4: Add or correct the `functionName` value, ensuring it matches the function name as deployed in the Azure Function App.. Step 5: Save and re-run the pipeline, confirming the activity executes without Error 3607.

High severityconfigurationMicrosoft Fabric →

Power BI Refresh Error:
Fabric Pipeline Error 3607

What does this error mean?

The Azure Function activity in a Fabric Data Pipeline does not have a `functionName` property in its JSON definition, making it impossible for the pipeline to identify which function to invoke.

Common causes

1The `functionName` property was not included when the Azure Function activity was configured or scripted
2An activity definition template or export omitted the functionName field during migration
3A refactoring of the pipeline renamed or removed the functionName without updating the activity JSON
4The activity was configured through the UI but the function name field was left blank and not validated

How to fix it

1Step 1: Open the failing Fabric Data Pipeline and select the Azure Function activity.
2Step 2: Switch to the JSON/code view and locate the `typeProperties` section of the activity.
3Step 3: Verify that a `functionName` property is present and contains the exact name of the Azure Function you intend to call.
4Step 4: Add or correct the `functionName` value, ensuring it matches the function name as deployed in the Azure Function App.
5Step 5: Save and re-run the pipeline, confirming the activity executes without Error 3607.

Frequently asked questions

Is `functionName` case-sensitive?

Yes, Azure Function names are case-sensitive. The value in `functionName` must exactly match the name of the function as it appears in the Azure Function App.

Can I use a pipeline parameter to supply the function name dynamically?

Yes. You can use a dynamic expression such as `@pipeline().parameters.myFunctionName` as the value of the `functionName` property to make the activity reusable across environments.