BizTalk Server 2020 Faces Protocol Shift: AMQP Support Arrives Before SBMP Retirement

Microsoft has delivered a critical update for BizTalk Server 2020 customers, releasing a hotfix that enables Advanced Message Queuing Protocol (AMQP) support in the Service Bus adapter before the September 30, 2026 retirement of the Service Bus Messaging Protocol (SBMP). This transition represents a significant shift for organizations relying on the BizTalk Service Bus (SB-Messaging) adapter, which currently depends on SBMP for its operations.

The Protocol Change Landscape

The retirement of SBMP support in Azure Service Bus marks the end of an era for BizTalk Server customers. Since the BizTalk Service Bus adapter was designed around SBMP, this change necessitates a fundamental reconfiguration of how messages flow between BizTalk Server and Azure Service Bus. Microsoft's response has been proactive—the hotfix (KB5091375) adds native AMQP support to the adapter, providing a modern alternative protocol that aligns with current Azure messaging standards.

AMQP becomes the default transport mechanism once the hotfix is installed, though SBMP remains available as an opt-in fallback for backward compatibility. This dual-support approach gives organizations flexibility during their migration period, allowing them to test AMQP thoroughly before fully committing to the new protocol.

Hotfix Availability and Requirements

The hotfix is specifically available for BizTalk Server 2020 Cumulative Updates 6 and 7, targeting organizations that are maintaining current support levels. However, there's an important technical consideration: the current hotfix is built on the existing Service Bus SDK, which itself is scheduled for deprecation in September 2026. Microsoft has acknowledged this overlap and plans to release an updated version in June 2026 based on the new Service Bus SDK.

This timeline creates a strategic decision point for customers. Organizations can either implement the current hotfix immediately to begin validation and migration work, or wait for the June update if they don't need to start testing right away. The June refresh will provide a more future-proof foundation, eliminating concerns about the underlying SDK deprecation timeline.

Migration Steps and Validation Requirements

Microsoft outlines a clear migration path for affected customers. The first step involves migrating adapter configurations from SBMP to AMQP, which requires careful planning and testing. Organizations should install the hotfix well in advance of the September 2026 deadline, ideally in non-production environments first to minimize operational risk.

The validation process extends beyond simple connectivity testing. Microsoft specifically calls out the need to validate large message and file patterns, as AMQP may handle these scenarios differently than SBMP. Additionally, organizations should test any operational fallback strategies they've implemented, ensuring that the opt-in SBMP fallback works as expected when needed.

Strategic Implications for BizTalk Customers

This protocol transition occurs against the backdrop of Microsoft's broader modernization push toward Azure Logic Apps. While the company remains committed to supporting BizTalk Server 2020 through its official product lifecycle—with extended paid support available after April 2028—the SBMP retirement serves as a catalyst for organizations to evaluate their integration strategies.

For many customers, this represents an opportunity to begin modernizing their integration architecture while maintaining their existing BizTalk investments. The AMQP support in the hotfix provides a bridge between current SBMP-based implementations and future Azure-native solutions. Organizations can use this transition period to build AMQP expertise and gradually shift workloads toward more modern integration patterns.

Obtaining the Hotfix

Customers can acquire the hotfix through Microsoft support channels by opening a support case and requesting KB5091375. Alternatively, customers with dedicated Microsoft account teams can work through those relationships to obtain the update. Microsoft plans to issue a new KB article specifically for the June 2026 SDK-based refresh, providing clear documentation for that subsequent update.

Timeline and Planning Considerations

The September 2026 retirement date provides a clear deadline, but Microsoft's recommendation to install the hotfix "well before" that date suggests organizations should begin planning immediately. The June 2026 SDK refresh adds another milestone to the timeline, creating a phased approach to the transition.

Organizations should consider their current BizTalk Server version, their dependency on specific messaging patterns, and their overall modernization timeline when planning their approach. Those on older cumulative updates may need to upgrade before applying the hotfix, while those with complex messaging scenarios should prioritize early validation to identify any compatibility issues.

The SBMP retirement and AMQP transition represents more than just a protocol change—it's a strategic inflection point for BizTalk Server customers. Organizations that approach this transition methodically, leveraging the hotfix to validate AMQP while planning their longer-term integration strategy, will be best positioned to maintain operational continuity while positioning themselves for future modernization opportunities.