OS: macOS M1 Repro Steps: Create a Python project with HTTP Trigger function and open it in VS Code. Create a Python Linux Consumption function app. Deploy the Python project to the above function app. Check whether there is a HTTP Trigger function under the "Functions" node in VSCode or in the Azure Portal. Expect: There is a HTTP Trigger function under the "Functions" node both in VSCode and Azure Portal. Actual: There is no function under the "Functions" node both in VSCode and Azure Portal. But the Function when run locally with Azure Function core tools works fine, with the HTTP Triggers.

Azure Function not showing HTTP Triggers when deployed.

Rishab Kumar 0 MVP

OS: macOS M1

Repro Steps:

Create a Python project with HTTP Trigger function and open it in VS Code.
Create a Python Linux Consumption function app.
Deploy the Python project to the above function app.
Check whether there is a HTTP Trigger function under the "Functions" node in VSCode or in the Azure Portal.

Expect: There is a HTTP Trigger function under the "Functions" node both in VSCode and Azure Portal.

Actual: There is no function under the "Functions" node both in VSCode and Azure Portal.
But the Function when run locally with Azure Function core tools works fine, with the HTTP Triggers.

Screenshot 2024-07-05 at 11.44.43 AM

Screenshot 2024-07-05 at 11.41.35 AM

navba-MSFT 19,735 Reputation points Microsoft Employee

2024-07-08T03:23:17.9933333+00:00
@Rishab Kumar 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 are not able to see the HTTP Triggers in Azure.

Please follow the below action plan in order:

.

Plan 1:

Navigate to your Azure Function App in the Azure portal. Select the Enviornment Variables Under the App settings --> Delete the app setting - WEBSITE_RUN_FROM_PACKAGE. Try deploying your function app again and check if that helps.

.

Plan 2:

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.

.

Plan 3: 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.

.
Plan 4:

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>

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.

.
.
.
If none of the above plan helps, please let me know. I will share the next steps with you.

Share via

Azure Function not showing HTTP Triggers when deployed.