On 30 September 2026 some Azure services will be retired. Does it impact hosted ABP Framework 7.0 #10899

4 Answer(s)

• 

  0

  AI-Bot created 14 hours ago

  Support Team ABP Agent

  • ABP Framework 7.0 (Hosted or Self-hosted) will not “stop working” just because those legacy Azure Service Bus client libraries are retired, as long as your app is not actually using WindowsAzure.ServiceBus / Microsoft.Azure.ServiceBus at runtime.
  • In ABP’s Azure Service Bus distributed event bus integration, the implementation uses the new Azure SDK package Azure.Messaging.ServiceBus, not Microsoft.Azure.ServiceBus / WindowsAzure.ServiceBus. This can be verified from ABP source (AzureDistributedEventBus.cs) where it directly references Azure.Messaging.ServiceBus types like ServiceBusMessage and ServiceBusReceivedMessage.

  What this means for your case (ABP 7.0 using “Volo DLL”):

  1. If you are using ABP’s Azure Service Bus Event Bus integration (Volo.Abp.EventBus.Azure / Volo.Abp.AzureServiceBus), your runtime dependency is Azure.Messaging.ServiceBus, so the retirement of Microsoft.Azure.ServiceBus / WindowsAzure.ServiceBus should not impact you.
  2. Your application would only be impacted if some other library/package in your solution (custom code or a 3rd-party package) still pulls in and uses Microsoft.Azure.ServiceBus / WindowsAzure.ServiceBus at runtime.

  Recommended action (to be 100% sure):

  • Check your deployed output / NuGet dependency graph:
    • Ensure your solution does not reference Microsoft.Azure.ServiceBus or WindowsAzure.ServiceBus.
    • Ensure the effective runtime client library is Azure.Messaging.ServiceBus.
  • If you find any direct/indirect usage of the retired packages, upgrade/replace that part to Azure.Messaging.ServiceBus (ABP 10 migration is a good time to eliminate legacy dependencies anyway).

  Links (verified):

  • https://abp.io/docs/latest/framework/infrastructure/event-bus/distributed/azure
  • https://abp.io/docs/latest/framework/infrastructure/event-bus/distributed
  • https://abp.io/support/questions/2334

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  ajanur created 13 hours ago

  I found below references <PackageReference Include="Microsoft.Azure.ServiceBus" Version="4.2.1" /> What would be the replacement reference if we want to fix it?

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  AI-Bot created 13 hours ago

  Support Team ABP Agent

  • Replace Microsoft.Azure.ServiceBus with the new Azure SDK package: Azure.Messaging.ServiceBus.

  Update your project file:

  <ItemGroup>
    <PackageReference Include="Azure.Messaging.ServiceBus" Version="7.*" />
  </ItemGroup>
  

  Then remove the old reference:

  <ItemGroup>
    <PackageReference Include="Microsoft.Azure.ServiceBus" Version="4.2.1" />
  </ItemGroup>
  

  Notes (ABP-specific):

  • ABP’s Azure Service Bus integration package (Volo.Abp.AzureServiceBus) already depends on Azure.Messaging.ServiceBus (not Microsoft.Azure.ServiceBus), so in many solutions you can simply remove Microsoft.Azure.ServiceBus if it’s not used by your own code.

  • If you have custom code that uses Microsoft.Azure.ServiceBus types (QueueClient, TopicClient, Message, etc.), you must also migrate that code to the new API surface (ServiceBusClient, ServiceBusSender, ServiceBusProcessor, ServiceBusMessage, etc.).

  Sources:

  • https://abp.io/docs/latest/framework/infrastructure/event-bus/distributed/azure
  • https://www.nuget.org/packages/Azure.Messaging.ServiceBus

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 12 hours ago

  Support Team Fullstack Developer

  Hi,

  Your app won't stop because of ABP. The ABP Azure Service Bus integration (Volo.Abp.AzureServiceBus and Volo.Abp.EventBus.Azure) uses the new Azure.Messaging.ServiceBus SDK. That's the same in 7.0 and 10.0. It doesn't use any of the retired packages.

  The Microsoft.Azure.ServiceBus 4.2.1 reference you found doesn't come from ABP. It's in your own project. It will still work after 30 September, because Microsoft only stops support and updates for these libraries. But it won't get fixes anymore, so it's better to replace it:

  • If nothing in your code uses it, just remove the reference.
  • If your code uses types like QueueClient, TopicClient, MessageReceiver or Message, add the new package and move that code to ServiceBusClient, ServiceBusSender, ServiceBusProcessor and ServiceBusMessage. Changing only the package name won't compile.

  <PackageReference Include="Azure.Messaging.ServiceBus" Version="7.21.0" />
  

  Microsoft's migration guide maps the old API to the new one: https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/MigrationGuide.md

  To make sure no other package brings in the old SDKs, run this in your solution folder and search the output for Microsoft.Azure.ServiceBus and WindowsAzure.ServiceBus:

  dotnet list package --include-transitive
  

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel