General availability support for Java Message Service (JMS) 2.0 API on Azure Service Bus Premium

Lift and shift Java and Spring workloads to Azure Service Bus with configuration only code changes. This functionality enables you to seamlessly migrate away from on-premises message brokers if you are using the JMS 2.0 API to communicate with these message brokers. You can also utilize existing EAI connectors to talk to Azure Service Bus just as you would do with any other JMS provider (MQ broker).

As customers move away from their on-premises setup, Azure Service Bus can act as an on-ramp to Azure allowing them to further leverage the cloud native capabilities and deeper integrations with Azure’s PaaS offerings to further modernize their stack.

To learn more, refer to the below:

• Announcement on TechCommunity
• Use Java Message Service 2.0 API with Azure Service Bus Premium - Azure Service Bus | Microsoft Docs
• Migrate Java Message Service (JMS) applications from Apache ActiveMQ to Azure Service Bus - Azure Service Bus | Microsoft Docs
• JMS Developer guide for Azure Service Bus | Microsoft Docs