Error Deploying Azure Function from VS Code: 'No HTTP triggers found'

idea-seeds 25 Reputation points
2025-04-24T06:54:42.7266667+00:00

I am trying to overwrite deploy code that I was previously able to deploy to an Azure Function App using VS Code, but I am unable to deploy it. So, I tried to investigate by creating new sample code and new Function App on the Azure. Even it's brand new one, the deployment seems to be successful, but the console in VS Code displays "No HTTP triggers found," and it appears that the files themselves are not present on Azure.

What can I do to successfully deploy a Function App from VS Code?

What I have tried:

(Note: Some details like the Function App name have been replaced with [******REDACTED******].)

  1. Start VS Code.
  2. To create a new template, perform the following actions in the VS Code command palette:
    1. Select > Azure Functions: Create New Project.
    2. Specify a particular folder as the project save location.
    3. Choose "Python" as the language.
    4. For the Python execution environment, select "Skip virtual environment."
    5. Choose "HTTP trigger" as the template.
    6. Specify "http_trigger" as the function name for the template.
    7. Set the auth level to "FUNCTION."
    8. Select "Open in current window."
  3. Run func host start to confirm that it can run in the local environment.
  4. To deploy the newly created template, I created a new Function App by performing the following actions in the VS Code command palette:
    1. Select > Azure Functions: Create Function App in Azure (advanced).
    2. Specify a name for the Function App.
    3. Choose "Linux Consumption" as the type.
    4. Select "Japan East" as the region.
    5. Choose "Python 3.11" as the stack.
    6. Select my resource group for the Function App.
    7. Choose "Create new storage account."
    8. Specify a name for the storage account.
    9. Select "Skip for now" for Application Insights.
    10. Select "Create Assigned identity" for Assigned identity.

The output displayed in VS Code after executing these steps was as follows:

16:11:16: Failed to get latest templates: The operation was aborted. Rejecting from abort signal callback while making request.
16:15:41: Creating user assigned identity "[******REDACTED******]" in location "Japan East"...
16:15:42: Successfully created user assigned identity "[******REDACTED******]".
16:15:42: Ensuring App Service plan "[******REDACTED******]" exists...
16:15:42: Creating App Service plan "[******REDACTED******]"...
16:15:44: Successfully created App Service plan "[******REDACTED******]".
16:15:44: Creating storage account "[******REDACTED******]" in location "Japan East" with sku "Standard_LRS"...
16:16:09: Successfully created storage account "[******REDACTED******]".
16:16:10: Role assignment "Storage Blob Data Owner" created for the storageAccounts resource "[******REDACTED******]".
16:16:10: Creating new function app "[******REDACTED******]"...
16:16:34: Successfully created function app "[******REDACTED******]": https://[******REDACTED******].azurewebsites.net
  1. Select > Azure Functions: Deploy to Function App.
    1. Choose the previously created Function App name.
    2. When warned that it will overwrite and cannot be undone, select "Deploy."

As a result, the following logs were displayed in the VS Code output, indicating that no HTTP Trigger function exists.

16:18:32 [******REDACTED******]: Starting deployment...
16:18:33 [******REDACTED******]: Creating zip package...
16:18:33 [******REDACTED******]: Adding 4 files to zip package...
16:18:33 [******REDACTED******]: c:\[******REDACTED******]\testing\requirements.txt
16:18:33 [******REDACTED******]: c:\[******REDACTED******]\testing\host.json
16:18:33 [******REDACTED******]: c:\[******REDACTED******]\testing\function_app.py
16:18:33 [******REDACTED******]: c:\[******REDACTED******]\testing\.funcignore
16:18:33 [******REDACTED******]: Zip package size: 1.28 kB
16:18:34 [******REDACTED******]: Fetching changes.
16:18:35 [******REDACTED******]: Cleaning up temp folders from previous zip deployments and extracting pushed zip file /tmp/zipdeploy/[******REDACTED******].zip (0.00 MB) to /tmp/zipdeploy/extracted
16:18:38 [******REDACTED******]: Updating submodules.
16:18:39 [******REDACTED******]: Preparing deployment for commit id '7e4a567c-3'.
16:18:39 [******REDACTED******]: PreDeployment: context.CleanOutputPath False
16:18:39 [******REDACTED******]: PreDeployment: context.OutputPath /home/site/wwwroot
16:18:39 [******REDACTED******]: Repository path is /tmp/zipdeploy/extracted
16:18:39 [******REDACTED******]: Running oryx build...
16:18:39 [******REDACTED******]: Command: oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform python --platform-version 3.11 -p packagedir=.python_packages/lib/site-packages
16:18:40 [******REDACTED******]: Querying triggers...
16:18:47 [******REDACTED******]: No HTTP triggers found.

What steps can I take to investigate this further, or solve this?

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
5,909 questions
{count} vote

Accepted answer
  1. Sai Prabhu Naveen Parimi 2,260 Reputation points Microsoft External Staff Moderator
    2025-05-13T06:17:13.7366667+00:00

    @idea-seeds

    The root cause was that the AzureWebJobsStorage setting was missing in the Function App’s configuration. Here's what we did:

    In the Azure Portal, we went to the customer’s Function AppConfigurationApplication settings, and added the key:

    AzureWebJobsStorage with the connection string from the linked Storage Account.

    After redeploying from VS Code, we tested the function URL in the browser and it responded with:

    "This HTTP triggered function executed successfully. Pass a name in the query string..."

    Everything worked fine after that.

    Sharing this here in case it helps others running into the same “No HTTP triggers found” issue when deploying from VS Code.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.