Azure function is not deployed from VS - No HTTP triggers found

Benjamin Koubik 50

I created an Azure POST function that works wonderfully locally. When I deploy the whole thing using VS, I see 'No HTTP triggers found.' in the output. The function does not appear in my dashboard

User's image

navba-MSFT 24,910 Reputation points Microsoft Employee

2023-10-25T06:34:17.75+00:00
@Benjamin Koubik Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

I understand that you are facing an issue with deploying an Azure Function from Visual Studio, where you see the error message No HTTP triggers found in the output, and the function does not appear in their dashboard.

Please follow the below suggestions step by step:

Navigate to Advanced tools and debug console: https://<APPNAME>.scm.azurewebsites.net/DebugConsole, browse to C:\home\site\wwwroot and check if the Functions are there

Navigate to C:\home\data\SitePackages and check if the latest zip file contains the Functions and the packagename.txt is updated. Please download and check the code contents of your zip file.

Manually Syncing Triggers:

Restart your function app in the Azure portal.

Send an HTTP POST request to https://{functionappname}.azurewebsites.net/admin/host/synctriggers?code=<API_KEY> using the master key.

Send an HTTP POST request to https://management.azure.com/subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RESOURCE_GROUP_NAME>/providers/Microsoft.Web/sites/<FUNCTION_APP_NAME>/syncfunctiontriggers?api-version=2016-08-01. Replace the placeholders with your subscription ID, resource group name, and the name of your function app. This request requires an access token in the Authorization request header.

When you deploy using an external package URL, you need to manually restart your function app to fully sync your updates when the package changes without changing the URL.

More Info here.

Action Plan (if above steps doesn't help): 1.Please try to deploy using the zip deployment method and check if that helps. You can use the below command to publish your function app:

func azure functionapp publish <APP_NAME>

2.The language of your function app is maintained in the FUNCTIONS_WORKER_RUNTIME AppSetting in Azure Function App Portal. Ensure that you have set it correctly.
3.Also ensure that the Func Core tools are up to date.
4.Please check the AzureWebJobsStorage setting in local.settings.json.
You need to update the value to the Azure Storage connection string:

DefaultEndpointsProtocol=https;AccountName=<ACCOUNT NAME>;AccountKey=<ACCOUNT KEY>;EndpointSuffix=core.windows.net

Also ensure the same connectionstring is placed in the App settings in Azure.

Hope this helps.

If none of the above action plan helps, please let me know. I would be happy to assist you further.

**

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Benjamin Koubik 50

@navba-MSFT Thank you for your quick support. Unfortunately, I have to report that the problem persists. I have successfully completed all of the points listed above. The function (only one) IS available under C:\home\site\wwwroot, as well as the last ZIP file under C:\home\data\SitePackages. The packagename.txt refers to the last ZIP file. An HTTP POST to the URL https://{functionappname}.azurewebsites.net/admin/host/synctriggers?code=<API_KEY> returns the status code success. AzureWebJobsStorage has already been set correctly by default both in the json file and in the settings. FUNCTIONS_WORKER_RUNTIME is set to 'node', which is correct. I provided my function here, it's not rocket science, but that's why it fails

const {
  DocumentAnalysisClient,
  AzureKeyCredential,
} = require("@azure/ai-form-recognizer");
const { app } = require("@azure/functions");

app.http("startAnalysing", {
  methods: ["POST"],
  authLevel: "anonymous",
  handler: async (request) => {
    const { url } = await request.json();

    const client = new DocumentAnalysisClient(
      process.env.FORM_RECOGNIZER_ENDPOINT,
      new AzureKeyCredential(process.env.FORM_RECOGNIZER_API_KEY)
    );

    const poller = await client.beginAnalyzeDocument(
      process.env.FORM_RECOGNIZER_CUSTOM_MODEL_ID,
      url,
      {
        onProgress: ({ status }) => {
          console.log(`status: ${status}`);
        },
      }
    );

    const {
      documents: [document],
    } = await poller.pollUntilDone();

    if (!document) {
      throw new Error("Expected at least one document in the result.");
    }
    return { body: JSON.stringify(document.fields) };
  },
});

locale.settings.json file:

{
  "IsEncrypted": false,
  "Values": {
    "AzureWebJobsStorage": "DefaultEndpointsProtocol=https;AccountName=aidocumentanalysing;AccountKey=8DOb+NvimZg1b9GOCi1IeUTT7ZSq8fAJkqEXbqx0GOtfhSoAl4LNVvkz3BDIhcsvKu81xurMUqku+AStPfVeLQ==;EndpointSuffix=core.windows.net",
    "FUNCTIONS_WORKER_RUNTIME": "node",
    "AzureWebJobsFeatureFlags": "EnableWorkerIndexing",
    "FORM_RECOGNIZER_API_KEY": "22651ab54aad4a289c6988b743fcd1e0",
    "FORM_RECOGNIZER_ENDPOINT": "https://eastus.api.cognitive.microsoft.com/",
    "FORM_RECOGNIZER_CUSTOM_MODEL_ID": "workingplan-last-test-for-today"
  }
}

And also the host json file:

{
  "version": "2.0",  
  "logging": {
    "applicationInsights": {
      "samplingSettings": {
        "isEnabled": true,
        "excludedTypes": "Request"
      }
    }
  },
  "extensionBundle": {
    "id": "Microsoft.Azure.Functions.ExtensionBundle",
    "version": "[3.*, 4.0.0)"
  }
}

navba-MSFT 24,910 Reputation points Microsoft Employee

2023-10-26T10:46:27.4+00:00
@Benjamin Koubik Thanks for sharing the snippet and clarifying your ask. I used the same sample which you have shared and I was able to get this to work at my end.

See the below screenshot where we can see the HTTPTrigger url post deployment:

I was also able to see this in the HTTP Trigger function in the portal:

Action Plan:
In your VS code terminal run the below commands one by one:

npm install @azure/ai-form-recognizer

npm install @azure/functions

Then publish it using the func cli as: func azure functionapp publish FUNC_NAME

Hope this helps.

**

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Benjamin Koubik 50 Reputation points

2023-10-26T11:12:03.6733333+00:00

@navba-MSFT Thanks for your help. Unfortunately it didn't work that way either. I don't get an HTTP trigger displayed after successfully deploying the function, see screenshot
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Accepted answer

navba-MSFT 24,910 Reputation points Microsoft Employee

2023-10-26T12:01:17.7166667+00:00
@Benjamin Koubik Thanks for your reply. Lets take a step back and do this in the same way I did at my end from scratch. Hopefully that might help.

We will do it using a new function app project right from scratch. Follow the below steps one by one:

Create a new empty folder and open this folder using VS code.

Then open the New terminal in VS code and navigate to this folder.

Run the func init command, as follows, to create a functions project in a folder named LocalFunctionProj:

func init LocalFunctionProj --model V4

You're then prompted to choose a worker runtime and a language - choose Node for the first and JavaScript for the second.

Navigate into the project folder:

cd LocalFunctionProj

Add a function to your project by using the following command:

func new

Choose the template for "HTTP trigger". You can keep the default name (httpTrigger) or give it a new name (HttpExample).

Replace the existing content with below in your local.settings.json.

{ "IsEncrypted": false, "Values": { "AzureWebJobsStorage": "DefaultEndpointsProtocol=https;AccountName=aidocumentanalysing;AccountKey=8DOb+NvimZg1b9GOCi1IeUTT7ZSq8fAJkqEXbqx0GOtfhSoAl4LNVvkz3BDIhcsvKu81xurMUqku+AStPfVeLQ==;EndpointSuffix=core.windows.net", "FUNCTIONS_WORKER_RUNTIME": "node", "AzureWebJobsFeatureFlags": "EnableWorkerIndexing", "FORM_RECOGNIZER_API_KEY": "22651ab54aad4a289c6988b743fcd1e0", "FORM_RECOGNIZER_ENDPOINT": "https://eastus.api.cognitive.microsoft.com/", "FORM_RECOGNIZER_CUSTOM_MODEL_ID": "workingplan-last-test-for-today" } }

You can find the function you added in the src/functions directory.

Open the JS file and Add the below code:

const { DocumentAnalysisClient, AzureKeyCredential } = require("@azure/ai-form-recognizer"); const { app } = require('@azure/functions'); app.http('httpTrigger', { methods: ['GET', 'POST'], authLevel: 'anonymous', handler: async (request, context) => { if (request.method === "GET") { return { body: "Hello, world!" }; } const { url } = await request.json(); const client = new DocumentAnalysisClient( process.env.FORM_RECOGNIZER_ENDPOINT, new AzureKeyCredential(process.env.FORM_RECOGNIZER_API_KEY) ); const poller = await client.beginAnalyzeDocument( process.env.FORM_RECOGNIZER_CUSTOM_MODEL_ID, url, { onProgress: ({ status }) => { console.log(`status: ${status}`); }, } ); const { documents: [document], } = await poller.pollUntilDone(); if (!document) { throw new Error("Expected at least one document in the result."); } return { body: JSON.stringify(document.fields) }; } });

In your VS code terminal run the below commands one by one:

npm install @azure/ai-form-recognizer

npm install @azure/functions

Run your function by starting the local Azure Functions runtime host from the LocalFunctionProj folder.

func start

Test and confirm it works locally.

Then you can deploy to your Azure Function using func cli as: func azure functionapp publish FUNC_NAME

Then check if you see the http_trigger getting deployed. Also test from portal.

You should be also able to send the GET verb to this function app and it should show HELLO WORLD message.

** Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Please sign in to rate this answer.

2 people found this answer helpful.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Dennis Aschurov 0 Reputation points

2024-02-23T16:20:10.2233333+00:00

Your post helped me a lot, thank you very much!
I was struggling with publishing my function to the function app using the Azure Vscode extension.

I was following the "Quickstart: Create a JavaScript function in Azure using Visual Studio Code" Article step by step, everything seemed to work perfectly, except for the deployment. Clicking on "deploy to function app..." would execute the deployment process, the files would be pushed successfully, but afterward 0 functions appeared in the function app.

After executing func azure functionapp publish FUNC_NAME in the CLI, the function actually appeared in my function app.

It seems like there might be an issue with the Azure Functions Vscode Extension?

Sivanesan 20 Reputation points

2024-04-04T08:43:35.48+00:00

Hi @navba-MSFT I am having the exact problem in m y python function app. Can you help.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Sven 0 Reputation points

2024-09-20T09:45:54.81+00:00

Resetting .funcignore to the default did the trick for me.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure function is not deployed from VS - No HTTP triggers found

0 additional answers

Your answer