An Azure service that provides an event-driven serverless compute platform.
Hi @Zaheer. Sadaf (Enterprise Services) , Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
Here are a few things you could check to troubleshoot this issue:
- Verify the Folder Structure: Ensure that the folder structure of your function app follows the language-specific recommendations. Each function should typically have its own folder with a
function.jsonfile. - Deployment Method: If you deployed using Visual Studio Code, confirm that you're using the latest Azure Function Runtime Core Tools. Older versions may cause issues with deployment.
- Check for WEBSITE_RUN_FROM_PACKAGE: If the
WEBSITE_RUN_FROM_PACKAGEsetting is enabled, it means thewwwrootfolder is read-only. You would need to perform a full deployment instead of trying to add functions individually. - RBAC Permissions: Make sure you have the right RBAC permissions to deploy functions.
- Storage Account Connectivity: Verify that your function app has good connectivity to the storage account it uses. You can use the Network Troubleshooter from the Diagnose and Solve Problems blade in the Azure portal to check this.
- Function App Status: Ensure the function app is up and running. If it’s not, you may see messages indicating that the runtime is unreachable.
- Check Environment Variables: Make sure that any necessary application settings (like connection strings) are present in the Azure portal under the Application Settings for your function app.
If you’ve double-checked everything and still can’t see your functions, it might help to get some additional information. Here are a few follow-up questions you could consider:
- What type of functions are you trying to deploy (HTTP, timer, etc.)?
- Have you confirmed the function app status—does it show any warning or error messages?
- Can you check the logs in the Azure portal? Are there any specific error messages showing there?
- Did you deploy the functions to an existing Function App, or did you create a new one for this deployment?
- Are you using any specific bindings or triggers that might require additional configuration?