On 30 September 2026, Azure Service Bus stops accepting SBMP — the transport BizTalk's SB-Messaging adapter uses by default. Without the AMQP hotfix, those connections are refused at the network level. Not degraded. Refused.
Hotfix KB5091375 adds AMQP to the SB-Messaging adapter. One call tells you whether you need it.
Sound familiar
Most BizTalk estates were built by people who left years ago. The platform still runs — that's the problem. It runs well enough that nobody has had to understand it since 2014.
Nobody knows what half these orchestrations do.
Original developers gone, documentation stale, business logic buried in XLANG nobody wants to open. Discovery is the real project.
We can't hire a BizTalk developer. We've tried for a year.
The talent pool shrinks every quarter and nobody new is learning it. Waiting raises the cost of running it and shrinks the pool that can move it.
Suspended messages every week, and no one knows why.
Someone resumes them manually and moves on. Nobody has traced root cause in years, because that means understanding the whole pipeline.
Audit flagged us for software approaching end of support.
Common in healthcare and financial services, and anything touching CMS or HIPAA. Compliance turns technical debt into a board conversation overnight.
We got a quote. It was a number and a 40-slide deck.
Generic cloud consultancies price BizTalk work off interface counts because they can't read orchestrations. That's how six-month projects become eighteen.
Every EDI partner onboarding takes six weeks and one person.
Trading partner config, envelope schemas, acknowledgement handling — all in one head. A business continuity risk, not just a technical one.
Verified against Microsoft lifecycle
Microsoft has confirmed BizTalk Server 2020 is the final release. These are the published dates — no rounding, no dramatization.
BizTalk 2020's SB-Messaging adapter uses SBMP by default, so any BizTalk-to-Azure integration that hasn't switched transport will fail — a network-level refusal, not a graceful degradation. Microsoft's hotfix KB5091375 (via a support case) adds AMQP and makes it the default. Retiring Service Bus SDK libraries share this date but are a separate, less urgent issue.
Every BizTalk 2016 deployment loses all support — no security patches, no hotfixes, no incident support. Microsoft's guidance is a direct modernization path to Azure Logic Apps rather than an interim upgrade. If you're on 2016, your window is now.
No further design changes or non-security feature requests; security updates continue into extended support. Reaching this date fully supported requires Cumulative Update 6 plus Windows Server 2022 and SQL Server 2022 — the original 2020 platform pairing expires well before BizTalk does.
Extended support for BizTalk Server 2020 expires. After this, every BizTalk deployment anywhere is unpatched and unsupported. In regulated industries that is a compliance finding, not a preference.
A methodical migration takes 6–18 months. Starting now buys parallel running, real UAT, and a rollback plan. Starting in 2029 buys a cutover weekend and a prayer.
Four questions · No email required
Sized by integration estate, not headcount — a 60-person healthcare payer can carry a heavier BizTalk footprint than a 3,000-person manufacturer.
Migration destinations
We hold no reseller or licensing partnerships with MuleSoft, Boomi, or TIBCO, and earn nothing from where you land. This is how we'd advise you regardless of who does the work.
Default recommendation
Even for a small estate, Logic Apps Standard is the lower-risk choice for a Microsoft shop. You reuse XSLT maps, schemas, and EDI partner configuration through Microsoft's migration tooling, and keep a supported vendor platform underneath. Consumption pricing at low volume is genuinely cheap.
Worth considering
With real in-house .NET capability and a genuinely simple estate — file drops, a few REST calls, no multi-party EDI — a purpose-built .NET layer removes platform licensing entirely. You pay Azure compute and own every line.
The honest trade-off: you become the platform vendor. Every connector, retry policy, dead-letter path, and EDI envelope becomes your team's code — and building it is a larger engagement than a Logic Apps migration. We recommend it only when your team can carry it.
Default recommendation
For 30–200 flows in a Microsoft shop, this is the intended successor and the path of least resistance. Logic Apps handles orchestration and B2B, API Management fronts your services, Service Bus carries the durable messaging MessageBox used to, Event Grid covers event routing.
Worth considering
Most mid-size estates have a handful of integrations that resist a low-code model — proprietary protocols, high-throughput transformations, logic too dense for a designer. Run those as Functions alongside Logic Apps rather than forcing one shape.
Where scale changes the answer
Above roughly 200 flows with a global partner network and a dedicated CoE, licensed iPaaS starts earning its cost through centralized governance and observability. That said, plenty of large Microsoft-committed enterprises run Azure Integration Services at this scale — iPaaS is not automatic at 200 flows.
What actually decides it
At this size the platform comparison matters less than the operating model. Who owns the integration layer? Is there a CoE, or does each unit build its own? What's your rollback story for a partner-facing flow?
| Platform | Best for | Licensing | Estate size | B2B / EDI | You maintain |
|---|---|---|---|---|---|
| Azure Logic Apps | Microsoft shops, BizTalk asset reuse | Pay per execution | Any | Native X12, EDIFACT, HL7 | Workflows only |
| Custom .NET on Azure | Simple estates with real .NET capability | None — infra only | Under 30 flows | Build it yourself | The whole platform |
| MuleSoft Anypoint | API-led, Salesforce, multi-cloud | High | 200+ flows | Strong | Workflows only |
| Dell Boomi | EDI at scale, faster delivery | Mid | 100+ flows | Strong | Workflows only |
| TIBCO | Real-time streaming, financial services | High | 200+ flows | Enterprise-grade | Workflows only |
If you're not migrating yet
Budget cycles, competing programmes, an ERP replacement already in flight — there are legitimate reasons to defer. What isn't legitimate is running an unsupported, undocumented estate nobody understands.
Managed BizTalk support
An ongoing engagement that gives you a team who knows your estate — so the platform stops being a single-person dependency.
SBMP remediation
Narrow, urgent, independent of any migration decision. If BizTalk touches Azure Service Bus, this closes before 30 September 2026 whatever your long-term plan.
Why we offer this: most consultancies sell only the migration, because that's the big number. But a stable, documented, patched estate migrates faster and cheaper. Doing the boring work first isn't a delay tactic — it's the cheapest discovery you'll ever buy.
How the work runs
The commonest failure in BizTalk migration is pricing the work before anyone reads the orchestrations. These five phases are real gates, not slides.
PHASE 01
Full inventory of orchestrations, maps, schemas, adapters, pipelines, and EDI configuration. Every flow tiered by complexity and criticality — and we tell you what we found even when it changes the price.
PHASE 02
Platform recommendation weighed against real constraints: team skills, cloud commitments, EDI volume, regulatory scope. Written, with the reasoning shown.
PHASE 03
Ordered by risk, not convenience. Low-impact flows first to prove the pattern and calibrate estimates, then mission-critical paths once validated.
PHASE 04
Reuse maps, schemas, and partner configuration wherever tooling allows. Rebuild where it doesn't — complex pipeline components and host-level config rarely translate directly.
PHASE 05
Both platforms live, output compared message-for-message, then a controlled cutover with a tested rollback path. Nobody cuts over on a Friday and hopes.
Who you'd work with
BeyondBizTalk is led by Suren Machiraju, a founding member of Microsoft's BizTalk B2B team in the early 2000s and one of the architects behind the integration patterns BizTalk introduced. He holds over 20 patents in enterprise integration, messaging, and B2B architecture.
After 25 years at Microsoft across Cloud & Enterprise and Azure, reaching Partner and Principal level, he founded Maarg Ventures to bring that depth to enterprises facing this transition.
That matters for one practical reason: when we open an orchestration built in 2007, we recognise the pattern and know why it was built that way. General Azure consultancies read the same XLANG and see a black box — which is how estimates double halfway through.
We've delivered 10+ end-to-end BizTalk implementations and migrations across healthcare, manufacturing, financial services, and government.
Suren Machiraju & Suraj Gaurav · Walter de Gruyter / De|G Press, 2017 · 340 pages. Integration patterns, Azure modernization paths, and B2B architecture — one of four books Suren has authored.
View on Amazon ↗Client results
We've found our partnership enormously valuable — the quality of work and depth of BizTalk and Azure integration expertise is simply unmatched.
Incredibly responsive, and even in our toughest integrations the team always nails down the details for success. A truly fruitful partnership built on deep technical know-how.
Much-needed help keeping us compliant with complex new CMS guidelines as we onboarded our federal exchange business. Their healthcare integration expertise was critical to our timeline.
Over 50 applications to migrate from our data center to Microsoft Azure. The team handled the full complexity and delivered a smooth, zero-disruption lift-and-shift.
A robust solution to load ESI Part B Drug flat files into our Oracle database, with operational reporting. Technically sharp, reliable, and exactly what we needed on a tight schedule.
A key role in converting our on-premise application into a multi-tenant SaaS platform on Microsoft Azure. A genuinely transformational engagement — on time, exceptional quality.
Common questions
Azure Service Bus stops accepting the Service Bus Messaging Protocol. BizTalk Server 2020's SB-Messaging adapter uses SBMP as its default transport, so any BizTalk port pointing at Service Bus has its connections refused at the network level. Microsoft has published hotfix KB5091375 — obtained by opening a support case — which adds AMQP support and makes AMQP the default, with SBMP as an opt-in fallback until retirement. Separately, three older Service Bus SDK libraries retire the same day, which matters if you have custom .NET pipeline components talking to Service Bus directly.
Microsoft has confirmed BizTalk Server 2020 is the final version. Mainstream support runs to 11 April 2028, extended support to 9 April 2030. Microsoft's guidance points 2016 customers toward a direct modernization path to Azure Logic Apps, and positions Azure Integration Services as the platform going forward. To be precise: BizTalk is fully supported today and will be for years. This is a planning problem, not an emergency — except for SBMP, which genuinely is urgent.
Six to eighteen months for most estates. The variables that matter are orchestration complexity, trading partner count, how much custom pipeline code exists, and how much institutional knowledge remains in-house. Estates with hundreds of interfaces and heavy EDI regularly run twelve to eighteen months. Anyone quoting a duration before reading your orchestrations is guessing.
Maps and schemas, usually yes — Logic Apps supports BizTalk XSLT maps and schemas, and Microsoft's migration tooling handles a meaningful share automatically. B2B and EDI trading partner configuration carries across reasonably well. Orchestrations are harder: straightforward sequential flows translate, but complex correlation, custom pipeline components, and host-level configuration typically need rebuilding. We maximise reuse because it lowers cost and risk, but won't promise a translation rate before discovery.
For a Microsoft-aligned organisation, Azure Logic Apps and the wider Azure Integration Services stack is usually right regardless of size — it reuses your BizTalk investment, and Microsoft offers migration tooling and incentives. MuleSoft is a genuine alternative for multi-cloud estates or Salesforce-heavy architectures. Boomi is strong on EDI onboarding and delivery speed. TIBCO earns its cost in extreme-throughput real-time messaging. We hold no licensing partnerships with any of them, so we have no financial reason to point you anywhere.
Then don't. Migrating badly under budget pressure is worse than migrating later. Close the SBMP gap, get current on Cumulative Update 6 with Windows Server 2022 and SQL Server 2022, and document the estate while people who understand it are still there. That work isn't wasted — it becomes your migration discovery. See managed support.
Our principal was a founding member of Microsoft's BizTalk B2B team and holds 20+ patents in this area. Practically: we read your orchestrations rather than counting your interfaces. Most overruns come from discovering during build what should have surfaced during discovery — an unhandled correlation set, a pipeline component doing something undocumented, a partner agreement with a custom acknowledgement flow. We find those in week two, not month seven.
The initial conversation and a high-level readiness review are free. You get a deadline exposure map, a platform recommendation with the reasoning shown, and an indicative effort and duration range. A full discovery — the one producing a defensible plan and a real number — is a paid, fixed-scope engagement, because doing it properly takes weeks and anyone offering it free is amortising it into an inflated build quote.
Start here
No slide deck, no discovery call that's actually a sales call. Bring your BizTalk version and a rough sense of your estate, and we'll tell you what you're exposed to and what fixing it takes.