BizTalk Server end of support: your options and timeline

The BizTalk timeline

The paid support bridge, and who cannot use it

Microsoft "plans to offer eligible BizTalk Server 2020 customers a paid, time-limited extended-mainstream support option from April 13, 2028, through April 10, 2030" (Microsoft: BizTalk Server 2020 end of sale announcement, checked on 2026-10-03). It is priced annually per licensed core and requires active Software Assurance. It excludes several components, including BAM, the ESB Toolkit, the SWIFT, HL7 and RosettaNet accelerators and legacy line-of-business adapters. "BizTalk Server 2016, HIS 2016, and earlier versions will not be eligible." (Microsoft: BizTalk Server 2020 end of sale announcement, checked on 2026-10-03) Microsoft frames the bridge as contingency time, not a plan.

A deadline that has already passed: SBMP

Azure Service Bus ended support for the SBMP protocol on 30 September 2026 (Microsoft Learn: Service Bus AMQP overview (SBMP retirement), checked on 2026-10-03). BizTalk's SB-Messaging adapter "uses the SBMP protocol" and "does not support the AMQP protocol" (Microsoft Learn: BizTalk SB-Messaging adapter, checked on 2026-10-03). If any BizTalk application exchanges messages with Azure Service Bus through that adapter, check it now: Microsoft has not published a BizTalk-specific fix, so treat affected interfaces as the first wave of your migration.

Your options

• Move to Azure Logic Apps Standard or Hybrid. Microsoft recommends starting now with Logic Apps Standard (Azure-hosted) or Logic Apps Hybrid (your infrastructure) (Microsoft: BizTalk Server 2020 end of sale announcement, checked on 2026-10-03). Many schemas, maps, rules, assemblies and custom .NET components can be reused or adapted (Microsoft Learn: BizTalk to Logic Apps migration overview, checked on 2026-10-03).
• Use the migration agent. The Azure Logic Apps Migration Agent is an open-source Visual Studio Code extension that uses GitHub Copilot, covering discovery, planning, conversion and validation, with BizTalk 2016 and 2020 as sources (Microsoft Learn: BizTalk migration approaches, checked on 2026-10-03).
• Move to another integration platform. If you are not standardising on Azure, price alternatives with the same inventory; see iPaaS pricing compared.
• Stay, with the bridge. Possible for eligible 2020 customers until April 2030, at extra cost and without the excluded components (Microsoft: BizTalk Server 2020 end of sale announcement, checked on 2026-10-03).

Microsoft is explicit that "migration isn't a lift-and-shift process" and recommends moving in waves (Microsoft Learn: BizTalk migration approaches, checked on 2026-10-03). Customers depending on Host Integration Server SNA features need Host Integration Server 2028, because Logic Apps Standard does not support SNA (Microsoft: BizTalk Server 2020 end of sale announcement, checked on 2026-10-03).

Migration-readiness checklist

• List every BizTalk application, orchestration, pipeline, map and adapter, and the partner or system at each end.
• Mark anything that uses the SB-Messaging adapter, BAM, the ESB Toolkit or an industry accelerator.
• Record the BizTalk version and Software Assurance status for each environment.
• Identify custom .NET components and who maintains them.
• Choose the first migration wave and a date to finish it before the end of sale.