functions-dotnet-migrate-packages-v4-isolated.md

author	mattchenderson
ms.service	azure-functions
ms.topic	include
ms.date	07/31/2023
ms.author	mahender

If you haven't already, update your project to reference the latest stable versions of:

• Microsoft.Azure.Functions.Worker
• Microsoft.Azure.Functions.Worker.Sdk

Depending on the triggers and bindings your app uses, your app might need to reference a different set of packages. The following table shows the replacements for some of the most commonly used extensions:

Scenario	Changes to package references
Timer trigger	Add Microsoft.Azure.Functions.Worker.Extensions.Timer
Storage bindings	Replace Microsoft.Azure.WebJobs.Extensions.Storage with Microsoft.Azure.Functions.Worker.Extensions.Storage.Blobs, Microsoft.Azure.Functions.Worker.Extensions.Storage.Queues, and Microsoft.Azure.Functions.Worker.Extensions.Tables
Blob bindings	Replace references to Microsoft.Azure.WebJobs.Extensions.Storage.Blobs with the latest version of Microsoft.Azure.Functions.Worker.Extensions.Storage.Blobs
Queue bindings	Replace references to Microsoft.Azure.WebJobs.Extensions.Storage.Queues with the latest version of Microsoft.Azure.Functions.Worker.Extensions.Storage.Queues
Table bindings	Replace references to Microsoft.Azure.WebJobs.Extensions.Tables with the latest version of Microsoft.Azure.Functions.Worker.Extensions.Tables
Cosmos DB bindings	Replace references to Microsoft.Azure.WebJobs.Extensions.CosmosDB and/or Microsoft.Azure.WebJobs.Extensions.DocumentDB with the latest version of Microsoft.Azure.Functions.Worker.Extensions.CosmosDB
Service Bus bindings	Replace references to Microsoft.Azure.WebJobs.Extensions.ServiceBus with the latest version of Microsoft.Azure.Functions.Worker.Extensions.ServiceBus
Event Hubs bindings	Replace references to Microsoft.Azure.WebJobs.Extensions.EventHubs with the latest version of Microsoft.Azure.Functions.Worker.Extensions.EventHubs
Event Grid bindings	Replace references to Microsoft.Azure.WebJobs.Extensions.EventGrid with the latest version of Microsoft.Azure.Functions.Worker.Extensions.EventGrid
SignalR Service bindings	Replace references to Microsoft.Azure.WebJobs.Extensions.SignalRService with the latest version of Microsoft.Azure.Functions.Worker.Extensions.SignalRService
Durable Functions	Replace references to Microsoft.Azure.WebJobs.Extensions.DurableTask with the latest version of Microsoft.Azure.Functions.Worker.Extensions.DurableTask
Durable Functions (SQL storage provider)	Replace references to Microsoft.DurableTask.SqlServer.AzureFunctions with the latest version of Microsoft.Azure.Functions.Worker.Extensions.DurableTask.SqlServer
Durable Functions (Netherite storage provider)	Replace references to Microsoft.Azure.DurableTask.Netherite.AzureFunctions with the latest version of Microsoft.Azure.Functions.Worker.Extensions.DurableTask.Netherite
SendGrid bindings	Replace references to Microsoft.Azure.WebJobs.Extensions.SendGrid with the latest version of Microsoft.Azure.Functions.Worker.Extensions.SendGrid
Kafka bindings	Replace references to Microsoft.Azure.WebJobs.Extensions.Kafka with the latest version of Microsoft.Azure.Functions.Worker.Extensions.Kafka
RabbitMQ bindings	Replace references to Microsoft.Azure.WebJobs.Extensions.RabbitMQ with the latest version of Microsoft.Azure.Functions.Worker.Extensions.RabbitMQ
Dependency injection and startup config	Remove references to Microsoft.Azure.Functions.Extensions (The isolated worker model provides this functionality by default.)

See Supported bindings for a complete list of extensions to consider, and consult each extension's documentation for full installation instructions for the isolated process model. Be sure to install the latest stable version of any packages you are targeting.

Tip

Any changes to extension versions during this process might require you to update your host.json file as well. Be sure to read the documentation of each extension that you use. For example, the Service Bus extension has breaking changes in the structure between versions 4.x and 5.x. For more information, see Azure Service Bus bindings for Azure Functions.

Your isolated worker model application should not reference any packages in the Microsoft.Azure.WebJobs.* namespaces or Microsoft.Azure.Functions.Extensions. If you have any remaining references to these, they should be removed.

Tip

Your app might also depend on Azure SDK types, either as part of your triggers and bindings or as a standalone dependency. You should take this opportunity to update these as well. The latest versions of the Functions extensions work with the latest versions of the Azure SDK for .NET, almost all of the packages for which are the form Azure.*.