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:
- 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.
- 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/wwwrootdirectory. - 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.
- 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.
- 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: