Earlier this year in July, we announced the public preview for Virtual Network Service Endpoints and Firewall rules for both Azure Event Hubs and Azure Service Bus. Today, we’re excited to announce that we are making these capabilities generally available to our customers.
Azure Availability 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…
The two long standing, well known and appreciated Azure Core Services (Azure Service Bus and Azure Event Hubs) just released a preview of an upcoming generally available Geo-disaster recovery feature. With the help of this feature, no client needs to manage Geo-disaster recovery scenarios anymore via code, but can instead rely on the services doing the metadata synchronization between two independent namespaces. At this time, data replication is not yet supported and will be added at a later (post General Availability) point in time.
Azure Service Bus .NET Standard client is generally available. With it comes support for .NET Core and the .NET framework. And as mentioned in an earlier post it also supports Mono/Xamarin for cross-platform application development. This is only the start of greater things to come.
The Azure Service Bus team is extremely excited to announce general availability of our Java client library version 1.0.0. It allows customers to enjoy a solid Java experience with Azure Service Bus as it comes complete with native functionality.
We're happy to announce that Azure Stream Analytics now supports IoT Hub Operations Monitoring giving you an easy way to analyze the operations of your IoT devices.
Azure Service Bus services will be coming soon to new Azure portal. Learn more about some of these upcoming changes.
Halo 5 chose Event Hubs to process billions of events per day in their massive game telemetry platform. Find out why.
Event Hubs is a new capability now commercially available in Microsoft Azure Service Bus that provides a platform-as-a-service solution.
Recently we announced splitting the user experience between Service Bus and Notification Hubs to enable a better experience for Notification Hubs. Now, we are now making the default of NamespaceType to be 'Messaging' to align with the Portal behavior.