Hello, Welcome to MS Q&A
If your Azure Function with an HTTP trigger is working fine locally using func start but not finding the HTTP trigger when deployed, please try checking below steps
Endpoint Configuration: Ensure that the endpoint URL you are using to trigger the function in the cloud matches the format you used locally. The general format for the HTTP trigger is http://<YOUR_FUNCTION_APP>.azurewebsites.net/api/<FUNCTION_NAME>.
Function App Settings: Verify that your function app is correctly configured in Azure. Check the application settings and ensure that the function is enabled and that there are no restrictions on the HTTP methods being used.
Networking Issues: If your function app is behind a virtual network or has specific access restrictions, ensure that your requests are coming from an allowed source.
- Logs and Monitoring: Check the logs in Azure to see if there are any errors or messages that can provide insight into why the HTTP trigger is not being found.
By reviewing these aspects, you should be able to identify the issue with your HTTP trigger not being found.
References:
- Develop Azure Functions locally using Core Tools (TypeScript)
- Develop Azure Functions locally using Core Tools (PowerShell)
- Develop Azure Functions locally using Core Tools (JavaScript, TypeScript, Python, PowerShell)
Please let us know if any other questions
Kindly accept if it helps
Thanks
Deepanshu