BizTalk Server end of life: what it means, and what to do next.
There is no BizTalk Server 2022. Mainstream support for BizTalk Server 2020 ends April 11, 2028, and paid extended support runs until April 9, 2030. Here are the facts, your realistic options, and how to plan the move without a big-bang cutover.
BizTalk Server 2020 is the final version Microsoft will release. Mainstream support ends April 11, 2028, and paid extended support runs until April 9, 2030. BizTalk is not switched off on those dates: environments keep running, but without security updates, and the pool of engineers who know the platform keeps shrinking. Cerebrum City are Microsoft V-TSP–recognized BizTalk specialists with two decades running BizTalk in production; we map each artifact to its Azure equivalent, run old and new in parallel, and cut over in waves so there is no outage. Book a courtesy assessment at (678) 203-0800.
What Microsoft has actually said.
Three things are settled. Everything else in a BizTalk end-of-life conversation is planning, not fact.
Final release
BizTalk Server 2020 is the last version
There is no BizTalk Server 2022, and no later release is planned. The product line ends with 2020 — so there is no upgrade path that keeps you on BizTalk.
Support horizon
Mainstream support ends April 11, 2028
Paid extended support then runs to April 9, 2030, and end of support is April 10, 2030. Once mainstream support ends, non-security fixes stop being included and become a paid engagement.
What does not happen
Nothing switches off
BizTalk keeps processing messages after support ends. The change is that the risk becomes yours alone — unpatched, unsupported, and harder to staff every year.
The real date is April 2028. The harder constraint is your people.
Most BizTalk estates are not at risk because of a date on a Microsoft page. They are at risk because of who is left to explain how the integrations work.
No security updates
BizTalk usually sits at the network edge handling trading-partner traffic. An unpatched integration tier is a poor place to carry known vulnerabilities.
Audit and compliance exposure
Running unsupported software becomes a finding in its own right, independent of whether anything has actually gone wrong.
Tribal knowledge walking out
The orchestrations were built by people who understood the business rules. Every year fewer of them are still in the building to document the edge cases.
Dependency drift underneath
Supported Windows Server, SQL Server, and adapter versions keep moving. The platform gets harder to host long before support formally lapses.
Three honest paths — including doing nothing.
Not every estate needs to move this year. What every estate needs is a decision made deliberately rather than by default.
Option 1
Stay on BizTalk, manage the risk
Defensible in the short term if your estate is stable, isolated from the edge, and staffed. It is a holding position, not a strategy — and it gets more expensive to exit the longer it runs.
Option 2 · Most common
Rebuild on the right Azure services
Each BizTalk artifact — ports, orchestrations, pipelines, maps, adapters — is mapped to its Azure equivalent across Logic Apps, Service Bus, and Functions. Run in parallel, prove message-for-message, cut over in waves.
Option 3
Move to an Azure-native successor
Where Logic Apps alone leaves gaps — high-throughput messaging, complex mapping, stateful orchestration — the Art2link ESB provides the BizTalk constructs natively on Azure, in your own tenant.
We didn’t read about BizTalk. We ran it for 20 years.
Most cloud partners have never operated BizTalk at enterprise scale. We have — which is why we recognize the silent-failure and dead-letter patterns that break migrations weeks after everyone declared success. Microsoft V-TSP–recognized for BizTalk Server and an ISV Partner in the Microsoft AI Cloud Partner Program.
The questions teams ask first.
Is BizTalk Server end of life?
Effectively, yes. BizTalk Server 2020 is the final version Microsoft will release. Mainstream support ends April 11, 2028, and paid extended support runs until April 9, 2030, after which the platform receives no security updates. BizTalk is not switched off on those dates; existing environments keep running. What ends is Microsoft’s obligation to patch them.
Is there a BizTalk Server 2022 or a newer version coming?
No. There is no BizTalk Server 2022 and no later release planned. BizTalk Server 2020 is the end of the product line. Microsoft’s forward path for integration workloads is Azure — Logic Apps, Service Bus, and Functions — which is why migration planning, not an upgrade, is the decision in front of most BizTalk estates.
When does BizTalk Server support actually end?
Microsoft has published the dates. For BizTalk Server 2020, mainstream support ends April 11, 2028, paid extended support runs until April 9, 2030, and end of support is April 10, 2030. The date that matters for most enterprises is April 2028, not 2030: once mainstream support ends, non-security hotfixes become a paid engagement rather than something included. Earlier BizTalk versions have their own, earlier dates.
What happens if we stay on BizTalk after support ends?
The platform keeps processing messages, but no security updates are issued for it. That creates three compounding exposures: unpatched vulnerabilities in a system that usually sits on your network edge handling partner traffic, audit and compliance findings for running unsupported software, and a shrinking pool of engineers who still know the platform. The technical risk is manageable; the people risk is the one that gets worse every year.
Is BizTalk dead?
BizTalk is not dead in production — a great deal of enterprise message traffic still runs on it every day, and it does several things well. It is dead as a roadmap: there will be no further versions, and support has an end date. The practical reading is that BizTalk remains a reliable platform to run and a poor platform to keep betting on.
Do we have to move everything to Azure Logic Apps?
No. Logic Apps handles many integration patterns well and leaves gaps in others — high-throughput messaging, complex mapping, and stateful orchestration in particular. Cerebrum City maps each BizTalk artifact to the right Azure service, and where Logic Apps falls short we deploy the Art2link ESB, our Azure-native BizTalk successor, rather than force-fitting a workload into one tool.
How long does it take to move off BizTalk?
It depends on the number of interfaces and trading partners, which is exactly what an assessment scopes. The sequence matters more than the total: because we run BizTalk and the new Azure platform in parallel and cut interfaces over in waves, there is no production outage and no single deadline the whole estate has to hit at once.
Find out what moving off BizTalk actually involves.
The courtesy assessment inventories your BizTalk estate, maps each artifact to its Azure target, flags the high-risk interfaces, and gives you a staged roadmap — on your schedule, with no obligation.
Or call (678) 203-0800
