What causes Fabric Pipeline Error 3602?

The HTTP method field in the Azure Function Activity was set to an unsupported value such as PATCH or a custom method. A dynamic expression or parameter resolving the HTTP method produced an invalid or misspelled method name at runtime. The pipeline was migrated or copied from another tool and the HTTP method value was corrupted or changed in translation. A typo was introduced in the method name (e.g., 'POSTS' instead of 'POST')

How do I fix Fabric Pipeline Error 3602?

Step 1: Open the Azure Function Activity settings in your Fabric pipeline and locate the HTTP Method field.. Step 2: Ensure the HTTP method is set to one of the supported values: PUT, POST, GET, DELETE, OPTIONS, HEAD, or TRACE.. Step 3: If the HTTP method is set via a dynamic expression or pipeline parameter, validate that the expression resolves to a valid method name at runtime by using the Debug run feature.. Step 4: Save and republish the pipeline, then trigger a test run to confirm the error is resolved.. Step 5: Review any pipeline templates or copy operations that may have introduced the invalid method to prevent recurrence.

Medium severityconfigurationMicrosoft Fabric →

Power BI Refresh Error:
Fabric Pipeline Error 3602

What does this error mean?

The Fabric pipeline's Azure Function Activity was configured with an HTTP method that is not supported. Only a specific set of HTTP methods are valid for this activity type.

Common causes

1The HTTP method field in the Azure Function Activity was set to an unsupported value such as PATCH or a custom method
2A dynamic expression or parameter resolving the HTTP method produced an invalid or misspelled method name at runtime
3The pipeline was migrated or copied from another tool and the HTTP method value was corrupted or changed in translation
4A typo was introduced in the method name (e.g., 'POSTS' instead of 'POST')

How to fix it

1Step 1: Open the Azure Function Activity settings in your Fabric pipeline and locate the HTTP Method field.
2Step 2: Ensure the HTTP method is set to one of the supported values: PUT, POST, GET, DELETE, OPTIONS, HEAD, or TRACE.
3Step 3: If the HTTP method is set via a dynamic expression or pipeline parameter, validate that the expression resolves to a valid method name at runtime by using the Debug run feature.
4Step 4: Save and republish the pipeline, then trigger a test run to confirm the error is resolved.
5Step 5: Review any pipeline templates or copy operations that may have introduced the invalid method to prevent recurrence.

Frequently asked questions

Is PATCH supported as an HTTP method in the Azure Function Activity?

No, PATCH is not supported. The supported methods are PUT, POST, GET, DELETE, OPTIONS, HEAD, and TRACE. If your Azure Function requires a PATCH request, consider using a Web Activity instead, which supports a broader range of HTTP methods.

Can I use a pipeline parameter to dynamically set the HTTP method?

Yes, but you must ensure the parameter always resolves to one of the seven supported method strings. Add input validation or use an allowed-values list on the parameter to prevent invalid values from reaching the activity at runtime.