What Is Microsoft BizTalk Server? Architecture, Uses and Alternatives
Kamran Liaquat Ali- posted on
- No Comment
Quick answer: Microsoft BizTalk Server is an on-premises integration platform that connects business systems such as ERP, CRM, databases, file shares and trading partners. It receives messages through adapters, stores them in a SQL Server “MessageBox”, transforms them with maps, runs business processes called orchestrations, and sends the results to other systems. BizTalk Server 2020 is the final major release, and Microsoft’s recommended path for new integration work is Azure Integration Services.
This guide explains how BizTalk works, where it still makes sense, and how to plan a move to modern integration tools without breaking the processes your business depends on.
In this guide
- What Does BizTalk Server Do?
- BizTalk Server Architecture
- How a Message Flows Through BizTalk
- Strengths and Limitations
- Support Timeline and What It Means
- BizTalk Server vs Azure Integration Services
- When BizTalk Is Still a Reasonable Choice
- A Safe Modernisation Roadmap
- Operating BizTalk Well Until You Migrate
- Frequently Asked Questions
What Does BizTalk Server Do?
BizTalk sits in the middle of an organisation’s systems so they do not need direct, point-to-point connections. Typical jobs include:
- Exchanging EDI documents (X12, EDIFACT) and AS2 messages with suppliers and customers.
- Moving orders, invoices and master data between SAP, Dynamics, Oracle and in-house databases.
- Picking up flat files or XML from a folder or SFTP server, validating them and loading them into another system.
- Exposing internal processes as SOAP or REST services.
- Coordinating long-running processes that wait hours or days for an approval or a reply.
BizTalk Server Architecture
| Component | Role |
|---|---|
| Receive port and receive location | Entry point. An adapter (FILE, SFTP, HTTP, WCF, SQL, SAP and others) listens for messages. |
| Receive pipeline | Decodes, disassembles and validates the message, for example turning a flat file into XML. |
| MessageBox database | SQL Server database where every message is published. Subscriptions decide who receives it. |
| Maps | XSLT-based transformations between message schemas. |
| Orchestrations | Visual workflows for multi-step and long-running business processes. |
| Send pipeline and send port | Prepare the outgoing message and deliver it through an adapter. |
| Hosts and host instances | Logical containers and the Windows processes that run receive, send and orchestration work. |
| Business Rules Engine and BAM | Externalised business rules and business activity monitoring. |
How a Message Flows Through BizTalk
- A receive location picks up a message, for example an XML order dropped into a folder.
- The receive pipeline validates it against a schema and promotes key fields, such as the customer ID, as context properties.
- The message is published to the MessageBox.
- Any orchestration or send port whose subscription matches those properties receives a copy.
- A map transforms the message into the target format.
- The send port delivers it, retrying automatically if the destination is unavailable.
This publish-and-subscribe model is BizTalk’s main strength. The sender does not need to know how many systems consume a message, and failed deliveries can be suspended and resumed later instead of being lost.
Strengths and Limitations
| Strengths | Limitations |
|---|---|
| Mature EDI, AS2 and B2B support | Windows Server and SQL Server only, with significant licensing cost |
| Guaranteed delivery and suspend/resume of failed messages | Development relies on older Visual Studio tooling and specialist skills |
| Rich adapter library for enterprise systems | Scaling means adding servers rather than elastic cloud capacity |
| Good fit for long-running, stateful processes | No new major versions, so the platform will not gain modern features |
Support Timeline and What It Means
BizTalk Server 2020 is the last major version. According to Microsoft’s lifecycle policy, mainstream support ends in April 2028 and extended support ends in April 2030. After mainstream support ends, Microsoft provides security fixes but no new features. Search for “BizTalk Server 2020” on Microsoft’s product lifecycle site to confirm the exact dates that apply to your edition.
For most organisations this means BizTalk can keep running safely for now, but any new integration should be built on a platform with a longer future, and existing interfaces should have a migration plan.
BizTalk Server vs Azure Integration Services
| BizTalk concept | Azure Integration Services equivalent |
|---|---|
| Orchestration | Azure Logic Apps workflows (Standard plan for stateful, single-tenant workloads) |
| MessageBox publish/subscribe | Azure Service Bus topics and subscriptions, or Event Grid for events |
| Maps (XSLT) | Logic Apps data mapper and XSLT maps in an integration account or Standard project |
| Adapters | Logic Apps built-in and managed connectors, plus on-premises data gateway |
| SOAP/WCF services | Azure API Management in front of Logic Apps or Azure Functions |
| Custom pipeline components | Azure Functions or custom code in Logic Apps Standard |
| EDI and AS2 | Logic Apps B2B features with an integration account |
The mapping is not one-to-one. Logic Apps workflows are usually smaller and more focused than large BizTalk orchestrations, and error handling is designed differently, so a migration is a redesign rather than a copy.
When BizTalk Is Still a Reasonable Choice
- You already run stable BizTalk interfaces and the business has no budget or reason to change them before the support end date.
- Data must stay on-premises for regulatory reasons and cloud services are not allowed.
- You rely on heavy EDI volumes with existing trading-partner agreements that are expensive to re-test.
Even then, freeze new development on BizTalk where possible and keep the environment patched with the latest cumulative update.
A Safe Modernisation Roadmap
- Inventory: list every application, receive location, send port, orchestration, map and partner agreement. Export bindings from the BizTalk Administration Console and record message volumes.
- Classify: mark each interface as retire, keep until end of life, or migrate. Many old interfaces turn out to be unused.
- Pick a pilot: start with a simple, low-risk flow such as a file-to-database load, not your most complex orchestration.
- Build the platform first: set up networking, the on-premises data gateway or VNet integration, identity, monitoring and CI/CD before moving interfaces.
- Run in parallel: compare outputs from BizTalk and the new flow for the same input before switching traffic.
- Cut over in batches and keep BizTalk available for rollback until each batch is proven in production.
Microsoft publishes migration guidance for moving BizTalk workloads to Azure Logic Apps, including how BizTalk features map to Azure services. Read it before estimating effort, because custom pipeline components and complex orchestrations usually take the most time.
Operating BizTalk Well Until You Migrate
- Monitor suspended instances daily and fix root causes instead of repeatedly resuming messages.
- Keep the SQL Server Agent jobs that BizTalk installs (backup, purge and tracking cleanup) enabled and healthy; disabled jobs are a common cause of MessageBox growth and slowdowns.
- Limit message body tracking to what you need, since full tracking increases database size.
- Separate receive, send and orchestration work into different hosts so one busy workload does not starve the others.
- Store binding files and deployment scripts in source control so environments can be rebuilt.
Frequently Asked Questions
Is BizTalk Server discontinued?
No new major versions are planned after BizTalk Server 2020, but it is still supported under Microsoft’s lifecycle policy until its published end dates. Existing installations continue to work and receive security updates during the support period.
What replaces BizTalk Server?
Microsoft’s recommended successor is Azure Integration Services: Logic Apps, Service Bus, API Management, Event Grid and Azure Functions. Other organisations choose third-party integration platforms. The right choice depends on where your systems run and what skills your team has.
Do I need to know .NET to work with BizTalk?
Basic C# helps for custom pipeline components, helper libraries and orchestration expressions. Most day-to-day work, however, involves schemas, maps, bindings and administration rather than writing application code.
Is BizTalk an ETL tool?
Not exactly. BizTalk is message-based integration middleware that moves individual business documents in near real time. ETL tools are built for bulk data movement into data warehouses. See our comparison of ETL tools for data integration for that use case.
For broader .NET and software topics, visit our programming and development guide.
