Microsoft BizTalk Server is an on-premises integration platform that connects applications, exchanges business documents, transforms data, and runs multi-step processes. It is best known for enterprise application integration (EAI), business-to-business communication (B2B), and electronic data interchange (EDI) in Microsoft-based environments. BizTalk Server 2020 remains supported, with mainstream support through April 11, 2028 and extended support through April 9, 2030.

What is Microsoft BizTalk Server?

BizTalk Server is an integration broker and process automation platform from Microsoft. It sits between systems that use different protocols, message formats, and data models. Instead of creating a separate point-to-point connection for every pair of applications, a team can route messages through BizTalk, apply shared transformations and rules, and manage the integrations from one platform. Microsoft first released BizTalk Server in 2000. The current major release is BizTalk Server 2020.

What is BizTalk Server used for?

BizTalk is used where a business process crosses application or organizational boundaries and the participating systems cannot exchange data directly in a reliable, manageable way.

Enterprise application integration

Enterprise application integration connects systems inside one organization. BizTalk may synchronize customers between a CRM and ERP system, pass orders to a warehouse platform, or connect a mainframe transaction to a newer web application. It is most useful when those systems cannot adopt the same interface standard.

B2B and EDI

BizTalk has established support for EDI and partner management. It can process purchase orders, invoices, shipping notices, and acknowledgements, while AS2 supports secure document exchange with external trading partners.

Supply chain and manufacturing

Manufacturers and distributors use integration middleware to connect production, inventory, procurement, logistics, and ERP processes. BizTalk can route transactions across this chain and manage format differences between internal systems and partner interfaces.

Healthcare and public-sector integration

Existing BizTalk estates are found in healthcare and government, where older systems, strict access controls, industry message formats, and long retention periods often coexist. A migration assessment must cover the interfaces and operating procedures around BizTalk, not only the applications deployed to it.

Hybrid integration

BizTalk Server 2020 can participate in hybrid architectures. An organization might keep a local ERP integration in BizTalk while introducing Azure Logic Apps, Service Bus, API Management, or Functions for newer cloud workflows. This reduces immediate migration risk but creates two environments that need clear ownership.

A purchase order example

Consider a purchase order sent by a retailer as EDI. BizTalk receives and validates the document, maps it to the supplier’s ERP schema, and routes it to the right endpoint. An orchestration can wait for an acknowledgement, handle an exception, or return a status update. Each system keeps its own interface while BizTalk handles the translation and process flow.

How does BizTalk Server work?

BizTalk uses a publish-and-subscribe model. Incoming messages are published to the MessageBox database, and BizTalk routes them to orchestrations or send ports whose subscriptions match the message properties. A complete flow looks like this:

• Receive the message

  A receive location accepts data through an adapter configured for the source transport or system.

• Prepare the inbound payload

  A receive pipeline can decode, decrypt, disassemble, validate, and promote message properties.

• Publish to MessageBox

  The MessageBox stores the message and provides the central persistence and routing mechanism.

• Evaluate subscriptions

  BizTalk matches message type and promoted properties to orchestration or send-port subscriptions.

• Run process logic

  An orchestration can transform data, call another system, evaluate rules, wait for a response, or create a new message.

• Prepare the outbound payload

  A send pipeline assembles the target format and applies required encoding or security processing.

• Deliver and track

  The send adapter transmits the message, while tracking and administration tools record configured runtime activity.

Main BizTalk Server components

The main components below cover transport, message preparation, persistence, routing, process logic, monitoring, and administration. They can be combined differently for each application.

Adapters, ports, and locations

Adapters communicate with external systems and protocols. Receive locations define the endpoints where messages enter BizTalk, while receive ports group one or more locations. Send ports combine an outbound adapter, pipeline, endpoint, and subscription filter.

Pipelines, schemas, and maps

Pipelines decode, disassemble, validate, encrypt, decrypt, assemble, and encode messages. Schemas describe message structure, while maps transform a source schema into the format expected by the destination.

MessageBox and subscriptions

The MessageBox is a SQL Server database that provides persistence, routing, and subscription evaluation. BizTalk promotes selected message properties, evaluates active subscriptions, and delivers the message to matching orchestrations or send ports.

Orchestrations and business rules

Orchestrations express long-running or multi-step process logic through a visual workflow model. The Business Rules Engine keeps selected decisions separate from orchestration or application code, which can make frequently changed rules easier to manage.

BAM, tracking, and administration

Business Activity Monitoring tracks business milestones and measures. Administration and tracking tools deploy applications, configure runtime artifacts, inspect service instances, troubleshoot failures, and monitor message activity.

Enterprise SSO and security

Enterprise Single Sign-On stores configuration values and can map credentials between Windows and non-Windows systems. Security still depends on the whole design, including service accounts, certificates, network controls, adapter configuration, and database access.

When an orchestration is unnecessary

Not every integration needs an orchestration. A static send-port subscription can route a message without a workflow. Adding an orchestration where simple messaging would work introduces another service instance, deployment artifact, and failure path without adding business value.

Architecture and operations

A production BizTalk environment has several moving parts. SQL Server performance, host separation, tracking volume, adapter behavior, retry settings, backup procedures, and deployment practices all affect reliability. The architecture must be designed for the actual message volume and failure modes.

BizTalk capabilities and components

Capabilities	Description	Components	Description
Message handling	Receives, persists, routes, and sends messages across different systems and formats.	Adapters	Connect BizTalk to transports, applications, databases, enterprise systems, and partner endpoints.
Data preparation	Parses, validates, secures, assembles, and encodes inbound and outbound payloads.	Pipelines	Run ordered processing components on messages entering or leaving BizTalk.
Data transformation	Converts a source document into the schema expected by the destination.	Schemas and maps	Define message structures and transform data between those structures.
Persistent routing	Uses promoted properties and subscriptions to determine which service receives a message.	MessageBox	Stores messages and provides the central publish-and-subscribe routing mechanism.
Process automation	Coordinates calls, waits, decisions, exceptions, and multi-step business processes.	Orchestrations	Express executable workflow logic through visual shapes and deployed artifacts.
Externalized decisions	Allows selected rules to change separately from orchestration or application code.	Business Rules Engine	Evaluates policies and vocabularies used by integration processes.
Business monitoring	Tracks business milestones and measures in terms relevant to process owners.	BAM and tracking	Collect runtime events for monitoring, diagnosis, and operational reporting.
Platform operations	Supports deployment, configuration, security, troubleshooting, and runtime management.	Administration and SSO	Manage BizTalk applications, service instances, configuration values, and credential mappings.

Is BizTalk Server still supported?

BizTalk Server 2020 is still supported under Microsoft’s Fixed Lifecycle Policy. Microsoft extended the mainstream support period, giving existing customers a defined window in which to maintain, stabilize, and modernize their platforms.

BizTalk Server 2020 support dates

Microsoft lists mainstream support through April 11, 2028 and extended support through April 9, 2030. These dates follow the Pacific Time schedule on the official Microsoft lifecycle page.

What support means

Support does not mean that Microsoft has announced another major BizTalk release. It means organizations can operate BizTalk Server 2020 within a published lifecycle while they decide which integrations to keep, modernize, or migrate.

Check the complete technology stack

An estate can run a supported BizTalk release while depending on an unsupported Windows Server version, SQL Server version, adapter, accelerator, or third-party component. Record the complete software stack, edition, cumulative update, and dependencies during the assessment.

Benefits of BizTalk Server

BizTalk earned its place in enterprise integration through durable messaging, subscription-based routing, transformations, EDI, orchestration, and controlled administration. Organizations with experienced teams may also have years of tested schemas, maps, partner agreements, and operational procedures that still deliver value.

Limitations and operating costs

The platform requires Windows Server, SQL Server, BizTalk licensing, patching, backups, monitoring, and capacity planning. Specialist development and administration skills are less common than they were at BizTalk’s adoption peak, and changes often follow a heavier release process than a small cloud workflow.

When BizTalk remains a good fit

Keeping BizTalk can be reasonable when integrations are stable, documented, supported, and expensive to change relative to their business value. Modernization becomes more attractive when the estate is difficult to support, blocks application change, or no longer fits the organization’s cloud and operating model.

The decision should be made per workload. A reliable EDI flow with several established partners may stay in BizTalk while a new SaaS workflow is built in Azure. Treating the entire estate as one migration unit can hide both easy wins and high-risk dependencies.

BizTalk Server vs Azure Logic Apps

BizTalk Server and Azure Logic Apps both coordinate integrations, but they use different deployment and operating models. Logic Apps is a managed Azure workflow service. A broader BizTalk replacement often combines it with Service Bus, API Management, Event Grid, Functions, storage, and monitoring services.

Area	BizTalk Server	Azure Logic Apps and Azure Integration Services
Primary deployment	Customer-managed servers, usually on premises or in Azure virtual machines.	Managed Azure services with multitenant and single-tenant workflow options.
Infrastructure	The organization manages Windows, SQL Server, BizTalk hosts, patching, backup, and capacity.	Microsoft manages service infrastructure; the customer manages workflows, resources, connectivity, and governance.
Scaling	Planned through BizTalk hosts, server nodes, SQL Server, and runtime configuration.	Scaling options depend on the Logic Apps hosting model and connected Azure services.
Development	Visual Studio projects, BizTalk artifacts, .NET Framework, and MSI-based deployments.	Visual workflow design, connectors, Azure deployment tooling, and custom code where needed.
Connectivity	Mature adapters for enterprise, partner, and legacy systems.	A broad connector catalog plus built-in operations, APIs, gateways, and messaging services.
State and logic	Orchestrations and MessageBox persistence.	Stateful or stateless workflows, often combined with Service Bus and other services.
EDI and B2B	Mature EDI, AS2, trading partner, and accelerator capabilities.	Logic Apps B2B capabilities with architecture and feature differences that require assessment.
Operations	Administration Console, tracking databases, BAM, and third-party monitoring tools.	Azure portal, run history, Azure Monitor, Application Insights, and Log Analytics.
Commercial model	Server and core licensing plus infrastructure and operational costs.	Consumption or hosting-based Azure charges plus supporting services, network, and operations.
Best assessment unit	Existing BizTalk application and its dependencies.	Individual workload and its target Azure architecture.

BizTalk is often the stronger short-term fit for stable, complex on-premises or B2B integrations that already have tested artifacts, operating procedures, and specialist support. The organization remains responsible for infrastructure, SQL Server, scaling, patching, backup, and runtime administration.

Azure Logic Apps and Azure Integration Services suit cloud and hybrid workflows where managed infrastructure, connector-based development, Azure governance, and service-level scaling are priorities. They still require architecture, cost controls, observability, deployment practices, and support ownership.

Compare the platforms workload by workload. A file transfer, an EDI partner flow, a correlated orchestration, and a custom pipeline component may each need a different Azure target. See Multishoring’s Azure Logic Apps services and the wider Azure Integration Services offering.

BizTalk Server alternatives

The right alternative depends on deployment constraints, integration patterns, existing skills, partner requirements, and the wider application strategy. A product-level feature checklist is not enough to select a migration target.

• Azure Integration Services

  A Microsoft-oriented cloud and hybrid target that can combine Logic Apps, Service Bus, API Management, Event Grid, Functions, and related Azure services.

• Boomi

  An iPaaS for SaaS, application, data, API, and B2B integration. Read Multishoring’s guide to what Boomi is and how it works.

• MuleSoft Anypoint Platform

  A common option for API-led connectivity, API management, and integration across cloud and on-premises environments.

• IBM App Connect and TIBCO

  Established enterprise integration options that may fit organizations with existing IBM or TIBCO platforms, skills, and operating practices.

Should you keep, modernize, or migrate BizTalk?

Keep and stabilize

Keep an integration when it is stable, well documented, supported, and expensive to change relative to its business value. The platform still needs current cumulative updates, database maintenance, monitoring, tested recovery procedures, and people who can diagnose failures.

Modernize in stages

A hybrid plan moves selected interfaces while BizTalk continues to run the rest. Teams often start with simpler file transfers, API mediation, or isolated partner flows. Coexistence reduces release risk but requires logging, identity, networking, and support processes across both platforms.

Migrate and retire

A full migration becomes more attractive when the estate is hard to support, the organization has adopted Azure broadly, or BizTalk blocks application modernization. The plan must leave time for partner testing, reconciliation, parallel operation, endpoint changes, and retirement of old artifacts.

A practical BizTalk migration process

BizTalk migration is a redesign for a different runtime and operating model, not a direct product upgrade. The practical process starts with an inventory and usage analysis, then classifies complexity, selects target patterns, organizes migration waves, rebuilds operations, tests business outcomes, and retires BizTalk only after reconciliation.

Frequently asked questions

Is BizTalk Server obsolete?

BizTalk Server 2020 is not obsolete in the support sense. Microsoft lists mainstream support through April 11, 2028 and extended support through April 9, 2030. The product is mature, however, and Azure services are Microsoft’s primary direction for new cloud integration work.

What is the latest version of BizTalk Server?

The latest major version is BizTalk Server 2020. Organizations should also check their cumulative update level and the support status of Windows Server, SQL Server, adapters, accelerators, and third-party components.

What will replace BizTalk Server?

There is no single replacement service for every BizTalk feature. A Microsoft Azure target commonly combines Logic Apps with Service Bus, API Management, Event Grid, Functions, storage, and monitoring. The exact combination depends on the workload.

Can BizTalk Server run in Azure?

Yes. BizTalk Server can run on Azure virtual machines, and Microsoft provides Azure Marketplace images for supported editions. The organization still operates BizTalk, Windows, SQL Server, and the surrounding platform.

What is the difference between BizTalk and an ESB?

An enterprise service bus focuses on mediation, routing, and communication between services. BizTalk includes ESB-like messaging capabilities, but it also provides orchestration, EDI and B2B features, mapping, business rules, tracking, and deployment tooling.

Can BizTalk migration be automated?

Only partly. Tools can inventory artifacts and convert selected patterns, but complex orchestrations, custom code, EDI, unsupported adapters, and operational procedures require analysis and manual engineering. Testing must validate business results as well as technical execution.

Official sources and next steps

For current lifecycle information, use the BizTalk Server 2020 lifecycle page. Microsoft’s dates should take precedence over older blog posts, licensing guides, or assumptions based on previous versions.

Architecture details are documented in Microsoft’s guides to the BizTalk Server Messaging Engine and the lifecycle of a message. Microsoft also maintains the open-source Azure Integration Migrator for assessment and partial conversion of supported scenarios.

For platform support, modernization planning, or migration delivery, use the resources below:

• BizTalk consulting and integration services: support, modernization planning, and migration delivery.
• Integration audit: inventory applications, dependencies, support risks, and migration candidates.

A good next step is to inventory the estate before choosing a target. Contact Multishoring to discuss the scope, risks, and most practical path for your BizTalk environment.