Functions is not appearing in the function app

Hi @Sabyasachi Mohapatra ,

This usually caused by how the Functions runtime is detecting functions, or by portal “add/edit” restrictions.

Here are the most relevant things to check based on the troubleshooting guidance:

1. Make sure the function folder structure matches the runtime expectations

For Azure Functions to detect functions, the folder structure in your deployed package needs to follow the language-specific folder structure recommendations (what the runtime looks for to find your function(s)).

If the structure is slightly off, deployment can look “successful” while the Functions list remains empty.

• Verify your deployed artifact has the function folders in the correct place (and with the expected function.json location per runtime/language conventions).

2. Check whether you deployed using WEBSITE_RUN_FROM_PACKAGE (read-only wwwroot)

If WEBSITE_RUN_FROM_PACKAGE is enabled, the wwwroot folder becomes read-only. In that scenario, you generally can’t “add” functions after the fact from the portal—your functions have to come from the deployment package.

3. Check your Function App settings for WEBSITE_RUN_FROM_PACKAGE.

• If it’s enabled, ensure your pipeline is doing a full deployment including the functions content (not relying on post-deploy filesystem writes).
• Check whether deployment slots are enabled (portal may be read-only)

When deployment slots are enabled, the Function App may be put into a read-only mode in the portal, which prevents adding new functions from the portal UI.

• Verify whether you’re using deployment slots and what mode the portal is showing for the app.

4. Verify storage connectivity (common cause of detection/behavior issues)

If the Function App can’t properly connect to its associated Storage account, function discovery/bindings and runtime operations can be impacted.

• Use the Network Troubleshooter in Diagnose and solve problems to validate storage connectivity.

5. If keys/system keys aren’t in sync, ensure the Functions host is actually running correctly

You mentioned “Host keys are getting created without the system keys.” If the Functions host isn’t starting cleanly or is unreachable, the portal may not populate functions/keys properly even though some files appear in Kudu.

• In the Azure portal, check if the Functions host is healthy (you can use the Diagnose and Solve experience).
• Review Kudu SCM site errors/event log entries (look for reasons the app/host isn’t starting).

6. Consider triggering a trigger sync (if your functions exist but aren’t being registered)

There’s community guidance that sometimes functions don’t appear immediately after deployment; syncing triggers can help in certain cases.

• Use the admin/host/synctriggers endpoint to sync triggers (using the master key) as suggested in community troubleshooting for functions not showing after deployment.

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.