Hi Shaarang,
Thanks for reaching out to Microsoft Q&A.
Function Key:
- Since your function's authorization level is set to "Function", you need to provide a function key when calling it.
- Make sure the Azure Function Linked Service in your Synapse pipeline is configured with the correct function key.
- In Synapse, ensure that this key is passed as a header with the key
"x-functions-key"
and the value set to the copied function key.
Linked Service Configuration:
- Double-check the Azure Function Linked Service configuration in Synapse.
- Ensure the function app name, function name, and function key are all correct.
Managed Identity:
- If you're using MI for authentication, make sure it's properly configured and has the necessary permissions to invoke the function.
Network Security:
- Since you mentioned a private endpoint, ensure that the Synapse workspace has the necessary network access to the Function App's private endpoint.
- Since you're using a private endpoint, ensure that the Synapse workspace has the necessary network configurations to communicate with the Azure Function App through its private endpoint.
- Make sure that the Private DNS Zone is set up correctly, and that the Synapse pipeline can resolve the function app's private endpoint URL. Verify that the Managed Private Endpoint for Synapse to the Function App is approved and in a healthy state.
Function App Configuration:
- Check if there are any IP restrictions or authentication rules in the Function App that might be blocking the request from Synapse.
Please 'Upvote'(Thumbs-up) and 'Accept' as an answer if the reply was helpful. This will benefit other community members who face the same issue.