Azure Updates - Latest from Azure Charts

Exponential backoff and circuit breaker for Service Bus-triggered Azure Functions

Thu, 14 May 2026 23:04:41 Z

Use exponential backoff and circuit breaker patterns in Azure Functions with Service Bus SDK bindings. Control retry storms, protect dependencies, and degrade gracefully under transient failures. The post Exponential backoff and circuit breaker for Service Bus-triggered Azure Functions appeared first on Azure SDK Blog.
Update Type: Announcement, Services: Service Bus, Azure Functions, Categories: Services

Update: 99.99% uptime for all Azure Service Bus Premium namespaces in Availability Zone regions

Tue, 12 May 2026 18:30:55 Z

Starting May 1, 2026, all Azure Service Bus Premium namespaces deployed in regions with Availability Zone support now qualify for a 99.99% uptime SLA. Premium is the tier customers choose for their most important workloads, and this update brings the SLA
Update Type: Announcement, Services: Service Bus, Categories: Compliance, Services, Regions & Datacenters

Confidential computing for Azure Service Bus Premium

Tue, 12 May 2026 18:30:55 Z

Confidential computing for Azure Service Bus Premium is now generally available in Korea Central and UAE North. This capability enables Service Bus to process messages inside hardware-based trusted execution environments (TEEs), adding protection for data
Update Type: GA, Services: Service Bus, Azure Key Vault, Categories: Features, Security, Services

The problem: All-or-nothing batch processing in Azure Service Bus

Tue, 28 Apr 2026 18:47:37 Z

Azure Functions lets you settle each Service Bus message on its own within a batch. Complete, abandon, dead-letter, or defer messages one by one to avoid duplicate processing and handle errors with precision. The post The problem: All-or-nothing batch processing in Azure Service Bus appeared first on Azure SDK Blog.
Update Type: Announcement, Services: Service Bus, Azure Functions, Categories: Services

How to Troubleshoot Azure Functions Service Bus Trigger Issues

Mon, 27 Apr 2026 06:01:00 Z

Overview Azure Functions integrates with Azure Service Bus via triggers and bindings, allowing you to build event-driven applications that react to queue and topic messages. The Service Bus ...
Update Type: Announcement, Services: Service Bus, Azure Functions, Categories:

Service Bus SBMP Retirement: What BizTalk Server 2020 Customers Need to Know

Tue, 21 Apr 2026 01:02:00 Z

On September 30, 2026, the Azure Service Bus team will retire support for the Service Bus Messaging Protocol (SBMP). This is important BizTalk Server 2020 customers who use the BizTalk Service Bus (S...
Update Type: Announcement, Services: Service Bus, Categories:

Network Security Perimeter for Azure Service Bus

Mon, 06 Apr 2026 18:00:04 Z

Network Security Perimeter (NSP) support for Azure Service Bus is now generally available. Network Security Perimeter creates a logical network boundary around your Service Bus namespaces and other Azure PaaS resources, blocking unauthorized public access
Update Type: GA, Services: Service Bus, Azure Key Vault, Virtual Network, Categories: Security, Services

Take Control of Every Message: Partial Failure Handling for Service Bus Triggers in Azure Functions

Mon, 23 Mar 2026 19:11:00 Z

The Problem: All-or-Nothing Batch Processing in Azure Service Bus Azure Service Bus is one of the most widely used messaging services for building event-driven applications on Azure. When you use A...
Update Type: Announcement, Services: Service Bus, Azure Functions, Categories:

Geo-Replication for Azure Service Bus Premium

Wed, 31 Dec 2025 21:00:35 Z

The Geo-Replication feature for Azure Service Bus in the premium tier is now generally available. The Service Bus Geo-Replication feature is one of the options to insulate Azure Service Bus applications against outages and disasters, providing replication
Update Type: GA, Services: Service Bus, Categories: Features, Services

Service Bus SDK type bindings in Azure Functions for Node.js

Wed, 17 Dec 2025 18:45:01 Z

Azure Functions triggers and bindings enable you to easily integrate event and data sources with function applications. Now that SDK type bindings support for Azure Blob Storage is available, we’re also introducing support for Service Bus SDK type bindi
Update Type: Preview, Services: Service Bus, Azure Functions, Azure Storage, Categories: Services, SDK and Tools

Introducing native Service Bus message publishing from Azure API Management

Mon, 20 Oct 2025 01:22:00 Z

We’re excited to announce a new capability in Azure API Management (APIM) — you can now send messages directly to Azure Service Bus from your APIs using a built-in policy. This enhancement simplifies...
Update Type: Announcement, Services: API Management, Service Bus, Categories: Management

Introducing native Service Bus message publishing from Azure API Management (Preview)

Mon, 20 Oct 2025 01:22:00 Z

We’re excited to announce a preview capability in Azure API Management (APIM) — you can now send messages directly to Azure Service Bus from your APIs using a built-in policy. This enhancement, curre...
Update Type: Preview, Services: API Management, Service Bus, Categories: Management

SDK type bindings in Azure Functions for Azure Blob Storage, Azure Service Bus, Azure Cosmos DB and Azure Event Hubs

Mon, 19 May 2025 17:00:33 Z

Azure Functions triggers and bindings enable you to easily integrate event and data sources with function applications. This feature enables you to use types from service SDKs and frameworks, providing more capability beyond what is currently offered.
Update Type: Preview, Services: Service Bus, Azure Functions, Cosmos DB, Azure Storage, Event Hubs, Categories: Features, Services, SDK and Tools

Introducing granular permissions for Azure Service Bus Explorer

Thu, 29 Aug 2024 20:16:57 Z

When working with the Service Bus Explorer in the Azure portal, you may want to grant different permissions to different users, depending on their role and responsibility. For example, you may want to allow some users to send messages to a queue, but not receive them. Or you may want to restrict access to a specific queue, topic, or subscription, but not the entire namespace. To address this challenge, we are excited to announce granular permissions for Service Bus Explorer. To use granular permissions, you need to use Microsoft Entra authentication, and assign one of the following roles, either on the namespace level or on the entity level. Service Bus Data Owner; Allows to execute both send and receive operations. Service Bus Data Sender; Allows to execute send operations. Service Bus Data Receiver; Allows to execute peek, receive, and purge operations. In case you use a role which doesn’t have send or receive permissions, or you do not have permissions on the specific entity, the unavailable operations will be disabled. Furthermore, a notification will be shown showing which permissions are missing. For more information on using the Service Bus Explorer, you can check our documentation.
Update Type: Announcement, Services: Service Bus, Categories: Services

Logic Apps Standard - Service Bus In-App connector improvements for Peek-lock operations

Mon, 05 Aug 2024 17:00:00 Z

In collaboration with Divya Swarnkar and Aprana Seth. Service Bus In-App connector is bringing new triggers and actions for peek-lock operations. Those changes will allow peek-lock operations in message and queues that don’t require session to be started and completed from any instance of the runtime available in the pool of resources, removing previous requirements for VNET integration and fixed size or role instances, which were needed because of the underlying client SDK used by the connector. The new trigger and actions will be the default operations for peek-lock, but will not impact existing workflows. Read through the next sections to learn more about this update and its impact. New triggers Starting from bundle version 1.81.x, you will find new triggers for messages available in a queue and topic using the peek-lock method: New Actions Starting from bundle version 1.81.x, you will find new actions for managing messages in a queue or topic subscriptions using the peek-lock method are added for queue and topic. What is the difference between this version and the previous version of the connector The new connector actions require details of the repository holding the message (queue name / topic and subscription name) as well as lock token, where the previous item required the message id. This allows the connector to reuse or initialize a client in any instance of the runtime available in the pool of resources. With that, not only the pre-requisites of VNET integration and fixed number of role instance is remov but also the requirement of the same Message Receiver that peeked the message being the workflow that execute all the actions is removed. For more information about the previous connector requirements, check this Tech community post. What is the impact of existing workflows that used the previous version of the Service Bus actions? The previous actions and triggers are marked as internal actions now. This is how Logic Apps indicat
Update Type: Announcement, Services: Logic Apps, Service Bus, Virtual Network, Categories: Services

Public Preview: Geo-Replication for Azure Service Bus Premium

Fri, 05 Jul 2024 00:00:00 Z

The new Geo-Replication feature for Service Bus is now in public preview. This feature allows to replicate data and metadata for a namespace between a primary and a secondary region.

Update Type: Preview, Services: Service Bus, Categories: Features

Announcing public preview of Geo-Replication for Azure Service Bus Premium

Tue, 25 Jun 2024 16:00:00 Z

Today we are excited to announce the public preview of the new Geo-Replication feature for Azure Service Bus in the premium tier. This feature ensures that the metadata and data of a namespace are continuously replicated from a primary region to a secondary region. Moreover, this feature allows promoting a secondary region at any time. The Geo-Replication feature is the latest option to insulate Azure Service Bus applications against outages and disasters. Other options are Geo-Disaster Recovery and Availability Zones. Differentiation There are currently two features that provide Geo-Disaster Recovery in Azure Service Bus for the Premium tier. First, there is Geo-Disaster Recovery (Metadata DR) that just provides replication of metadata. Second, Geo-Replication, which is now in public preview, provides replication of both metadata and data. Neither Geo-Disaster Recovery feature should be confused with Availability Zones. Regardless of if it is Metadata DR or Geo replication, both geo-graphic recovery features provide resilience between Azure regions such as East US and West US. Availability Zones are available on all Service Bus tiers, and support provides resilience within a specific geographic region, such as East US. For a detailed discussion of disaster recovery in Microsoft Azure, see this article. Concepts The Geo-Replication feature implements metadata and data replication in a primary-secondary replication model. It works with a single namespace, and at a given time there’s only one primary region, which is serving both producers and consumers. There is a single hostname used to connect to the namespace, which always points to the current primary region. After promoting a secondary region, the hostname points to the new primary region, and the old primary region is demoted to secondary region. After the new secondary has been re-initialized, it is possible to promote this region again to primary at any moment. Replication modes There
Update Type: Preview, Services: Service Bus, Categories: Features, Services, Regions & Datacenters

Public Preview: Geo-Replication for Azure Service Bus Premium

Thu, 20 Jun 2024 16:47:53 Z

Status: In Preview We are excited to announce the public preview of the new Geo-Replication feature for Azure Service Bus in the premium tier. This feature ensures that the metadata and data of a namespace are continuously replicated from a primary region to a secondary region. Moreover, this feature allows promoting a secondary region at any time. The Geo-Replication feature is the latest option to insulate Azure Service Bus applications against outages and disasters. The Geo-Replication feature implements metadata and data replication in a primary-secondary replication model. It works with a single namespace, and at a given time there’s only one primary region, which serves both producers and consumers. There is a single hostname used to connect to the namespace, which always points to the current primary region. After promoting a secondary region, the hostname points to the new primary region, and the old primary region is demoted to secondary region. After the new secondary has been re-initialized, it is possible to promote this region again to primary at any moment. Learn more. Products: Azure Service Bus ________________________________________________________________________________________________________________________________
Update Type: Preview, Services: Service Bus, Categories: Services

Azure Logic Apps PeekLock caching and Service Bus queue Lockduration

Fri, 07 Jun 2024 16:20:15 Z

This article is about optimizations when integrating the “When messages are available in a queue (peek-lock)” Logic App trigger with an Azure Service bus queue. Under high load scenarios or business flows that takes from 1 to 5 minutes, stateful logic apps which are triggered by “When messages are available in a queue (peek-lock)” trigger, may need some adjustments for optimizing performance and avoiding degradation issues like the below mentioned: { "code": "ServiceProviderActionFailed", "message": "The service provider action failed with error code 'BadRequest' and error message 'The lock supplied is invalid. Either the lock expired, or the message has already been removed from the queue. For more information please see https://aka.ms/ServiceBusExceptions . Reference:XXXXXXX, TrackingId:xxxxxxxxxxxx, SystemTracker:gi::xxxxxxxxxxxxx:amqps://xxxxxxxxx.servicebus.windows.net/-source(address:/queue,filter:[]), Timestamp:2024-05-30T00:48:25 (MessageLockLost). For troubleshooting information, see https://aka.ms/azsdk/net/servicebus/exceptions/troubleshoot.'." } This may be due the several reasons. Let’s explore 2 of them and understand how they can be solved. Lock duration (lockduration for more details) property of the service bus queue is set to 1 minute by default. However, our business flow can take longer. To solve this problem, we can increase it up to 5 minutes. There are various ways to increase this value. a. Existing queue through the Azure portal: Go to the Service Bus namespace >> Entities >> Queues >> Your Queue >> Click “change” in the Message lock duration property and enter the new value and click “OK” b. Existing queue through Azure PowerShell: we are not going deep into this. Please refer to the following article: How to set LockDuration on an Azure ServiceBus queue with PowerShell | John Billiris (wordpress.com) c. When creating a new queue: Go to the Service Bus namespace >> Entitie
Update Type: Announcement, Services: Logic Apps, Service Bus, Categories: Services

Announcing Batch delete in Service Bus- Public Preview

Tue, 21 May 2024 17:26:40 Z

Azure Service Bus is a fully managed enterprise message broker with message queues and publish-subscribe topics. Sometimes, you may want to delete messages from your queues and subscriptions in a more programmatic manner, for example, to clear out old or unwanted messages from your entities. We are excited to announce the public preview of Batch Delete, a new feature that lets you delete messages in bulk from your Service Bus entities. Batch delete helps you to delete multiple messages from a messaging entity in one operation, instead of deleting them one by one. Since deletion is done at service side, you don't need to receive the messages before deleting them. To learn more about Batch Delete, visit aka.ms/batchdelete We are sure you will find the Batch Delete feature a significant improvement in Azure Service Bus and encourage you to explore this new addition. Know more: Introduction to Azure Service Bus, an enterprise message broker - Azure Service Bus | Microsoft Learn
Update Type: Preview, Services: Service Bus, Categories: Services

Public Preview Azure Service Bus Enhancements

Tue, 21 May 2024 00:00:00 Z

Azure Service Bus is a fully managed enterprise message broker that ensures secure and efficient delivery of data messages between different parts of your system, even when they're disconnected or processing tasks at different speeds. We're thrilled to announce a new feature to streamline message management and improve operational efficiency: batch delete.
Update Type: Preview, Services: Service Bus, Categories: Features

Update to Azure Functions Service Bus extension v5.x by 31 March 2025 for continued support

Fri, 22 Mar 2024 00:00:00 Z

Applications that are using the Azure Functions Service Bus extension v4.x will be unsupported after 31 March 2025
Update Type: Deprecation, Services: Service Bus, Azure Functions, Categories: Retirements

Microsoft named a Leader in 2024 Gartner® Magic Quadrant™ for Integration Platform as a Service

Tue, 12 Mar 2024 08:00:00 -0700

We’re thrilled to announce that Microsoft has once again been named a Leader in the 2024 Gartner® Magic Quadrant™ for Integration Platform as a Service. It’s the sixth time in a row that we’ve been recognized.
Update Type: Announcement, Services: Event Grid, Service Bus, Azure Functions, Categories:

Generally Available: Azure Chaos Studio supports new faults for Service Bus

Mon, 18 Dec 2023 00:00:00 Z

Azure Chaos Studio supports new faults for Service Bus.
Update Type: GA, Services: Service Bus, Azure Chaos Studio, Categories: Features, Services

Announcing general availability of partitioned namespaces for Azure Service Bus Premium

Wed, 15 Nov 2023 18:00:00 Z

Today we are excited to announce General Availability of our partitioned namespaces feature, which allows the use of partitioning for the premium messaging tier. This means that the overall throughput of a partitioned entity is no longer limited by the performance of a single message broker. Moreover, along with the partitioned namespaces feature we are also announcing an updated SLA. If you create a Premium namespace with the new partitioned entities feature enabled, in a region where Availability Zones is available, we will provide an SLA of 99.99%. Partitioned namespaces work in close conjunction with scaling through Messaging Units, as the configured MUs on a namespace are equally distributed across the different partitions. Currently it is possible to scale up to 4 partitions, and as each partition can scale from 1MU to 16MU, this means we can scale up to a total of 64MU. There are some differences between partitioning in the standard and premium SKUs. First, the number of partitions is configured during namespace creation on the premium SKU, while partitioned namespaces in the standard SKU comes with a fixed number of partitions. Second, unlike the standard SKU, partitioned namespaces in the premium SKU do not allow non-partitioned entities in them. To enable partitions, select to enable partitioning and set the number of partitions during creation of a new namespace. Please note that it is not possible to change the number of partitions after creation. More details can be found in the documentation, including a list of regions that are currently supported.
Update Type: GA, Services: Service Bus, Categories: Services, Regions & Datacenters

Generally available: Partitioned namespaces for Azure Service Bus Premium

Wed, 15 Nov 2023 00:00:00 Z

Partitoned namespaces for Azure Service Bus, allowing the use of partitioning for the premium messaging tier, is now generally available.
Update Type: GA, Services: Service Bus, Categories:

GA: Service Bus message settlement in isolated worker model for .NET Azure Functions

Wed, 25 Oct 2023 00:00:00 Z

Functions using the ServiceBusTrigger can perform message settlement actions in the isolated worker model for .NET applications
Update Type: Announcement, Services: Service Bus, Azure Functions, Categories: Features

Migrate to Azure Resource Manager control plane API version 2021-11-01 by 30 September 2026

Fri, 06 Oct 2023 00:00:00 Z

Older control plane APIs in Azure Service Bus, Azure Event Hubs, and Azure Relay will be retired.
Update Type: Deprecation, Services: Service Bus, Event Hubs, Categories: Retirements

Some Azure Service Bus SDK libraries will be retired on 30 September 2026—migrate to the latest SDKs

Fri, 06 Oct 2023 00:00:00 Z

Azure Service Bus SDK libraries that don't conform to Azure SDK guidelines will be retired and support will end.
Update Type: Deprecation, Services: Service Bus, Categories: Retirements

Announcing preview of Java Message Service 2.0 over AMQP on Azure Service Bus

Wed, 05 Aug 2020 00:00:00 -0700

Azure Service Bus simplifies enterprise messaging scenarios by leveraging familiar queue and topic subscription semantics over the industry driven AMQP protocol.
Update Type: Announcement, Services: Service Bus, Categories:

Unlock dedicated resources and enterprise features by migrating to Service Bus Premium

Wed, 03 Apr 2019 00:00:00 -0700

Azure Service Bus has been the Messaging as a Service (MaaS) option of choice for our enterprise customers. We’ve seen tremendous growth to our customer base and usage of the existing namespaces, which inspires us to bring more features to the service.
Update Type: Announcement, Services: Service Bus, Categories:

Azure Service Bus and Azure Event Hubs expand availability

Wed, 23 Jan 2019 00:00:00 -0800

The Azure Messaging team is continually working to enhance the resiliency and availability of our service offerings – Azure Service Bus, Azure Event Hubs, and Azure Event Grid.
Update Type: Announcement, Services: Event Grid, Service Bus, Event Hubs, Categories:

Azure Service Bus now integrates with Azure Event Grid!

Mon, 26 Feb 2018 00:00:00 -0800

Azure Service Bus now sends events to Azure Event Grid. The key scenario this feature enables is for Service Bus queues, topics, or subscriptions with low message volumes to not require a receiver...
Update Type: Announcement, Services: Event Grid, Service Bus, Categories: