Enforcing TLS 1.2 use with Azure Service Bus

Long-term commitment to supporting protocols and protocol versions is a key expectation customers have from commercial cloud services. Deployed solutions, and especially widely deployed client applications that are often operated outside the original developer’s control, are expected to not become spontaneously broken and cut off from cloud services by protocols being retired.  When it comes to…


Deprecating Service Management support for Azure Service Bus, Relay and Event Hubs

Resource Manager, our next-generation cloud infrastructure stack, is fully replacing the “classic” Service Management model. As a result, Service Management REST APIs and support for Service Bus, Relay, and Event Hubs will be retired on November 1, 2019. As with all changes of this type, we’re providing 12 months’ notice so you have adequate time…


Mixing Standard and Premium Service Bus with VNet Service Endpoints

We recently announced the preview of VNET Service Endpoints for Azure Service Bus. There is an important caveat for this feature: once you enable a service endpoint for Service Bus you cannot mix Standard and Premium tiers on that VNet. Because Service Bus Standard does not support VNets the endpoint will be restricted to Premium…


IP Filtering for Event Hubs and Service Bus

The Azure Messaging team is happy to announce the public preview of IP Filtering for Service Bus Premium and Event Hubs Standard and Dedicated price plans. This feature allows users to control which IPs are accessing their resources. Some characteristics of this feature: Rules allow you to specify accept and reject actions on IP masks…


Azure Event Hubs and Service Bus Virtual Network Service Endpoints in preview

This blog was co-authored by Anitha Adusumilli , Principal Program Manager, Azure Networking and Sumeet Mittal, Program Manager, Azure Networking. Azure Event Hubs, a highly reliable and easily scalable data streaming PaaS offering has been prolific this year with new features such as Availability Zones and a big investment into Open Source with enabling support for Apache…


Azure Service Bus is now offering support for Availability Zones in preview

Azure Availability Zones support for Service Bus Premium provides an industry-leading, financially-backed SLA with fault-isolated locations within an Azure region, providing redundant power, cooling, and networking. This preview begins with Central US, East US 2, and France Central. This feature adds even more resiliency and fault tolerance capabilities to organizations in Finance, Healthcare, Retail, or…


ACS Migration Guide

Previously Service Bus namespaces could contain Queues/Topics, Event Hubs, Relays, or Notification Hubs. You may still be affected by the ACS deprecation if you are using an older namespace. For the scope of the below article, “Service Bus namespaces” includes older, mixed-entity namespaces. Access Control Service PowerShell has been released and is available here. This…


Premium Messaging: High Performance Without Partitions

When Premium Messaging became generally available almost two years ago, by default when creating entities for your namespaces you got two partitions. This was a relatively new concept for some Service Bus customers that were used to one partition. Our reasoning at the time was to improve availability for a nascent service. Well the team…


AMQP transaction support and Send Via are now generally available

For the longtime Service Bus users among our community have enjoyed message transactions with the old client. As of today, transactions are fully supported in our new open source libraries (Java and .Net Standard) or any AMQP library that implements the AMQP 1.0 Standard. If you know the SBMP transaction feature you don’t need to…


Azure Service Bus Deprecating Entity Metrics REST API

We are in the process of deprecating the entity metrics pipeline on May 31, 2018, this was the same API used for the Classic Azure portal and Service Bus Explorer. Also both Event Hubs and Relay services relied on this too. For example the URL looked something like this:  https://management.core.windows.net/73A8B69B-12D4-46A8-9575-9E752E2A1234/services/servicebus/namespaces/mynamespace/queues/myqueue/Metrics The good news is we…