From 701e2644e2389f08af68d8e31d398df022a75013 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andreas=20=C3=96hlund?= Date: Mon, 15 Jun 2026 09:26:04 +0200 Subject: [PATCH 1/3] Guide towards the new package --- README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 41d42fb9..11cf906a 100644 --- a/README.md +++ b/README.md @@ -2,11 +2,13 @@ > **NServiceBus.AzureFunctions.InProcess.ServiceBus has been officially sunsetted.** > Microsoft announced that .NET 8 will be [the last release supporting the in-process hosting model](https://techcommunity.microsoft.com/t5/apps-on-azure-blog/net-on-azure-functions-august-2023-roadmap-update/ba-p/3910098). > We will continue to provide support and address critical fixes during the sunset period, but no new features will be added. -> New projects should use the [isolated worker model](https://docs.particular.net/nservicebus/hosting/azure-functions-service-bus/) instead. Follow [these instructions](https://docs.particular.net/nservicebus/upgrades/azure-functions-service-bus-in-process-isolated-worker) to migrate. +> New projects should use the [isolated worker model](https://docs.particular.net/nservicebus/hosting/azure/functions/) instead. To migrate: +> 1. Update to [`NServiceBus.AzureFunctions.Worker.ServiceBus`](https://docs.particular.net/nservicebus/upgrades/azure-functions-service-bus-in-process-isolated-worker). +> 2. Update to [`NServiceBus.AzureFunctions.AzureServiceBus`](https://docs.particular.net/nservicebus/upgrades/azure-functions-service-bus-isolated-to-azure-functions). # NServiceBus.AzureFunctions.InProcess.ServiceBus -NServiceBus.AzureFunctions.InProcess.ServiceBus supports processing messages in AzureFunctions using the Azure Service Bus trigger and the NServiceBus message pipeline. +NServiceBus.AzureFunctions.InProcess.ServiceBus supports processing messages in Azure Functions using the Azure Service Bus trigger and the NServiceBus message pipeline. It is part of the [Particular Service Platform](https://particular.net/service-platform), which includes [NServiceBus](https://particular.net/nservicebus) and tools to build, monitor, and debug distributed systems. From 3814ae5829fb52626415babe07b0de77f5292c0c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andreas=20=C3=96hlund?= Date: Tue, 16 Jun 2026 09:00:04 +0200 Subject: [PATCH 2/3] Deper explanation of migration --- README.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 11cf906a..5072c636 100644 --- a/README.md +++ b/README.md @@ -2,9 +2,7 @@ > **NServiceBus.AzureFunctions.InProcess.ServiceBus has been officially sunsetted.** > Microsoft announced that .NET 8 will be [the last release supporting the in-process hosting model](https://techcommunity.microsoft.com/t5/apps-on-azure-blog/net-on-azure-functions-august-2023-roadmap-update/ba-p/3910098). > We will continue to provide support and address critical fixes during the sunset period, but no new features will be added. -> New projects should use the [isolated worker model](https://docs.particular.net/nservicebus/hosting/azure/functions/) instead. To migrate: -> 1. Update to [`NServiceBus.AzureFunctions.Worker.ServiceBus`](https://docs.particular.net/nservicebus/upgrades/azure-functions-service-bus-in-process-isolated-worker). -> 2. Update to [`NServiceBus.AzureFunctions.AzureServiceBus`](https://docs.particular.net/nservicebus/upgrades/azure-functions-service-bus-isolated-to-azure-functions). +> New projects should use the [isolated worker model](https://docs.particular.net/nservicebus/hosting/azure/functions/) instead, see [migration instructions below](#migration). # NServiceBus.AzureFunctions.InProcess.ServiceBus @@ -12,6 +10,15 @@ NServiceBus.AzureFunctions.InProcess.ServiceBus supports processing messages in It is part of the [Particular Service Platform](https://particular.net/service-platform), which includes [NServiceBus](https://particular.net/nservicebus) and tools to build, monitor, and debug distributed systems. +## Migration + +To prepare for migration, please review: + +- [Migration instructions from InProcess to the Isolated model](https://docs.particular.net/nservicebus/upgrades/azure-functions-service-bus-in-process-isolated-worker). +- [Migration instructions from the old isolated package to the new multi-endpoint isolated package](https://docs.particular.net/nservicebus/upgrades/azure-functions-service-bus-isolated-to-azure-functions). + +Decide whether going straight to the new package is the best course of action, or whether going straight to the latest multi-endpoint package is acceptable from a migration-risk perspective. + ## Documentation See the [Azure Functions with Azure Service Bus (in-process) documentation](https://docs.particular.net/nservicebus/hosting/azure-functions-service-bus/in-process/) for more details on how to use it. From 4470e83e3a9fb3ecdb40a442ae9246d9f87732b3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andreas=20=C3=96hlund?= Date: Tue, 16 Jun 2026 10:01:01 +0200 Subject: [PATCH 3/3] Update README.md Co-authored-by: Daniel Marbach --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5072c636..1db698e7 100644 --- a/README.md +++ b/README.md @@ -17,7 +17,7 @@ To prepare for migration, please review: - [Migration instructions from InProcess to the Isolated model](https://docs.particular.net/nservicebus/upgrades/azure-functions-service-bus-in-process-isolated-worker). - [Migration instructions from the old isolated package to the new multi-endpoint isolated package](https://docs.particular.net/nservicebus/upgrades/azure-functions-service-bus-isolated-to-azure-functions). -Decide whether going straight to the new package is the best course of action, or whether going straight to the latest multi-endpoint package is acceptable from a migration-risk perspective. +Review both migration guides and decide whether the safer approach is to first migrate from InProcess to the isolated package and then upgrade to the latest multi-endpoint package, or whether a direct migration from InProcess to the latest multi-endpoint package is acceptable. ## Documentation