The underestimated deadline that endangers your day-to-day business
It is a classic scenario in the Enterprise IT: the Great Migration Plan For replacing the BizTalk server.
At the same time, the budget for 2027/28 is reserved. The roadmap looks clean: Mainstream Support by April 11, 2028, Extended Support until April 9, 2030. Enough time, many IT managers think.
But the reality of cloud dependencies throws a spanner in the works of this schedule.
Because Microsoft has one Critical Announcement madeAzure updates), which is not yet on the radar in many companies: am September 30, 2026, so Almost 2 years before the Biztalk EOL, will support for that Service Bus Messaging Protocol (SBMP) set in the Azure Service Bus (Service Bus Messaging).
That means specifically:
no transitional period. No fault tolerance. No Grace Period.
are affected All BizTalk integrations that use the Azure Service Bus via the SBMP (Service Bus Adapter/Legacy Setup) protocol. These connections no longer work from the deadline.
And now it gets explosive: As of February 2026, they remain less than 8 months.
The problem
Why the SBMP shutdown immediately affects your BizTalk environment
What is SBMP – and why is your BizTalk Server (probably) using it?
SBMP (Service Bus Messaging Protocol) is an older Microsoft proprietary messaging protocol designed to communicate between on-premises systems and the Azure Service Bus.
The hook:
If you’re running BizTalk Server in a hybrid scenario, that is, connect on-premises BizTalk to Azure Cloud services, you’re most likely to use the standard Service Bus Adapter. This adapter uses SBMP as the default protocol in older versions and many historically grown configurations.
Typical scenarios affected:
- Biztalk Send Ports, Send messages to Azure Service Bus Queues/Topics
- BizTalk Receive Locations, Receive the messages from Azure Service Bus
- Hybrid Integrations: On-Prem ERP (SAP, D365) ↔ BizTalk ↔ Azure Cloud Apps (Logic Apps, Functions, External SaaS)
- EDI workflows: Partner communication if this is realized via Azure Service Bus (Queue/Topic/Relay)
The consequence
Immediate business stop on September 30, 2026
The consequence is hard and without warning: It is clear: On the deadline in September 2026, these connections will no longer work. No gradual loss of performance. No degraded fashion.
Instead, the following applies:
- Connection Failure On all SBMP-based service bus connections
- Message Delivery Errors in critical business processes (e.g. orders, delivery notes, payments)
- Partner EDI Communication Cancels (suppliers, customers, external systems)
- Compliance Violations (If statutory data transmissions fail, e.g. e-invoicing, reporting obligations)
The bottom line is that the risk is not a gradual decay, but an immediate business stop in the supply chain or in data exchange.
The trap: "We'll migrate soon anyway"
Why many Enterprise Architects are just falling into a time trap
In our consultations over the last few weeks, we often hear:
“We’re going to Azure Integration Services anyway in 2027/28. It’s no longer worth touching BizTalk.”
But let’s calculate briefly:
| Heute | 30. September 2026 | 11. April 2028 |
|---|---|---|
|
February 2026
|
SBMP shutdown |
BizTalk Mainstream Support End |
|
7 months left |
Breaking Hybrid Integrations |
Migration plan goal of most |
A full enterprise migration from BizTalk to Azure Logic Apps takes:
- Small (< 20 orchestrations): 3-6 months
- Medium (20-100 orchestrations): 6-12 months
- Large (> 100 orchestrations, complex): 12-24 months
That means: Anyone who now thinks “We’ll start migrating in 2027” is risking being surprised by the SBMP shutdown in the middle of the migration. In addition, under massive time pressure, they must both carry out a technical AMQP update (Quick Fix) and at the same time drive strategic migration. double effort. double risk. double costs.
The Q3/Q4 problem: Timing is everything
In addition, the problem is exacerbated by the time of the shutdown: September 30, 2026 falls exactly into the Q3/Q4 year-end business of many companies.
Typical conflicts:
- Retail/E-Commerce: Preparing Black Friday, Christmas Business
- Manufacturing: Annual Financial Statements, Inventory, Supplier Accounts
- Financial Sector: Quarterly Financial Statements, Compliance Reporting
- IT departments: Change Freeze (many companies stop critical updates in September-November)
Therefore, if you ignore the topic now, you will be under massive time pressure in the summer – exactly when change freezes begin.
Your options
Decision framework for IT decision makers
IT managers are now facing a critical course. There are two valid ways to reduce the risk. Which one is right for your company depends on your long-term strategy, your budget and your team know-how. We present two options:
Option B:
The strategic flight forward (fast track migration)
The strategy: You use SBMP printing as a catalyst to immediately migrate the affected interfaces to Azure Logic Apps Standard (or Azure Integration Services)
Advantage: Investment in the future
- You invest in the target architecture. Money flows into the future, not the past.
- You create the first migration step (Proof of Concept, Team Upskilling, Establish Cloud Architecture)
- You reduce the technical loads (less BizTalk orchestrations = less legacy load)
- You gain cloud native benefits: auto-scaling, managed services, modern monitoring tools (Azure Monitor, Application Insights)
Disadvantage: Initial architectural decisions required
- Requires Cloud Know-How (Azure Logic Apps, Service Bus, API Management)
- Team may need to be upskilled (training, workshops, external support)
- Architecture decisions must be made quickly (Logic Apps Standard vs. Consumption, Event-Driven-Patterns, Hybrid Connectivity with Azure Arc)
The pragmatic implementation:
Selective Fast Track Migration
You don’t have to migrate everything! The smart approach:
Step 1: Identify the Critical Interfaces
Analyze which of your BizTalk orchestrations are actually affected by the SBMP retirement. Often it is only a small part (10-30% in our projects).
Step 2: Fast Track Migration Only These Interfaces
Only migrate the SBMP-dependent interfaces to Azure Logic Apps Standard. The rest of your BizTalk landscape will remain unchanged and will continue until 2028.
Step 3: Establish Proof of Concept
You now have:
- A first cloud footprint (Azure Logic Apps productive in use)
- Team experience with Azure Integration Services
- Architecture Patterns for Hybrid Scenarios (BizTalk + Azure side by side)
- Budget justification for further migration (you can show ROI)
Who is Option B for?
- All interfaces that are on the modernization roadmap
- Medium to large number of affected interfaces (> 10-20)
- IT manager with strategic modernization mandate (cloud first strategy)
- Teams that want to build cloud know-how (skill building as a goal)
Option A:
The technical quick fix
(AMQP update)
The strategy: You convert your existing BizTalk Service Bus adapters to the newer AMQP protocol (Advanced Message Queuing Protocol). AMQP is the open standard that Microsoft will only support from September 2026.
Advantage: buy time
- You gain time until the final BizTalk EOL (2028/2030)
- You can perform your strategic migration as planned (without time pressure)
- No change of architecture required: BizTalk remains BizTalk
Disadvantage: “Dead Horse Investment”
- It is a pure technical investment without functional added value
- Money flows into the past (legacy preservation), not into the future
- they only "extend" the lifetime of a system that is to be replaced anyway
The technical reality: more complex than expected
Many IT managers underestimate the effort of an AMQP update. It’s not just a checkbox toggle. Here are the typical stumbling blocks:
Change adapter configuration (not trivial)
- Each affected SEND port and RECEIVE location must be manually reconfigured
- Transport Type Properties must be switched from SBMP to AMQP
- Authentication methods change (SBMP uses ACS tokens, AMQP uses SAS tokens or managed identity)
Firewall and Network Customizations
- AMQP uses other ports (5671/5672 instead of 9350-9354)
- Many company firewalls need to be customized (shares, DMZ rules)
- TLS/SSL certificates may have to be updated
Adapter behavior changes
- AMQP has a different message handling (e.g. for Retry-Logic, Session-Handling, Dead-Letter Queues)
- Existing orchestrations can react unexpectedly differently (race conditions, timeouts)
- Extensive tests required (unit tests, integration tests, UAT)
Documentation is incomplete
- Microsoft has released the official SBMP-to-AMQP migration documentary only in rudimentary terms
- Many community posts are contradictory or outdated
- Trial & Error is often necessary (= risk in productive operation)
Who is Option A for?
- Systems to be replaced after 2028/2030
- Small number of affected interfaces (< 10 send ports/receive locations)
- IT teams with deep BizTalk know-how (can change adapter configuration by themselves)
- Budget restrictions AMQP update is cheaper than migration)
Practice insight
How we evaluate the risk in a pragmatic way
In our current BizTalk Migration assessments, we see that blanket decisions (“patch everything!” or “migrate everything!”) are often expensive and risky. Instead, you need a data-driven, selective strategy.
Customer feedback
“We were panicking to update or migrate 120 orchestrations in 8 months. The analysis of Data Passion showed us: there are only 18. Suddenly, the project could be planned and at the same time we took the first step towards the cloud, without jeopardizing our day-to-day business.”
Case study
Manufacturing company with 120 BizTalk orchestrations
Starting position: A medium-sized production company (automotive supplier) faced exactly this dilemma:
- 120 BizTalk Orchestrations (grown over 10 years)
- Highly complex: SAP integration, EDI partner connections, internal process workflows
- Migration plan: complete replacement only in 2028 (budget for 2027/28 planned)
- Issue: Massively reliant on Azure Service Bus (45 Send Ports, 28 Receive Locations)
- Uncertainty: "Do we have to patch everything now? Or migrate everything? Both are unrealistic in 7 months!"
The result:
- Migration risk minimized: only 15% of the landscape had to be touched immediately
- Budget spared: instead of 120 orchestrations, only 18 were migrated (approx. 70% cost savings vs. full migration)
- No productive failure: on 09/30/2026 everything is stable (18 interfaces on Azure, 102 on Biztalk)
- Built Cloud Know-how: The team now has experience with Azure Logic Apps (for the planned 2027/28 migration)
- Proof of Concept Established: The first step into the cloud was taken – without jeopardizing operational operations
The Data Passion Approach:
Instead of putting blindly resources into an AMQP update or panic migration, we instead carried out our BizTalk on Azure Migration Assessment (including AI-supported analysis).
Step 1: AI Supported Dependency Analysis
Our tools scanned the entire BizTalk landscape:
- Which orchestrations use the Service Bus Adapter?
- Which protocol is configured (SBMP vs. AMQP)?
- How critical are the affected processes (Business Impact)?
- How complex are the orchestrations (migration effort)?
The result (surprising):
Of the 120 orchestrations, only 18 were critically affected by the SBMP retirement (= 15%). The remaining 85% used either:
- Other adapters (File, FTP, HTTP, SAP)
- Service Bus Connections (modern setups) already configured for AMQP
- No Azure Cloud Connection (only on-prem)
Step 2: Selective Fast Track Strategy
For the 18 critical orchestrations, we created a 3-month fast-track migration to Azure Logic Apps Standard:
- 6 orchestrations: EDI partner connections (highest priority) → migrated in month 1-2
- 8 Orchestrations: SAP to Azure Workflows → Migrated to Month 2-3
- 4 orchestrations: internal processes → migrated in parallel
Step 3: Rest Remains Biztalk (until 2028)
You now have:
- A first cloud footprint (Azure Logic Apps productive in use)
- Team experience with Azure Integration Services
- Architecture Patterns for Hybrid Scenarios (BizTalk + Azure side by side)
- Budget justification for further migration (you can show ROI)
Schedule
Act before the summer break
Status: February 2026
Less than 8 months remain until the SBMP shutdown on September 30, 2026.
| Period of time | Option A: AMQP update | Option B: Fast Track Migration |
|---|---|---|
| March 2026 | Complete inventory, set up log check, test environment | Perform assessment (including AI analysis), prioritize interfaces |
| April 2026 | AMQP Update Pilot (2-3 Interfaces), Testing | Architectural Design (Logic Apps Standard), Team Training |
| May 2026 | Rollout AMQP update (Batch 1), Productive Tests | Migration Batch 1 (Critical Interfaces), Parallel Operation BizTalk+Azure |
| June 2026 | Rollout AMQP update (Batch 2), UAT | Migration Batch 2, Integration Testing |
| July 2026 | Finalization, documentation | Migration Batch 3, Performance Tuning |
| August 2026 | Buffer month (for rework) | Buffer month (for rework) |
| September 2026 | 30.09.: SBMP shutdown – Your interfaces run on AMQP | 30.09.: SBMP shutdown – Critical interfaces run on Azure |
⚠️ Important:
Many companies have change freezes (year-end business, Q3/Q4 deal) in September-November. If you don’t start until August, it’s too late!
Our recommendation: Make the decision (option A or B) by the end of February/beginning of March 2026. Start implementation at the latest at the beginning of April.
Conclusion: SBMP shutdown is your wake-up call
The 3 most important findings for IT decision-makers:
1. SBMP retirement is not a “nice-to-know”, but business-critical
On September 30, 2026, all SBMP-based BizTalk-to-Azure hybrid integrations will break off. immediately. without warning.
If you are affected and not acting, your day-to-day business will stop.
2. You don’t need panic migration of your entire BizTalk landscape
Our experience shows that in most cases only 10-30% of the orchestrations are critically affected.
With a selective, data-driven strategy (AMQP update for non-critical, fast-track migration for strategic interfaces) you minimize risk and costs.
3. Act now = strategic advantage
Anyone who uses the SBMP retirement as a catalyst for modernization (option B: fast-track migration) invests in the future.
You build cloud know-how, create proof of concepts and gain experience before the big 2027/28 migration begins.
Next steps
How DATA Passion supports you
Are you unsure whether your BizTalk environment is affected? You don’t know if AMQP update or fast track migration is the right choice?
As Microsoft Solutions Partner for Digital & App Innovation and Infrastructure as well as specialists in BizTalk-to-Azure migrations, we support you pragmatically and data-driven.
BizTalk to Azure Migration Assessment (€2,500)
Our assessment package includes:
- AI-supported dependency analysis: your BizTalk environment
- SBMP risk identification: Which interfaces are affected? Which protocol is used?
- Business Impact Rating: Prioritization by Criticality
- Decision Framework: AMQP update vs. Fast Track Migration (incl. cost-benefit viewing)
- Individual migration plan: with timeline, budget, resource requirements
- Exclusive Benefits: Access to our Best Practice Patterns, Architectural Templates
Duration: Within a few days (depending on your BizTalk complexity)
Result: Concrete recommendation for action + detailed migration plan
The clock ticks: Act now
Status: February 2026
Less than 8 months remain until the SBMP shutdown.
Don’t wait until the summer break.
Until then, all qualified partners are fully booked and they are under massive time pressure.
Our promise:
We support you with pragmatic, data-driven advice – no sales pitches, no panic-making. Only specific recommendations for action that fit your situation.
More Data Passion resources
If you would like to delve deeper into the topic of BizTalk Migration, we recommend:
From Biztalk to the future: AI as the key to modern integration: our article on AI-supported BizTalk migration (October 2025)
SAP Integration and BizTalk Migration: Is the SAP Integration Suite the optimal BizTalk alternative – and how does a technical, organizational and economical transition succeed?
End-to-end monitoring for BizTalk & Azure Integration Services: How to monitor hybrid integrations across system boundaries
Get started
Find your use cases with real ROI
Contact us via the contact form for a non-binding initial consultation. We’ll get back to you as soon as possible with suggested dates.
