Azure functions not showing on portal, even though deployment was successful

Question

Hello. I am using an ADO pipeline to deploy my azure function app to a staging slot. Although the deployment is successful, the functions do not load in the portal overview tab and I hit a 404 error when triggering the endpoint. I tried deploying manually using zip deploy and it worked as expected, am just facing the issue with pipeline deployment

Answer 1

Hi @Ayleen Durasno ,

Thanks for the offline Conversation and your patience throughout. Glad the issue is resolved.

I am summarizing the discussion and posting as answer.

Issue:

Upon investigating further, the issue occurred when the Azure DevOps pipeline was deploying the Function App using Run From Package. Although the pipeline deployment completed successfully, the function files were not being properly unpacked into wwwroot, causing the functions to not appear in the Azure Portal and resulting in 404 errors when invoking the endpoints.

Solution:

After switching to zipDeploy deployment method explicitly and disabling WEBSITE_RUN_FROM_PACKAGE, the functions were correctly extracted into wwwroot, became visible in the Azure Portal, and the endpoints started responding as expected.

Steps followed:

1. Specified the deployment method as zipDeploy and enabled remote build

Specified the deploymentMethod as 'zipDeploy' rather than run from package made the functions found as this replicates the manual deployment process and files gets unloaded in wwwroot.

Added below config in the pipeline:

deploymentMethod: zipDeploy  

enableRemoteBuild: true

2. Configured application settings via the pipeline like below

appSettings: '-AzureWebJobsStorage @Microsoft.KeyVault(VaultName=valleyKeyvault;SecretName=AzureWebJobsStorage)'

Example:

           steps:

          - task: AzureFunctionApp@1

            displayName: 'Azure functions app deploy'

            inputs:

              azureSubscription: 'subscription'

              appType: 'functionAppLinux'

              appName: 'app'

              package: '$(Pipeline.Workspace)/drop/$(Build.BuildId).zip'

              appSettings: '-WEBSITE_RUN_FROM_PACKAGE 0'

Hope it helps!

---

Please do not forget to click "Accept the answer” and Yes, this can be beneficial to other community members.

If you have any other questions, let me know in the "comments" and I would be happy to help you.

Answer 2

It sounds like you might be experiencing a runtime issue rather than a deployment issue since the functions are not showing up in the Azure portal after a successful deployment through the ADO pipeline. Here are a few things to check:

1. Storage Account Access: Ensure that your function app has access to the required storage account. If the function runtime can't access the storage, it may not start correctly.
2. Deployment Package: Verify that the deployment package generated by your pipeline is correctly structured and includes all necessary files. The package should be loadable into the /home/site/wwwroot directory.
3. Configuration Settings: Check your function app configuration settings, such as the runtime or language version and any connection strings for triggers. Incorrect settings can prevent the function host from starting.
4. Deployment Logs: Review the logs from your ADO pipeline deployment to see if there are any warnings or errors that might indicate what went wrong during the deployment process.
5. Function Triggers: Ensure that the triggers for your functions are set up correctly and that any external dependencies are accessible and configured properly.

If you've checked these areas and are still encountering issues, you might want to consider running the Azure Function App Diagnostics to help identify any underlying problems.

---

References:

• Resolve common runtime issues after deployment
• Functions not found after deployment