Azure Service Bus SDK libraries retired - Where and how to determine impact?

Question

Azure Service Bus SDK libraries retired - Where and how to determine impact?

JvD 20

I received a notice from Microsoft:

Some Azure Service Bus SDK libraries will be retired on 30 September 2026—migrate to the latest SDKs

You’re receiving this notice because you use one or more of these Azure Service Bus SDK libraries: WindowsAzure.ServiceBus, Microsoft.Azure.ServiceBus, or com.microsoft.azure.servicebus.

So... based on the above we do use some of these tho I'm unsure where or for what. I first want to verify where these are used so I can specifically target someone internally to see about possibly updating things to reflect the newer versions (if applicable).

However in the documentation or the actual email I can't see where it's being used, nor specifically which part (Windows Azure, Microsoft Azure or com.Microsoft Azure). As such I'm unable to really understand the potential impact this may have.

Can anyone point me in the right direction that I might need to go within our tenant to figure out what objects/processes use this bit and thus determine the impact this might have on our business?

0 opmerkingen

2 antwoorden

Uw antwoord

Answer 1

Beste JvD,

De pensioenmelding die je hebt ontvangen betekent dat de legacy Azure Service Bus-clientbibliotheken (WindowsAzure.ServiceBus, Microsoft.Azure.ServiceBus, en com.microsoft.azure.servicebus) na 30 september 2026 niet meer worden ondersteund. Om je impact te begrijpen, is de eerste stap om te identificeren waar deze assemblies in je omgeving worden genoemd. Op Windows kun je je applicatiemappen scannen op DLL's die met de naam Microsoft.Azure.ServiceBus.dll of WindowsAzure.ServiceBus.dll PowerShell (Get-ChildItem -Recurse -Filter *ServiceBus*.dll). Controleer in Java-omgevingen je buildbestanden (pom.xml of gradle.build) op com.microsoft.azure:azure-servicebus.

Bekijk daarnaast je CI/CD-pijplijnen en pakketbeheerders: zoek in .NET naar NuGet-referenties (nuget.exe list Microsoft.Azure.ServiceBus), en in Java, controleer je Maven Central-afhankelijkheden. Als je Azure DevOps of GitHub Actions gebruikt, zoek dan in de repositories naar deze namespaces om te zien waar code QueueClient, TopicClient, of SubscriptionClient. Dit laat zien welke applicaties nog steeds gekoppeld zijn aan de met pensioen gaande SDK's.

Controleer voordat je migreert of je workloads functies gebruiken zoals sessies, transacties of berichtuitstel, aangezien de nieuwe SDK's (Azure.Messaging.ServiceBusvoor .NET en com.azure:azure-messaging-servicebus Java) verschillende API's hebben en codewijzigingen vereisen. Zodra je weet welke applicaties worden getroffen, kun je gerichte updates plannen in plaats van een algemene migratie.

Als mijn antwoord nuttig voor je is, klik dan alsjeblieft op 'Accepteer het antwoord' om mij te steunen.

Dank je,

Domic.

Answer 2

So basically this means:

Identify any servers with connections to something in the Azure cloud (shouldn't be too big a subset).
Verify if those servers still use those SDKs
Verify if those SDKs require updating

I've forwarded this to our application management department as I'm not sure what servers would be applicable for this (tho I have a good estimated guess). Going to wait to hear back from the department to see if this gives them something to go on.

Worst case we can just do nothing and see what fails (tho I'd rather not have to deal with stuff breaking and would really prefer to sort this beforehand).