Fix: “We Were Not Able to Load Some Functions” Error in .NET Isolated Azure Function Deployment

Hello and welcome to my blog! 👋😊 If you’re deploying a .NET Isolated Azure Function App using GitHub Actions and running into unexpected deployment errors — don’t worry, you’re not alone. I recently faced a similar issue while pushing my .NET isolated function app from GitHub to the Azure Portal, and here’s how I tackled it successfully.

❗ The Issue

While deploying my function app to Azure, I encountered below recurring error message. Despite multiple restarts, the issue persisted, and the function app wasn’t appearing correctly in the portal.

🧠 Root Cause Analysis

To investigate further, I accessed the Kudu Console (Advanced Tools) for my Azure Function App. Here’s what I discovered:

• Inside the wwwroot folder, the .azurefunctions directory was missing—a critical part of the build.

• The app setting WEBSITE_RUN_FROM_PACKAGE had conflicting values:
• In App Settings (Kudu): WEBSITE_RUN_FROM_PACKAGE was set to 0
• In Environment Variables: It was set to 1

This mismatch was preventing the function app from deploying and running correctly. Ideally, WEBSITE_RUN_FROM_PACKAGE should be set to 1 to ensure Azure pulls the app package correctly during every deployment.

🛠️ Step-by-Step Troubleshooting and Fix

Here’s the exact workaround that helped me resolve the issue:

✅ Step 1: Clean Kudu Deployment Files

I accessed the Kudu console and cleared all previous deployment files to start fresh.

✅ Step 2: Correct App Settings

I navigated to Application Settings in Azure and:

• Deleted the existing WEBSITE_RUN_FROM_PACKAGE setting.
• Re-added it with the correct value: WEBSITE_RUN_FROM_PACKAGE = 1

✅ Step 3: Include Hidden Files in GitHub Workflow

In my GitHub Actions workflow, I modified the deployment step to include hidden files (like .azurefunctions) by adding the flag include-hidden-files: true:

- name: Upload artifacts
 uses: actions/upload-artifact@v4
 with:
 …
 include-hidden-files: true
 …

This ensures that all required hidden folders are packaged and deployed properly.

🎉 Result: Successful Deployment!

After implementing these changes, I redeployed the function app from GitHub — and voilà! 😄
 The Azure Function App was deployed successfully, appeared in the portal, and passed all functionality tests.

🔍 Key Takeaways

• Always verify your WEBSITE_RUN_FROM_PACKAGE setting during deployment.
• Use the Kudu Console to inspect what’s missing inside the wwwroot folder.
• Make sure to include hidden files when uploading artifacts in GitHub Actions for .NET Isolated Azure Functions.

Thanks for stopping by! Your visit means a lot. Please Follow me😊 Stay tuned for more content. Exciting stuff coming your way soon! 🚀 #StayTuned. Also, visit on riovTech.

🔗 Follow Me for More Updates:

🌐 Blog: https://riovtech.com/

📱 Instagram : https://www.instagram.com/_riovtech_/

🐦 Twitter: https://x.com/riotech576