What causes Fabric Pipeline Error 3612?

The linked service reference was not included when the Azure Function activity was defined programmatically or imported from an external template. The linked service was deleted or renamed after the pipeline was originally created, leaving a broken reference. A partial pipeline export or migration omitted the linked service definition from the activity JSON. Manual JSON editing accidentally removed the connection details block from the activity definition

How do I fix Fabric Pipeline Error 3612?

Step 1: Open the failing pipeline in Fabric Data Factory and select the Azure Function activity that is producing Error 3612.. Step 2: Switch to the JSON editor and inspect the activity definition for the presence of a linked service block containing the Azure Function App connection details.. Step 3: If the linked service block is absent, add it by referencing an existing Azure Function linked service or create a new linked service pointing to the correct Function App URL.. Step 4: Ensure the linked service includes the `functionAppUrl` and any required authentication settings (e.g., function key or managed identity).. Step 5: Save, validate, and re-run the pipeline to confirm the linked service resolves correctly and the activity executes.

High severityconfigurationMicrosoft Fabric →

Power BI Refresh Error:
Fabric Pipeline Error 3612

What does this error mean?

The Azure Function activity JSON definition is missing the linked service connection details required to authenticate and connect to the target Azure Function App. The pipeline cannot resolve the endpoint without this configuration.

Common causes

1The linked service reference was not included when the Azure Function activity was defined programmatically or imported from an external template
2The linked service was deleted or renamed after the pipeline was originally created, leaving a broken reference
3A partial pipeline export or migration omitted the linked service definition from the activity JSON
4Manual JSON editing accidentally removed the connection details block from the activity definition

How to fix it

1Step 1: Open the failing pipeline in Fabric Data Factory and select the Azure Function activity that is producing Error 3612.
2Step 2: Switch to the JSON editor and inspect the activity definition for the presence of a linked service block containing the Azure Function App connection details.
3Step 3: If the linked service block is absent, add it by referencing an existing Azure Function linked service or create a new linked service pointing to the correct Function App URL.
4Step 4: Ensure the linked service includes the `functionAppUrl` and any required authentication settings (e.g., function key or managed identity).
5Step 5: Save, validate, and re-run the pipeline to confirm the linked service resolves correctly and the activity executes.

Frequently asked questions

Does deleting a linked service in Fabric automatically update all pipelines that reference it?

No — Fabric does not automatically remove or update activity definitions that reference a deleted linked service. You must manually update each affected pipeline activity to point to a valid linked service.

Can I use a managed identity instead of a function key in the Azure Function linked service?

Yes — Fabric Data Factory supports managed identity authentication for Azure Function linked services, which is the recommended approach for production pipelines to avoid storing function keys as secrets.