After Azure upgrade from inprocess to Isolated newly added function is not visible in the portal

Hello Jinugu, Manasa,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that after Azure upgrade from in process to Isolated newly added function is not visible in the portal.

Best advice is to follow the steps below:

1. Publish the isolated app and ensure the output has your .exe, functions.metadata, and function folders: dotnet publish -c Release -o publish (See the .NET isolated guide for project structure and deployment expectations). - https://learn.microsoft.com/en-us/azure/azure-functions/dotnet-isolated-process-guide
2. Deploy only the publish output in Zip/push contents of /publish (not the repo root or /bin) to App Service/Kudu: ``cd publish && zip -r app.zip .  &&  curl -X POST -u <user:pwd> https://<app>.scm.azurewebsites.net/api/zipdeploy -T app.zip(App Service/Kudu ZIP deploy requires packaging the publish folder only). - https://learn.microsoft.com/en-us/azure/app-service/deploy-zip, https://learn.microsoft.com/en-us/azure/azure-functions/deployment-zip-push
3. Use the isolated project shape: Your .csproj must target .NET and Functions v4 with an executable output:

      <Project Sdk="Microsoft.NET.Sdk.Worker">
        <PropertyGroup><TargetFramework>net8.0</TargetFramework><AzureFunctionsVersion>v4</AzureFunctionsVersion><OutputType>Exe</OutputType></PropertyGroup>
      </Project>
   

   It's required by the .NET isolated worker model. - https://learn.microsoft.com/en-us/azure/azure-functions/dotnet-isolated-process-guide
4. Remove in‑process packages and use Worker packages instead: <ItemGroup>   <PackageReference Include="Microsoft.Azure.Functions.Worker" />   <PackageReference Include="Microsoft.Azure.Functions.Worker.Sdk" OutputItemType="Analyzer" /> </ItemGroup> Do not use Microsoft.NET.Sdk.Functions/Microsoft.Azure.WebJobs.* in isolated. - https://learn.microsoft.com/en-us/azure/azure-functions/dotnet-isolated-in-process-differences, https://learn.microsoft.com/en-us/azure/azure-functions/dotnet-isolated-process-guide
5. Set the app setting to isolated and align with the runtime versions: FUNCTIONS_WORKER_RUNTIME=dotnet-isolated FUNCTIONS_EXTENSION_VERSION=~4 Mismatch triggers event is AZFD0013 making sure settings and payload agree. https://learn.microsoft.com/en-us/azure/azure-functions/errors-diagnostics/diagnostic-events/azfd0013, https://learn.microsoft.com/en-us/azure/azure-functions/errors-diagnostics/diagnostic-events/azfd0013
6. Use Kudu VFS to check /site/wwwroot if the portal doesn’t list files: https://<app>.scm.azurewebsites.net/api/vfs/site/wwwroot/ (Kudu/Advanced Tools expose VFS and Zip Push Deploy endpoints for validation) - https://learn.microsoft.com/en-us/azure/app-service/resources-kudu, https://github.com/projectkudu/kudu/wiki/REST-API
7. The deployed payload must include host/config and generated worker metadata (e.g., functions.metadata and worker.config.json) produced by the isolated build; regenerate by rebuilding if missing. (This prevents “invalid worker runtime metadata” warnings and undiscovered functions). - https://learn.microsoft.com/en-us/azure/azure-functions/errors-diagnostics/diagnostic-events/azfd0013
8. In Azure Pipelines, point the deploy task to the publish folder/zip: - task: AzureFunctionApp@2   inputs: { appName: '<func-app>', package: '$(Build.ArtifactStagingDirectory)/publish/**/*.zip' } (Use the v2 task and publish/download artifacts correctly; wrong root causes “0 functions found”). - https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/azure-function-app-v2?view=azure-pipelines, https://learn.microsoft.com/en-us/azure/devops/pipelines/artifacts/pipeline-artifacts?view=azure-devops

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.