Problem description I am developing an Azure Functions project in Python (no .NET code at all).
When I run my project locally with Azure Functions Core Tools (4.0.5198) and with Azure Functions Core Tools (4.0.5348) , the host fails to start with the following error:
Azure Functions Core Tools
Core Tools Version: 4.0.5198 Commit hash: N/A (64-bit)
Function Runtime Version: 4.21.1.20667
Skipping 'AzureWebJobsStorage' from local settings as it's already defined in current environment variables.
[2025-09-29T15:14:35.258Z] Error configuring services in an external startup class.
[2025-09-29T15:14:35.259Z] Error configuring services in an external startup class. Microsoft.Extensions.Azure: Could not load file or assembly 'Microsoft.Extensions.Options, Version=8.0.0.0, Culture=neutral, PublicKeyToken=a'. El sistema no puede encontrar el archivo especificado.
[2025-09-29T15:14:35.323Z] A host error has occurred during startup operation '5eb06afb-73f4-4468-b896-e462d844281c'.
[2025-09-29T15:14:35.325Z] Microsoft.Azure.WebJobs.Script: Error configuring services in an external startup class. Microsoft.Extensions.Azure: Could not load file or assembly 'Microsoft.Extensions.Options, Version=8.0.0.0, Culture=neutral, PublicKeyToken=a'. El sistema no puede encontrar el archivo especificado.
Value cannot be null. (Parameter 'provider')
[2025-09-29T15:14:35.342Z] Host startup operation has been canceled
What I have tried
- At fisrt I had Azure Functions Core Tools (4.0.5348) and only the .NET 8.0 runtime installed → the error occurred.
- Then I downgraded to Azure Functions Core Tools (4.0.5198) and installed the .NET 6.0 runtime (so now both 6.0 and 8.0 are installed) → the error still occurs.
- I deleted the
ExtensionBundles folder so Core Tools could re-download the latest bundle (currently Microsoft.Azure.Functions.ExtensionBundle 4.26.2) → same error.
- Confirmed my project structure is correct (
host.json, local.settings.json, requirements.txt, function folders with __init__.py and function.json).
My project was working correctly and suddenly this error appears in local while production is running fine.
Is it a documented problem with a solution?