This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 49%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
I have created a function app with NodeJS as runtime stack, I then created a project and function within VSCode (I have Installed all the necessary extensions and tools) and deployed it using the Azure: Deploy To Function App from command palette- the deployment is successful, but i do not see the function listed within the function app. moreover now I've also lost the option for creating a function from the portal.
I have also restarted/refreshed the function app multiple times to see if theres a delay in appearing on the portal, but doesnt help
Please can someone suggest what might have i been doing wrong?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 77%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
Thank you for posting your concern on Microsoft Q&A.
Could you please check the private message and provide the required details for troubleshooting the issue further.
Here is the reference link on how to access & data retention policy of private messages in Microsoft Q&A.
Just checking in—if the issue still persists, please respond via private message so we can assist you further.
We recently had a discussion regarding deploying Azure Functions using VS Code, and the issue was successfully resolved for the original poster after carefully following a set of steps. The resolution involved ensuring the correct application settings were updated and verifying the deployment process end-to-end.
You can find the full discussion and solution here: Error deploying Azure Function from VS Code – no HTTP Trigger found
Since your runtime stack is Node.js, please ensure that:
The function is using the correct folder structure (function.json is present in the function folder).
The correct runtime version is selected (matching your local development version).
Application settings like WEBSITE_NODE_DEFAULT_VERSION are configured appropriately in the Azure portal.
Here is the official Microsoft documentation for reference: Azure Functions Node.js developer reference
If you’ve already verified these and the issue still persists, please respond via private message with the requested details. We're here to help you resolve this.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
It sounds like you've encountered a common issue when deploying Azure Functions using Node.js from Visual Studio Code. If your deployment completes successfully but the function doesn’t show up in the Azure portal, here are several things to check:
Verify the Correct Folder Was Deployed
The function app root folder must contain a host.json file and subfolders for each function. Each function should be in its own folder with at least a function.json and an entry script like index.js. A common mistake is deploying the wrong folder level (e.g., a subfolder or parent of the actual function app root).
Ensure function.json and host.json Are Properly Configured
Every function must have a function.json file, which tells Azure how to trigger the function. The function.json should correctly point to the script file (e.g., "scriptFile": "index.js"). The host.json file should not have a "functions" array unless you're explicitly listing functions to load; if you do use it, make sure all function names are listed.
Check the Node.js Runtime Version
In the Azure Portal, go to your Function App > Configuration > General Settings and confirm the Node.js version matches what you’re using locally. If there is a mismatch, Azure may fail to run the function.
Look at Deployment Logs
After deploying from VSCode, review the output log. Also, in the Azure Portal, go to your Function App > Development Tools > Advanced Tools (Kudu) > Debug Console > site/wwwroot. This allows you to inspect whether the correct files and folders were deployed.
Understand Portal Behavior
When you deploy a function app via code (like from VSCode), the portal disables the “Create function” button. This is expected because the code is managed externally. The function should still appear in the list if it was deployed correctly.
Try a Clean Redeploy
If you're unsure whether the previous deployment was clean, you can manually delete all contents in site/wwwroot through Kudu and then redeploy using VSCode.
Please "Accept answer" if this help.
Glad to hear you’ve resolved the issue!
Resolution:
Moved the function definition to index.js using the correct app.http(...) syntax.
Added the environment variable AzureWebJobsFeatureFlags=EnableWorkerIndexing.
This helped the function appear in the Azure Portal. Thanks for sharing — this will definitely help others facing a similar issue!
Hi @Sai Prabhu Naveen Parimi @Anonymous Thanks for providing your answers. I was able to post the function on the Azure Portal.
Quick Update on what I did:
Initialized my function definition correctly in index.js file, I was previously doing this in my functionName.js file.
app.http('functionName', {
methods: ['POST'],
authLevel: 'anonymous',
handler: functionName,
}
And added an environment variable for this setting AzureWebJobsFeatureFlags=EnableWorkerIndexing.
Apparently, by doing this the function deployed and posted to the portal.