Announcement: Azure Active Directory backed authentication for JMS 2.0 API on Azure Service Bus

We are excited to share that Azure Service Bus now supports Azure Active Directory (AAD) based access control for its [JMS 2.0 API](https://learn.microsoft.com/en-us/azure/service-bus-messaging/how-to-use-java-message-service-20). The [azure-servicebus-jms](https://learn.microsoft.com/en-us/azure/service-bus-messaging/how-to-use-java-message-service-20) library has been updated and is readily available on Maven Central. Although AAD-backed authentication has been [an option for Service Bus for some time already](https://techcommunity.microsoft.com/t5/messaging-on-azure-blog/announcing-general-availability-for-azure-active-directory-based/ba-p/837285), until now, users of the JMS 2.0 API still had to resort to local authentication using Shared Access Signatures. This new release brings a welcome change as it allows users to leverage [AAD-based authentication](https://learn.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/overview), using both [system- and user assigned managed identities](https://learn.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/overview#managed-identity-types). To utilize AAD authentication for the JMS 2.0 API on Service Bus instead of SAS based authentication, check the [announcement blogpost ](https://techcommunity.microsoft.com/t5/messaging-on-azure-blog/announcing-azure-active-directory-backed-authentication-for-jms/ba-p/3771409)or the [documentation ](https://learn.microsoft.com/en-us/azure/service-bus-messaging/jms-developer-guide?tabs=JMS-20)to get started. Please note that the JMS 2.0 API is only supported on the premium SKU of Azure Service Bus. * Features * Security