Known issue with hosting Durable Functions app on preview Flex Consumption plan

[lilyjma]

Problem today

If you deploy a Python Durable Functions app to the Flex Consumption plan (currently in preview), you'll see the following error message on Portal when the app starts:

Microsoft.Extensions.DependencyInjection: Unable to activate type 'DurableTask.Netherite.AzureFunctions.NetheriteProviderFactory'. The following constructors are ambiguous: Void .ctor(Microsoft.Extensions.Options.IOptions1[Microsoft.Azure.WebJobs.Extensions.DurableTask.DurableTaskOptions], Microsoft.Extensions.Logging.ILoggerFactory, Microsoft.Azure.WebJobs.Host.Executors.IHostIdProvider, Microsoft.Azure.WebJobs.INameResolver, System.IServiceProvider, DurableTask.Netherite.ConnectionResolver, Microsoft.Azure.WebJobs.Extensions.DurableTask.IPlatformInformation) Void .ctor(Microsoft.Extensions.Options.IOptions1[Microsoft.Azure.WebJobs.Extensions.DurableTask.DurableTaskOptions], Microsoft.Extensions.Logging.ILoggerFactory, Microsoft.Azure.WebJobs.Extensions.DurableTask.IConnectionStringResolver, Microsoft.Azure.WebJobs.Host.Executors.IHostIdProvider, Microsoft.Azure.WebJobs.INameResolver, Microsoft.Azure.WebJobs.Extensions.DurableTask.IPlatformInformation).

Workaround

1. Remove the reference to Extension Bundles in host.json.
2. Instead of using bundles, manually install the latest stable version of Durable Functions extension to your function app:

func extensions install -p Microsoft.Azure.WebJobs.Extensions.DurableTask -v 2.13.4

This should add an extensions.csproj file to your app directory.

3. If you're using other Azure Functions extensions, you'll also need to manually install them.
4. Go to the extensions.csproj file to make sure that target framework is net8.0 (NOT netcoreapp3.1)
5. Run your app locally to make sure it's working as expected.
6. Redeploy app to Azure and you should no longer see the error message.

Notes

Use this workaround only if you need to deploy your app to the Flex Consumption plan.

We're fixing this issue now so customers can continue to use the Extension Bundles, which is the recommended approach, instead of manually installing extension(s). The reason is bundles will ensure that you're automatically on the latest version of extensions, which often contain critical bug and security fixes. Moreover, all extensions in bundles are tested to ensure that they're compatible with each other, saving you from having to deal with .NET errors when extensions you use are incompatible.