An Azure event routing service designed for high availability, consistent performance, and dynamic scale.
Hi @Mengran Bi
Thank you for your question.
Based on the architecture you've shared:
Azure IoT Hub → Azure Event Hubs → Python Azure Functions → PostgreSQL
the retirement notice for the legacy Azure Service Bus SDKs does not appear to impact your solution.
To address your questions:
- Does this retirement affect Python Azure Functions using Event Hub triggers? No. The retirement announcement is specific to the legacy .NET (
WindowsAzure.ServiceBus,Microsoft.Azure.ServiceBus) and Java (com.microsoft.azure.servicebus) Azure Service Bus SDKs. Python Azure Functions using Event Hub triggers are not affected by this SDK retirement. - Is there any SDK or Azure Functions extension that needs to be upgraded? If your Function App is already running on a supported Azure Functions runtime and is using the current Event Hubs trigger/binding and supported Python SDKs, no additional action is required specifically because of this retirement notice.
- Can the notification be safely ignored if we're already using the current Python Event Hubs libraries and Azure Functions runtime? Yes. If your application does not reference any of the retired legacy .NET or Java Service Bus SDKs and you're already using the current Python Event Hubs libraries with a supported Azure Functions runtime, then this retirement notice does not require any changes to your Event Hubs implementation.
I hope this helps. Please let us know if you have any further questions.