SqlOrchestrationService is not visible when referencing Microsoft.Azure.Functions.Worker.Extensions.DurableTask.SqlServer

I'm working on migrating a .NET 6 function application from using the in-proc to isolated model of hosting.

The deployed version of the application does not run with DDL permissions to the database, so cannot run the migrations itself on start-up. What we have historically done is add a CI/CD deployment step that applies any outstanding migrations, just prior to deploying the application:

await new SqlOrchestrationService(new SqlOrchestrationServiceSettings(connectionString))
    .CreateAsync();

This works fine when using a reference to Microsoft.DurableTask.SqlServer.AzureFunctions, however when I switch to Microsoft.Azure.Functions.Worker.Extensions.DurableTask.SqlServer, the DurableTask namespace and associated types are no longer resolvable. Both versions of the assembly are the same version (1.2.1):

It's possible I might be doing something wrong here, but I'm seeing minor differences in the schemas generated between the two, so I'd really like to make sure I'm using the correct SqlOrchestrationService to configure the schema.

Curiously, when I look at the assembly in the nuget package using ILSpy, I don't see any types in it, so I have no idea how the migration code is actually executed when I allow it to configure the schema on my local machine (which it can do successfully!)

Start by comparing the Microsoft.DurableTask.SqlServer.AzureFunctions and Microsoft.Azure.Functions.Worker.Extensions.DurableTask.SqlServer NuGet assemblies, including their exported types and dependencies. Trace how local schema migration is invoked and confirm which package should expose SqlOrchestrationService; done when the correct type is publicly resolvable and its generated schema matches the intended provider.