Azure Function Not Visible After Deployment from VS Code to Azure Portal

Harshal Jain 0 Reputation points
2025-04-02T20:06:02.5433333+00:00

Issue:

I have developed an Azure Function App (Blob Trigger) in VS Code, and it works perfectly when running locally using func start. However, after deploying it to Azure using VS Code, I cannot find the function in the Azure Portal, and the associated files
Environment Details:

OS: macOS

  • Azure Functions Core Tools Version: 4.0.7030
  • Python Version: 3.10
  • Function App Runtime: Python
  • Trigger Type: Blob Storage
  • Deployment Method: VS Code Azure Extension(used the button to deploy Screenshot 2025-04-03 at 1.34.44 AM

below are some images from the portal and the VScode for the observation.

unable to see functions
Screenshot 2025-04-03 at 1.27.45 AM

only this file appears.Screenshot 2025-04-03 at 1.27.57 AM

these are two local function have verified their execution locally .Screenshot 2025-04-03 at 1.26.24 AM

Screenshot 2025-04-03 at 1.26.36 AM

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
5,706 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Ranashekar Guda 1,265 Reputation points Microsoft External Staff
    2025-04-07T12:28:17.9133333+00:00

    Hello @Harshal Jain,
    Several common build issues can prevent Azure Functions, like your Blob Trigger function, from being found after deployment. To troubleshoot, start by ensuring that the agent pool used for deployment is running on Ubuntu. This is essential for ensuring that packages are restored properly during the build step.

    Next, check if your function app is located at the root of the source repository. If not, ensure the pip install step references the correct path for creating the .python_packages folder, keeping in mind that the path is case-sensitive.

    Additionally, verify that the deployment package can be loaded into /home/site/wwwroot, which is usually managed by the ArchiveFiles task. If these steps don’t resolve the issue, review the deployment logs for any errors or warnings that could provide more insights into what went wrong.

    For further clarification, please refer to the following documentations: Document1, Document2

    I hope this helps resolve your issue. Feel free to reach out if you have further concerns.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.