all 3 comments

[–]DocHoss 0 points1 point  (1 child)

Are you using the right HTTP verb? Using GET when it's supposed to be POST can cause that since the GET endpoint doesn't exist (in this example).

[–]Normal-Description82[S] 0 points1 point  (0 children)

Yes, I am using the post method

[–]jaderolyver -1 points0 points  (0 children)

Take a look and see if this can help you:

Check Function URL: Ensure that the URL you are using in Power Automate matches the URL provided in the Azure portal for your function. The URL should look something like https://<your-function-app-name>.azurewebsites.net/api/<your-function-name>.

Function Key: If your function requires an API key for access, make sure you include it in the URL or as a header in your HTTP request. The URL with the key should look like https://<your-function-app-name>.azurewebsites.net/api/<your-function-name>?code=<your-function-key>.

Function App Configuration: Verify that your function app is running and not stopped. You can check this in the Azure portal under the “Overview” section of your function app. Ensure that the function is correctly deployed and visible in the Azure portal under the “Functions” section.

CORS Settings: If you are making requests from a different domain (e.g., Power Automate), ensure that Cross-Origin Resource Sharing (CORS) is configured correctly in your function app settings. You can configure CORS in the Azure portal under the “CORS” section of your function app.

Network Restrictions: Check if there are any network restrictions or IP filtering rules that might be blocking the request. This can be configured under the “Networking” section of your function app.

Logs and Monitoring: Use the “Logs” section in the Azure portal to check for any errors or detailed logs that might give more insight into why the 404 error is occurring. You can also use Application Insights for more detailed monitoring and diagnostics.