Deployed Azure Function Not Visible in Portal

Question

Hi everyone,

I’m new to Azure Functions and I’ve run into an issue I can’t quite figure out.

I deployed my function app successfully (no errors during deployment), but when I check the Azure Portal, I can’t see any of the functions or code.

However, when I use the Visual Studio Code Azure extension, I can clearly see that the files have been deployed and exist in the expected directories.

So currently:

Deployment reports success

No functions/code visible in the Azure Portal

Files are visible via VS Code

Has anyone experienced this before? Could this be related to deployment method (e.g., run-from-package), runtime configuration, or something I might have missed as a first-time Azure user?

Any pointers would be really appreciated. Thanks!

Answer 1

Hi @MU Team ,

Thanks for reaching out to Microsoft Q&A.

Check below steps to troubleshoot the issue:

1. Run From Package:

• If you’ve enabled WEBSITE_RUN_FROM_PACKAGE or the equivalent ZIP deploy/run-from-package setting, your package is mounted read-only, and the portal UI sometimes won’t enumerate the functions.
  • You can temporarily disable run-from-package set it to 0 or remove it, refresh the portal and see if your functions reappear.

2. Application Settings & Host Startup

• Make sure your Function App has all required settings under Configuration =>Application Settings:

  – AzureWebJobsStorage (points at your storage account)  
     – FUNCTIONS_EXTENSION_VERSION (e.g. ~4)  
     – FUNCTIONS_WORKER_RUNTIME (e.g. dotnet, node, python)  

• If any are missing or incorrect, the Functions host may never start—and the portal won’t list your functions.
• Check host startup logs via Application Insights (if enabled) or in Kudu under https://<your-app>.scm.azurewebsites.net/LogFiles/Application or the Debug Console.

3. Kudu & File Locking

• From VS Code you can open the Kudu console https://<your-app>.scm.azurewebsites.net and browse /home/site/wwwroot to confirm the function.json files are in place.
  • If you previously had a deployment lock (ERROR_FILE_IN_USE), make sure the app was stopped or use the AppOffline option so new files actually propagate.

4. Networking:

• If your Function App lives in an Internal Load-Balanced ASE, the portal UI needs outbound access to your .scm.* endpoint and the management APIs.
  • Verify DNS entries, CORS on the .scm endpoint, and that your laptop/VM can resolve those addresses without a custom hosts change or blocked firewall rules.

5. Make sure all the required packages are installed.

Hope this helps!

---

If the resolution was helpful, kindly take a moment to click on and click on Yes for was this answer helpful. And, if you have any further query do let us know

Answer 2

This behavior usually indicates a runtime or configuration issue in the deployed function app rather than a deployment failure.

When deployment succeeds and the files are present under wwwroot (as seen via the Visual Studio Code Azure extension) but no functions appear in the Azure portal, the most common causes are:

1. Function host cannot start correctly
   If the Functions runtime fails to start, the portal cannot enumerate functions, so the Functions list appears empty even though files are deployed. Typical reasons include:
   • Lost access to the storage account configured for the function app.
   • Incorrect or incompatible runtime/language version settings.
   • Invalid or missing trigger connection strings or Key Vault references.
   • External dependencies (databases, messaging systems) causing timeouts during startup.
   • Sync triggers failing, so functions are not loaded.
2. Invalid folder/metadata structure for functions (Node.js example)
   For Node.js apps, the runtime requires a specific folder structure: a host.json at the root and, for each function, a folder containing a function.json. If this structure is missing or incorrect, logs may show errors such as:
   • No HTTP triggers found.
   • No job functions found.
   In that case, the portal will not show any functions even though the files are present.
3. Deployment vs. runtime distinction
   Once files are in wwwroot, deployment method (including run-from-package) is generally no longer the issue. At that point, troubleshooting should focus on runtime behavior: how the host starts, what configuration it reads, and what errors occur during initialization.

Recommended checks and next steps:

1. Verify folder structure and function metadata
   • Confirm that host.json exists at the root of the function app content.
   • Ensure each function has its own folder with a valid function.json file and entry point code.
2. Check for runtime startup errors
   • Use the Azure portal diagnostics for the function app (Diagnose and solve problems) to see if the runtime is failing to start or if sync triggers are failing.
   • Check Application Insights logs (if enabled) for errors like “No functions found” or configuration-related failures.
3. Validate configuration settings
   • Confirm that the storage account connection string is valid and the storage account is accessible.
   • Verify runtime version and language settings are correct for the deployed code.
   • Review any connection strings or Key Vault references used by triggers or startup code.
4. Redeploy or recreate if necessary
   • If configuration issues are hard to isolate, consider creating a new function app with the desired runtime stack and redeploying the same code to see if the functions appear correctly.

If, after these checks, the portal still shows no functions while files are present, focus on the runtime logs and diagnostics to identify which of the common runtime issues (storage, configuration, external dependency, or folder structure) is preventing the host from loading functions.

---

References:

• Quickstart: Create and deploy function code to Azure using Visual Studio Code (programming-language-csharp)
• Quickstart: Create and deploy function code to Azure using Visual Studio Code (programming-language-javascript)
• Quickstart: Create and deploy function code to Azure using Visual Studio Code (programming-language-powershell)
• Quickstart: Create and deploy function code to Azure using Visual Studio Code (programming-language-typescript)
• Azure Functions developer guide (programming-language-powershell)
• Quickstart: Create and deploy function code to Azure using Visual Studio Code (programming-language-other)
• Resolve common runtime issues after deployment
• Troubleshoot Node.js apps in Azure Functions (nodejs-model-v3)