Function App deployment successful, triggers found when running locally, but not when deploying

Question

Hi,

We have a serverless azure function that has been deploying and running fine until recently.
It still runs fine when debugging locally from VS Code (http triggers are found and work).
But when we deploy to Azure from VS code, the deployment succeeds but we get "No HTTP triggers found".
Obviously, we changed something in the code but cannot identify what.

My question: how can this be debugged?

​​https://APP_NAME.scm.azurewebsites.net/DebugConsole can’t be found.

​​https://APP_NAME.scm.azurewebsites.net shows the attached screen but the link "Deployments" returns "[]".

Thanks in advance for any tip.

Answer 1

Hello JDR

Your Azure function even if it contains others triggers besides HTTP, will run locally, since you may have installed storage simulations like Azurite. However, to run Azure functions in the cloud, it needs additional information and resources like a storage account (where its own binaries) may lie.

The proper way to deploy Azure functions on cloud is not from Visual Studio but using a proper Infrastructure-as-code (IaC) templates, like Azure Bicep (Or Terraform, if you are doing multi-cloud).

The following step-by-step tutorial may help you. Try this, and then add your code accordingly.

https://learn.microsoft.com/en-us/azure/azure-functions/functions-create-first-function-bicep?tabs=CLI

https://learn.microsoft.com/en-us/azure/azure-functions/functions-best-practices?tabs=csharp

Answer 2

Hi @JDR

With regards to your comment, you can Monitor executions in Azure Functions | Microsoft Learn. Regarding your original ask, if you didn't make any code changes and functions are no longer found, the runtime execution may have been changed on the deployed function app, see How to target Azure Functions runtime versions | Microsoft Learn for more details. Check the execution runtime from the drop-down under Function runtime settings in the Configuration blade. Based off what you've provided thus far, my guess is that it's different than what's running locally.