BizTalk Server has been the backbone of enterprise integration for thousands of organisations. Microsoft has now announced the end of mainstream and extended support — your integration estate needs a plan.
For many organisations, Microsoft BizTalk Server became the authoritative orchestration layer — routing messages between ERP systems, production lines, partner portals, and cloud services.
It introduced a centralised, message-driven integration model at a time when alternatives were limited. Over the years, BizTalk environments grew to cover hundreds of interfaces, business rules, and long-running workflows. The platform delivered reliability, but also accumulated significant technical depth and operational dependency.
For most organisations running BizTalk today, the platform is:
This is not a fringe legacy tool — it is core infrastructure. That is exactly why the end-of-life announcement demands careful, deliberate planning.
Mainstream support for BizTalk Server 2020 ends in April 2028. Extended support runs until April 2030 — after which there will be no security patches, no hotfixes, and no official support.
BizTalk 2006 establishes itself as the enterprise integration standard. Rapid adoption across manufacturing, logistics, and financial sectors.
Microsoft ships what is effectively the last version of BizTalk. No new major releases are planned. Azure Integration Services is positioned as the strategic successor. What was once the leading choice — receiving major updates every two to three years — has received no new features since. The product is in maintenance mode, and the roadmap ends here.
No new features, no design changes, no warranty claims. Security and critical updates continue under extended support only.
All support terminates. No security patches. Running BizTalk beyond this date introduces unmitigated security and compliance risk. The clock is ticking.
Until all support ends. A complex integration estate takes 18–36 months to migrate safely.
The number of active BizTalk interfaces in a mid-to-large enterprise. Each one must be assessed, migrated, or decommissioned.
Running unsupported integration middleware is a security, compliance, and operational risk that auditors and insurers notice.
"The question is not whether to move on from BizTalk. The question is how to do it without disrupting the business that depends on it."
Every organisation facing BizTalk EOL lands on one of three strategies. Each has different cost, risk, and capability profiles.
Discover characteristics of each option and decide which is the best for you.
| Criteria | A — Commercial iPaaS | B — Custom iPaaS | C — Zure Platform |
|---|---|---|---|
| Licensing cost | ✗ High annual licensing | ✓ Consumption-based only Possible partner-specific license-fees. |
✓ Consumption-based only |
| Time to production | ~ 12–24 months | ✗ 18–36 months | ✓ Faster with pre-built foundation |
| Operational tooling | ✓ Vendor-provided | ✗ Must be built | ✓ Included out of the box |
| Vendor lock-in | ✗ High — new vendor | ✓ Low — standard services | ✓ Low — Azure standard services |
| Extensibility | ~ Within product limits | ✓ Full control | ✓ Full control + pre-built patterns |
| BizTalk migration experience | ~ Varies by partner | ~ Requires internal expertise | ✓ Proven BizTalk migration track record |
| Automated deployments | ~ Varies by partner | ✗ Must be built | ✓ Included out of the box |
| Code ownership | ✗ None | ✓ Full control | ✓ Full control |
| AI-enabled development | ~ Starting to emerge | ✗ Must be built | ✓ AI-native development |
| Support options | ✗ Restricted to vendor options | ~ You support yourself | ✓ Self-support, from Zure, or hybrid |
| Ease of vendor-change | ✗ Massive project | ~ Hard because of fully custom-built architecture | ✓ You can go anyday and continue running and maintaining your documented and patterns-based integrations |
Zure Integration Platform is a production-ready, licence-free integration platform built on Azure PaaS services. It gives you the flexibility of a custom build with the operational maturity of a commercial product.
Developed and maintained by Zure's integration specialists, the platform has been refined across multiple enterprise migration projects — including migrations from BizTalk Server. It ships with pre-built patterns for message routing, transformation, error handling, monitoring, and retry logic, so your team can focus on building interfaces, not infrastructure.
Built on Logic Apps, Service Bus, API Management, and Functions. Standard Azure services — no proprietary runtime to manage.
Monitoring dashboards, alerting, message replay, and structured error handling included from day one.
Proven patterns for migrating BizTalk orchestrations, schemas, and adapters to Azure-native equivalents.
No integration middleware licence. Your interfaces, your code, your Azure subscription — Zure provides the platform and expertise.