Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.microsoft.com/en-us/answers/questions/5517460/i-cant-upload-my-azure-function below:

I can't upload my azure function

2025-08-08T14:21:45.1333333+00:00

Hello Fabrizio25504

Thanks for reaching out to Microsoft Q&A.

Based on the screenshot provided, we have identified two different errors.

• "No HTTP triggers found" error means your function deployed successfully but Azure can’t find any HTTP-triggered functions in it.
• Missing "Create function" button in Azure Portal happens because Microsoft now encourages using VS Code or the CLI to create functions instead of the portal.

How to Fix "No HTTP Triggers Found" Step-by-Step

Step 1: Check Your Code Make sure your function code follows the right format for Azure Functions Python v2 model. For example, your function_app.py should include proper function and route decorators.

Microsoft Documentation: Azure Functions Python developer guide

Step 2: Check Environment Variables

• Verify your local.settings.json and Azure App Settings contain all required environment variables.
• Use VS Code’s Azure tab to upload any missing settings to the cloud.

Step 3: Verify Dependencies

• Remove unnecessary or conflicting packages like logging from your requirements.txt.
• Make sure all libraries your code uses are listed. Compare by running pip freeze locally.

Step 4: Confirm Function App Settings

• In Azure Portal, check your Function App’s runtime is set to version ~4.
• Ensure the Python version in Azure matches your local environment.

Microsoft Documentation: How to target Azure Functions runtime versions

Step 5: Sync Functions Manually

• Restart your Function App in the portal.
• Send a POST request to the sync triggers endpoint using your function app name and API key to force Azure to detect your functions.

How to Fix Missing "Create Function" Button in Azure Portal

Step 6: Understand Portal Limitations

• Once you deploy functions from tools like VS Code or the CLI, portal editing is disabled on purpose. It’s Microsoft's design, not a bug.
• Portal editing works only for certain languages, originally portal-created functions, and specific plans and OS types.

Microsoft Documentation: Configure function app settings - Development limitations

Step 7: Check Subscription and Runtime Settings

• Free tier subscriptions may not show this option; upgrading to Pay-As-You-Go helps.
• Using .NET isolated model or Linux OS may limit portal features. Choosing Windows and in-process runtime model improves support.

Step 8: Alternative Ways to Develop

• Use VS Code as recommended for full control and better deployment practices.
• If really needed, you can enable limited portal editing by adding the application setting FUNCTION_APP_EDIT_MODE with value readwrite, but this isn’t recommended for production.

Best Practices

• Develop locally with version control and CI/CD pipelines to ensure smooth deployments.
• Keep local and Azure environments consistent.
• Monitor your functions using Application Insights and real-time logs to easily catch errors.

Microsoft Documentation References

1. Development limitations: Configure function app settings
2. Deployment best practices: Code and test Azure Functions locally
3. Troubleshooting deployment: Deployment technologies in Azure Functions
4. Python v2 programming model: Azure Functions Python developer guide

Kindly let us know if the above helps or you need further assistance on this issue.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4