VS Code and Azure Functions: Zip Deploy Successful but No Functions Found

Question

VS Code and Azure Functions: Zip Deploy Successful but No Functions Found

Timothy J. Harpster 0

I successfully completed a zip deployment for my Azure Functions using VS Code, but no functions are recognized in the Azure portal.

omni app function help 3

Here are the steps taken:

Installed Azure Tools and Azure Functions Core Tools via (Ctrl + Shift + P).

Followed the setup instructions from this answer:

Ran func init <foldername> --model V4 to create the workspace with node_modules (3k+ files) and the necessary JSON files.

Created functions using func new.

npm install @azure/ai-form-recognizer

npm install @azure/functions

Started the function with func start. This just locked up so I CTRL-C

I right click on my function, click deploy to function. The result is what you see in the image.

Despite these steps, the functions were deployed to my function storage account as a zip file, and the files were unzipped in the function app, but they are not recognized (as shown in the image).

Azure setup details:

Two storage accounts: one for the Function App and another for the app.

The functionStorage account has managed identity roles set for reading and writing blobs, tables, and queues.

Using a Flex Consumption plan with a pay-as-you-go subscription.

Environment variables for the Function app: APP_STORAGE_ACCOUNT_KEY, APPLICATIONINSIGHTS_CONNECTION_STRING,

AzureWebJobsFeatureFlags, AzureWebStorage__<funcname>, DEPLOYMENT_STORAGE_CONNECTION_STRING, FUNC_STORAGE_ACCOUNT_KEY, FUNCTIONS_EXTENSION_VERSION are all properly set in both the workspace local settings and Azure Function - Settings - Environment Variables - App Settings (and SQL_CONNECTION STRING in Connection strings).

Node.js version: 22, and the storage account is connected.

After investing four full days into troubleshooting this issue, I still cannot get the functions to be recognized. Assistance would be greatly appreciated.

Timothy J. Harpster 0 Reputation points

2025-05-08T04:33:45.0966667+00:00

Note:

The scm.azurewebsites.net doesn’t work on Linux flex consumption

FUNCTIONS_WORKER_RUNTIME Is invalid for flex consumption
Shireesha Eeraboina 2,825 Reputation points Microsoft External Staff Moderator

2025-05-08T08:23:54.3333333+00:00
Hi Timothy J. Harpster,

To help further investigate why the functions aren’t being recognized after deployment, could you please check and confirm the following:

Have all the local application settings from your local.settings.json been manually added in the Azure Portal > Function App > Configuration? These settings don’t get pushed automatically during deployment and might cause issues if missing.

In the Azure Portal, under Diagnose and Solve Problems > Availability and Performance, there are several built-in detectors available. Could you please run these to check for any errors like functions not being triggered, not found, or other runtime issues?

Could you let us know which hosting plan is being used — Flex Consumption or Standard Consumption? This affects how settings like FUNCTIONS_WORKER_RUNTIME are applied.

Finally, please check the Log Stream for your Function App. If the functions are not being detected correctly, the logs will typically show messages like “0 functions found” or “functions not able to unload”. This can help us confirm if the issue is at the runtime level.

Let us know what you find from these checks, and we’ll be happy to assist further.
Timothy J. Harpster 0 Reputation points

2025-05-08T15:35:01.7266667+00:00
Responses:
local app settings... Yes, i updated my original post, both the Azure portal and local_settings.json and settings.json have the same variables setup

(NOTE i added node_modules entire folder to .funcignore because its too many files and i dont think they are needed in Azure - they are no longer deployed - verified change in blob and function app)

Diagnose and Solve Problems...

Function App runtime encountered the below exceptions:
there are a bunch here is an example - Worker was unable to load entry point 'src/functions/CreateUser.js': Cannot find module 'mssql' Require stack: - /home/site/wwwroot/src/functions/CreateUser.js - /azure-functions-host/workers/node/dist/src/worker-bundle.js - /azure-functions-host/workers/node/dist/src/nodejsWorker.js (note from my image that my files seem to be unzipped into Files/src/functions not the root).

Build type is not detected in the past 30 days for this Function App - Remote Build (Oryx Build) is recommended for Function App.
so I updated settings.json and the function app Environmental variables

{ "azureFunctions.deploySubpath": ".", "azureFunctions.projectSubpath": ".", "azureFunctions.postDeployTask": "npm install (functions)", "azureFunctions.projectLanguage": "JavaScript", "azureFunctions.projectRuntime": "~4", "debug.internalConsoleOptions": "neverOpen", "azureFunctions.projectLanguageModel": 4, "azureFunctions.preDeployTask": "npm prune (functions)", "azureFunctions.scmDoBuildDuringDeployment": true, "azureFunctions.enableOryxBuild": true }

But,

11:22:55 AM omni-func-dev-eus: Following app settings are not supported with this SKU: SCM_DO_BUILD_DURING_DEPLOYMENT, ENABLE_ORYX_BUILD 11:22:55 AM omni-func-dev-eus: The app settings SCM_DO_BUILD_DURING_DEPLOYMENT, ENABLE_ORYX_BUILD are not supported with this SKU. Please remove the listed app settings and then redeploy. 11:22:57 AM omni-func-dev-eus: Deployment failed.

so i removed them from both settings.json and environment variables

Hosting plan... Flex Consumption - Linux - Node.js 22

Log or Log Stream... In VS Code after the run i get a pop up to view Log Stream (also in Function app - Monitoring - Log) there appears to be no activity at all, maybe i don't understand where I'm supposed to view what you are asking for.

In Activity Log
no errors

In Diagnostics - Config & Management
FUNCTIONS_WORKER_RUNTIME and LinuxFxVersion are both empty.

LinuxFxVersion can be set to empty only when FUNCTIONS_WORKER_RUNTIME is configued to dotnet in Linux Consumption.Target Azure Functions Runtime Versions

but setting FUNCTIONS_WORKER_RUNTIME to anything results in warnings/errors.

In Diagnostics - Deployment

Basically this diagnostic doesn 't work for Flex Consumption
Shireesha Eeraboina 2,825 Reputation points Microsoft External Staff Moderator

2025-05-12T13:53:04.0133333+00:00
Hi Timothy J. Harpster,

I apologize for the delay in my response and thank you for your understanding.

Thanks for the update and all the details. Based on what you shared, here are the key points and next steps:

Missing node_modules issue:

Since you're seeing errors like Cannot find module 'mssql', it's likely because the node_modules folder is excluded via .funcignore. Azure Functions doesn’t run npm install automatically in Flex Consumption. So, required dependencies must be included in your deployment package.

Deployment path issue:

Your functions are located under src/functions/, but Azure expects them at the root or correctly configured using FUNCTIONS_WORKER_RUNTIME and scriptFile. Since Flex Consumption doesn’t support FUNCTIONS_WORKER_RUNTIME, the structure must follow default expectations.

Solution:

Run npm install --production locally to reduce file size.

Remove node_modules from .funcignore so it gets deployed.

Move your function files to the root directory or update your function.json to reflect the correct path.

Let us know once these changes are made and if the issue persists—happy to help further.
Timothy Harpster 0 Reputation points

2025-05-12T14:45:42.3833333+00:00

Thanks for the help, i did those things but it didn't resolve my issue.

Here is the solution:

https://learn.microsoft.com/en-us/answers/questions/2264783/vs-code-and-azure-functions-zip-deploy-successful

1 answer

Your answer

Timothy J. Harpster 0 Reputation points

2025-05-08T04:33:45.0966667+00:00

Note:

The scm.azurewebsites.net doesn’t work on Linux flex consumption

FUNCTIONS_WORKER_RUNTIME Is invalid for flex consumption
Shireesha Eeraboina 2,825 Reputation points Microsoft External Staff Moderator

2025-05-08T08:23:54.3333333+00:00

Hi Timothy J. Harpster,

To help further investigate why the functions aren’t being recognized after deployment, could you please check and confirm the following:

Have all the local application settings from your local.settings.json been manually added in the Azure Portal > Function App > Configuration? These settings don’t get pushed automatically during deployment and might cause issues if missing.

In the Azure Portal, under Diagnose and Solve Problems > Availability and Performance, there are several built-in detectors available. Could you please run these to check for any errors like functions not being triggered, not found, or other runtime issues?

Could you let us know which hosting plan is being used — Flex Consumption or Standard Consumption? This affects how settings like FUNCTIONS_WORKER_RUNTIME are applied.

Finally, please check the Log Stream for your Function App. If the functions are not being detected correctly, the logs will typically show messages like “0 functions found” or “functions not able to unload”. This can help us confirm if the issue is at the runtime level.

Let us know what you find from these checks, and we’ll be happy to assist further.
Shireesha Eeraboina 2,825 Reputation points Microsoft External Staff Moderator

2025-05-12T13:53:04.0133333+00:00

Hi Timothy J. Harpster,

I apologize for the delay in my response and thank you for your understanding.

Thanks for the update and all the details. Based on what you shared, here are the key points and next steps:

Missing node_modules issue:

Since you're seeing errors like Cannot find module 'mssql', it's likely because the node_modules folder is excluded via .funcignore. Azure Functions doesn’t run npm install automatically in Flex Consumption. So, required dependencies must be included in your deployment package.

Deployment path issue:

Your functions are located under src/functions/, but Azure expects them at the root or correctly configured using FUNCTIONS_WORKER_RUNTIME and scriptFile. Since Flex Consumption doesn’t support FUNCTIONS_WORKER_RUNTIME, the structure must follow default expectations.

Solution:

Run npm install --production locally to reduce file size.

Remove node_modules from .funcignore so it gets deployed.

Move your function files to the root directory or update your function.json to reflect the correct path.

Let us know once these changes are made and if the issue persists—happy to help further.
Timothy Harpster 0 Reputation points

2025-05-12T14:45:42.3833333+00:00

Thanks for the help, i did those things but it didn't resolve my issue.

Here is the solution:

https://learn.microsoft.com/en-us/answers/questions/2264783/vs-code-and-azure-functions-zip-deploy-successful

Answer 1

Hi Timothy Harpster,

Thank you for your patience and for sharing your feedback on the Q&A community platform. I’m glad to hear that you were able to resolve your issue, and I appreciate you sharing your solution! Your contribution is valuable and can help others in the community facing similar challenges.

As per the Microsoft Q&A community policy, "The question author cannot accept their own answer. They can only accept answers by others"

I’m reposting your solution here so you can mark it as accepted if it resolves your query:

"The Function App issue by setting up resources correctly and enabling managed identity. They used GitHub Actions for deployment and linked the repo through Azure Deployment Center. All necessary environment variables were added. After pushing changes via VS Code with the right .yml config, the deployment worked"

Thank you again for your time and patience throughout this issue.

Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.

Share via

VS Code and Azure Functions: Zip Deploy Successful but No Functions Found

1 answer

Your answer