Older control plane APIs in Azure Service Bus, Azure Event Hubs, and Azure Relay will be retired.
Azure Service Bus SDK libraries that don't conform to Azure SDK guidelines will be retired and support will end.
Scale your Azure Service Bus premium namespaces far beyond the current limitations with two new features.
Manage and work with your messages directly in the portal integrated version of Service Bus Explorer.
Configure your Service Bus namespace to require that clients send and receive data with a minimal version of transport layer security (TLS).
Send, receive, and peek messages on queues, topics, and subscriptions.
To enforce stricter security measures, you can now configure your Service Bus namespace to require that clients send and receive data with a minimum version of TLS.
This new capability removes need for workarounds and enables migration of legacy payloads to Azure
You can now send and receive message payloads of up to 100MB in Azure Service Bus premium tier namespaces.
Use existing applications that leverage JMS 2.0 API to talk to Service Bus without any code changes. Only configuration changes are required.
In order to provide Azure Service Bus to more customers irrespective of their application stack and application ecosystem, and in keeping with that vision, we’re announcing feature parity with Java…
Send, receive, and peek from queues, topics, and subscriptions, now from the Azure portal (in preview).
On June 1, 2019, the unit of measure for the Service Bus Standard Base Unit Germany resource GUID will change.
Upgrade existing multi-tenant Service Bus standard namespaces to dedicated premium namespaces by using our new migration tool.
A new AMQP-based package for Azure Service Bus for Node.js is now available.
Effective March 1, 2019, the names for Service Bus Standard Base Unit will change.
Send messages asynchronously between your Go services by using the new preview package for Azure Service Bus.
A package for using Azure Service Bus from Python over AMQP is now available in preview.
Effective January 1, 2019, the names for Azure Service Bus Messaging will change.
Starting on May 1, 2018, you’ll be billed at an hourly rate for Service Bus standard base units and Service Bus premium messaging units.
On May 1, 2018, Azure Service Bus Standard Base Unit and Service Bus Premium Messaging Units will start being billed at an hourly rate from the current daily rate.
Azure Relay Hybrid Connections is generally available.
You can now use the new Azure portal to create and manage Service Bus messaging resources (namespaces, queues, and topics).
To better support a broader array of mission-critical cloud apps, Azure Service Bus Premium messaging is now generally available.
To better support a broader array of mission-critical cloud apps, we’ve introduced Azure Service Bus Premium messaging.
A new learning path for Azure Service Bus has been published.
In July 2014, we announced changes to Service Bus Queues and Topics, with messaging now offered in Basic and Standard tiers. These new tiers provide price flexibility that better accommodate…
Service Bus Basic and Standard tiers provide price flexibility that better accommodate different use cases.