Azure function built on ,.NET 9 isolated model with HTTP trigger, not working app plan free f1

(1) Share

Report

Posted on by Pragya752

234

We have created an azure function with .NET 9 isolated model which has an HTTP trigger. Now , before i selected B1 Basic plan and function was visible properly on function tab on azure when i published from Visual studio but after testinng a few times, i recognized that a consumption cost is very high so switched it back to F1 Free plan but then my function is not visible to me and showing warnings on overview page. I wanted to know what should be my approach, is it due to my isolated model or anything else, is there any alternative approach,that i need to change as charges for basic plan B1 is very high.

Categories:

Dynamics 365 general

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

DAnny3211 11,397 on at

Like (0)

Report
Hi ZazaZaza 👋

Thanks for your question!

The issue you're encountering—where your Azure Function built on .NET 9 isolated model with HTTP trigger is not working or visible after switching to the F1 Free App Service Plan—is likely due to plan limitations or compatibility issues.

✅ Here’s what to check and try:

Plan Compatibility

The F1 Free plan has limited resources and may not fully support newer runtime stacks like .NET 9 isolated model.

Consider switching back to B1 Basic or a higher-tier plan to ensure full functionality.

Function Runtime Errors

The error message “We were not able to load some functions…” suggests that the function app failed to initialize properly.

Check the Function App logs and Application Insights for detailed error messages.

Stack Settings Validation

Go to General Settings > Stack Settings and confirm that the runtime stack is correctly set to .NET 9 (Isolated).

If .NET 9 is not officially supported in the portal, you may need to manually configure it via deployment settings or switch to a supported version.

Refresh and Redeploy

Try refreshing the portal and redeploying the function.

Ensure your deployment includes all necessary configuration files (e.g., host.json, local.settings.json).

💡 Tip: The Free plan is great for testing, but for production or advanced features, a Basic or Standard plan is recommended.

Hope this helps!
✅ Please mark this reply as helpful if it answered your question.
Best regards! 👋

Was this reply helpful? Yes No